text:
Auto Build Marlin - command not found: platformio

I am new to compiling my own firmware. I am now trying to build Marlin 2.0.7.2 for the SKR Mini E3 V1.2 using the custom configuration supplied by the Marlin GitHub. I have used VSCode to compile Marlin versions 2.0.7 and 2.0.7.1 for the same board. Both compiled beautifully using the Auto Build Marlin and the Platformio plugins. I am doing the same thing as before but now I keep receiving this error:
platformio run -e STM32F103RC_btt_512K ; echo "done" >/var/folders/08/p81zkj6x7l7gq17dsxv4pxrh0000gn/T/ipc
stevewise@Steves-MacBook-Pro Marlin-2.0.x % platformio run -e STM32F103RC_btt_512K ; echo "done" >/var/folders/08/p81zkj6x7l7gq17dsxv4pxrh0000gn/T/ipc
zsh: command not found: platformio
stevewise@Steves-MacBook-Pro Marlin-2.0.x %
I have uninstalled everything and reinstalled several times with no success. I was able to get a successful build by going into project tasks in Platformio and doing the build from there. I apologize in advance if I am doing something stupid but I can't figure out what is wrong. I have searched the internet but with no success. Thanks for your help.

Same problem!
echo "done" >/var/folders/kh/9r2ycv7921lgg6q7t7twmsym0000gn/T/ipc
zsh: command not found: platformio

I have also noticed this error when doing the update in PlatformIO.
Updating platformio/contrib-pysite            2.38.201019 @ ~2.38.0              [Incompatible 2.39.201019]
I removed the folder ".platformio/penv" and then updated again but with the same error. Not sure if this helps.

I just got the same message! There must be a problem with the new update of platform.io...

Anyway I can build and upload. Sometimes is not uploading fine but repeating the process it works.
You have to go to the left vertical menu and click on the Platformio icon, then choose the file, in may case is env:melzi_optimized, @slwise in your case should be env:STM32F103RC_btt_512K. Click it and you will see below it build, upload and more options.
I hope this will help!

Anyway I can build and upload. Sometimes is not uploading fine but repeating the process it works.
You have to go to the left vertical menu and click on the Platformio icon, then choose the file, in may case is env:melzi_optimized, @slwise in your case should be env:STM32F103RC_btt_512K. Click it and you will see below it build, upload and more options.
I hope this will help!

This seems like a question for the platformio extension/team https://github.com/platformio/platformio-vscode-ide/issues


text:
Crash when toggling panel on newly opened folders

Version: 1.51.0-insider (user setup)
Commit: a5dfd9dcf83620a3b50dd56dc0117f83415c2ca8
Date: 2020-11-03T19:58:29.881Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19042
Steps to Reproduce:

Open project with a minimized panel
Toggle the panel with Ctrl+J
VS Code crashes

This doesn't seem to happen on all projects, only newer ones/ones I recently cloned. I attached a dump file.
nov3-dump.zip

Does this issue occur when all extensions are disabled?: Yes

Symbolicated trace
Operating system: Windows NT
                  10.0.19041 546
CPU: amd64
     family 6 model 126 stepping 5
     8 CPUs

GPU: UNKNOWN

Crash reason:  EXCEPTION_STACK_OVERFLOW
Crash address: 0x7ffc607e6e27
Process uptime: 5 seconds

Thread 0 (crashed)
 0  ntdll.dll!RtlpAllocateHeapInternal + 0x127
    rax = 0x000001e3f90c67d0   rdx = 0x0000000000000001
    rcx = 0x000001e3f8fc0000   rbx = 0x000001e3f90c0000
    rsi = 0x0000000000000000   rdi = 0x0000000000000002
    rbp = 0x000000c6ab6040b9   rsp = 0x000000c6ab604000
     r8 = 0x0000000000000018    r9 = 0x0000000000000000
    r10 = 0x0000000000000000   r11 = 0x0000000000000000
    r12 = 0x0000000000000018   r13 = 0x0000000000000020
    r14 = 0x0000000000000000   r15 = 0x0000000000000000
    rip = 0x00007ffc607e6e27
    Found by: given as instruction pointer in context
 1  KERNELBASE.dll!MultiByteToWideChar + 0x186
    rbp = 0x000000c6ab6040b9   rsp = 0x000000c6ab604090
    rip = 0x00007ffc5e34e8e6
    Found by: stack scanning
 2  Code - Insiders.exe!uv__convert_utf8_to_utf16 [util.c : 1306 + 0x11]
    rbp = 0x000000c6ab6040b9   rsp = 0x000000c6ab604160
    rip = 0x00007ff72b3108b0
    Found by: call frame info
 3  Code - Insiders.exe!uv_os_getenv [util.c : 1473 + 0xf]
    rbp = 0x000000c6ab6040b9   rsp = 0x000000c6ab6041c0
    rip = 0x00007ff72b3104a2
    Found by: call frame info
 4  Code - Insiders.exe!node::RealEnvStore::Get(v8::Isolate *,v8::Local<v8::String>) [node_env_var.cc : 67 + 0x8]
    rbp = 0x000000c6ab6040b9   rsp = 0x000000c6ab614240
    rip = 0x00007ff72bd6fdb6
    Found by: call frame info
 5  Code - Insiders.exe!node::EnvGetter [node_env_var.cc : 263 + 0xe]
    rbp = 0x000000c6ab6040b9   rsp = 0x000000c6ab6147e0
    rip = 0x00007ff72bd717bc
    Found by: call frame info
 6  Code - Insiders.exe!v8::internal::PropertyCallbackArguments::BasicCallNamedGetterCallback(void (*)(v8::Local<v8::Name>,v8::PropertyCallbackInfo<v8::Value> const &),v8::internal::Handle<v8::internal::Name>,v8::internal::Handle<v8::internal::Object>,v8::internal::Handle<v8::internal::Object>) [api-arguments-inl.h : 214 + 0x9]
    rbp = 0x000000c6ab6040b9   rsp = 0x000000c6ab614840
    rip = 0x00007ff72a035ba9
    Found by: call frame info
 7  Code - Insiders.exe!v8::internal::Runtime_LoadPropertyWithInterceptor(int,unsigned __int64 *,v8::internal::Isolate *) [ic.cc : 2746 + 0x222]
    rbp = 0x000000c6ab6040b9   rsp = 0x000000c6ab614940
    rip = 0x00007ff72a032755
    Found by: call frame info
 8  Code - Insiders.exe!Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_NoBuiltinExit + 0x3c
    rbp = 0x000000c6ab6040b9   rsp = 0x000000c6ab614aa0
    rip = 0x00007ff72a7adb9c
    Found by: call frame info

Stack overrun when attempting to convert one of the process.env properties from utf-8 to utf-16. Can you print your process.env, we should be able to create a minimal repro.

I have better repro steps now.

Rename a cloned project's directory to a folder name that was never opened before within VS Code (e.g. ~/vscode to ~/vscode2)
Open folder on that project locally
Toggle the panel (I use Ctrl+J)
Program crashes.

However, if I merely show the panel with Ctrl+~, the panel and terminal show properly, and no crash occurs. Moreover, whenever I reload the project afterwards, toggling the panel works without crashing the program. If I rename the folder to another new name, toggling the panel once again crashes the program.

Me too, toggle panel crashed when

Terminal is not opened
Problem window is not opened
Debug Console is not opened
Just open VScode Window

Me too, toggle panel crashed when

Terminal is not opened
Problem window is not opened
Debug Console is not opened
Just open VScode Window

I got the quick fix.
we need to add this in keybindings.json
    {
        "key": "ctrl+j",
        "command": "workbench.action.togglePanel",
        "when": "terminalIsOpen"
    },
    {
        "key": "ctrl+j",
        "command": "workbench.action.terminal.new",
        "when": "!terminalIsOpen"
    },

According to this link, we can utilize the Context condition

/** A context key that is set when there is at least one opened integrated terminal. */
export const KEYBINDING_CONTEXT_TERMINAL_IS_OPEN = new RawContextKey('terminalIsOpen', false);

I got the quick fix.
we need to add this in keybindings.json
    {
        "key": "ctrl+j",
        "command": "workbench.action.togglePanel",
        "when": "terminalIsOpen"
    },
    {
        "key": "ctrl+j",
        "command": "workbench.action.terminal.new",
        "when": "!terminalIsOpen"
    },

According to this link, we can utilize the Context condition

/** A context key that is set when there is at least one opened integrated terminal. */
export const KEYBINDING_CONTEXT_TERMINAL_IS_OPEN = new RawContextKey('terminalIsOpen', false);

Related fixed issue: https://github.com/microsoft/vscode/issues/111463
@ejabu are you on the latest Insiders build (v1.53.0-insider)?

Related fixed issue: https://github.com/microsoft/vscode/issues/111463
@ejabu are you on the latest Insiders build (v1.53.0-insider)?

Related fixed issue: #111463
@ejabu are you on the latest Insiders build (v1.53.0-insider)?

nope, I still using v1.52.1

Related fixed issue: #111463
@ejabu are you on the latest Insiders build (v1.53.0-insider)?

nope, I still using v1.52.1

source: gharchive/issue

repo: microsoft/vscode

license: MIT

license_type: permissive

license_source: github-api


text:
Auto-inject codicon font into webviews

It would be good to allow webviews easy access to the codicons font so they don't need to include/load it themselves.

#95199

authors: eamodio usernamehw


text:
settings sync creates too many requests?

Issue Type: Bug
Doing something that affects settings sync (like resizing text) while having multiple windows open appears to hit some sort of rate-limiting error.
VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:30:02.420Z)
OS version: Darwin x64 20.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
4, 4, 4

Memory (System)
16.00GB (0.10GB free)

Process Argv
--crash-reporter-id 8272335d-86bd-463b-8515-a55ed4b8469a

Screen Reader
no

VM
0%

Extensions (50)

Extension
Author (truncated)
Version

Handlebars
and
0.4.1

tailwindcss-extension-pack
and
1.1.4

vscode-apollo
apo
1.17.1

tailwind-docs
aus
1.4.0

vscode-tailwindcss
bra
0.5.6

rescript-vscode
che
1.0.2

npm-intellisense
chr
1.3.1

overmind-devtools-vscode
chr
0.0.36

bracket-pair-colorizer-2
Coe
0.2.0

vscode-eslint
dba
2.1.14

vscode-deno
den
2.3.3

gitlens
eam
11.0.6

vscode-npm-script
eg2
0.3.13

prettier-vscode
esb
5.8.0

vscode-diff
fab
1.4.0

vscode-jest-runner
fir
0.4.31

vscode-svelte-snippets
fiv
0.5.0

auto-rename-tag
for
0.1.5

vscode-pull-request-github
Git
0.22.0

headwind
hey
1.7.0

easy-snippet
inu
0.6.2

vscode-git-add-and-commit
iva
2.1.1

reason-vscode
jar
1.7.13

vscode-markdown-notes
kor
0.0.21

tailwind-sass-syntax
mac
1.2.1

code-coverage
mar
1.2.3

vscode-language-babel
mgm
0.0.30

vscode-docker
ms-
1.9.0

mssql
ms-
1.10.0

vscode-postgresql
ms-
0.3.0

remote-containers
ms-
0.154.1

vscode-typescript-tslint-plugin
ms-
1.3.2

vsliveshare
ms-
1.0.3303

vsliveshare-audio
ms-
0.1.91

vsliveshare-pack
ms-
0.4.0

sqltools
mtx
0.23.0

sqltools-driver-pg
mtx
0.2.0

sqltools-driver-sqlite
mtx
0.2.0

color-highlight
nau
2.3.0

angular-console
nrw
15.0.0

docker-compose
p1c
0.3.5

prisma
Pri
2.13.0

vscode-yaml
red
0.13.0

mdx
sil
0.1.0

svelte-vscode
sve
102.8.0

markdown-links
tch
0.8.0

gitflow
vec
1.2.1

vscodeintellicode
Vis
1.2.10

vscode-wakatime
Wak
4.0.9

markdown-all-in-one
yzh
3.4.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
openlogontheside:30221877
python763:30178808
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
python504:30227505
vswsl492:30211401
wsl2promptcf:30224613
pythonvsdeb440:30237827
unusedprompt:30224610
folderexplorercf:30224615
openfilemenu:30224647
pythonvsded773cf:30236630
vsjup459cf:30237188

@mwarger, looked at the service-side telemetry and between 2020-12-17 16:15 UTC and 2020-12-17 16:50 UTC, one of the Settings Sync regions has experienced an increased rate of throttling on requests made to Azure CosmosDB requests. There was no increase in the number of requests so we will work with our Azure partner team to understand the root cause of the throttling.
As of 2020-12-17 16:50 UTC, all service health indicators returned to a healthy baseline.
I will close this issue but please feel free to reopen if you are still seeing the issue. Apologies for the inconvenience.

authors: lszomoru mwarger


text:
Expose actions to duplicate editor groups

We have support to copy/duplicate editor groups including all of the editors, but we never exposed this as commands/actions.

Verification: try to use the 4 duplicate group actions and verify that text editors duplicate in the new group.

Verification: try to use the 4 duplicate group actions and verify that text editors duplicate in the new group.

Works great!
One suggestion: only show the Duplicate Group Left and Duplicate Group Up if there is more than 1 group currently open. Otherwise these actions are same as the others and might just create confusion...

Works great!
One suggestion: only show the Duplicate Group Left and Duplicate Group Up if there is more than 1 group currently open. Otherwise these actions are same as the others and might just create confusion...

authors: bpasero isidorn


text:
Test: Mac universal build

Refs: https://github.com/microsoft/vscode/issues/113851

[x] Mac @aeschli with intel
[ ] Mac @kieferrm with intel
[ ] Mac @deepak1556 with intel
[ ] Mac @chrmarti with apple silicon
[ ] Mac @jrieken with apple silicon
[ ] Mac @bpasero with apple silicon

Complexity: 2
Create Issue

Background
We are looking to make universal build as the default for mac which can run natively on x86_64 as well as arm64. As a start in this iteration the default download on the website will point to universal build while we will still provide arch specific downloads.

Testing
The website bits are pending to be merged and published to ppe https://github.com/microsoft/vscode-website/pull/924. So for testing use the builds from https://builds.code.visualstudio.com/builds/insider

Download universal build and install on x86_64 machine which had a previously running native x86_64 copy.

verify that universal app continues your session from where you had left off on the previous native version without any changes to configurations
verify your everyday setup just works
verify automatic update works

Download universal build and install on arm64 machine which had a previously running native arm64 copy.

verify that universal app continues your session from where you had left off on the previous native version without any changes to configurations
verify your everyday setup just works
verify automatic update works

I have assigned this item based on the members of team who have access to devices with M1 chips, feel free to reassign or unassign if you are blocked on other items. Thanks!

I have assigned this item based on the members of team who have access to devices with M1 chips, feel free to reassign or unassign if you are blocked on other items. Thanks!

The only way I figured out how to ensure I am on universal build is by checking the size of the application. Not sure we want a way to show this in e.g. the about dialog to diagnose issues?

The only way I figured out how to ensure I am on universal build is by checking the size of the application. Not sure we want a way to show this in e.g. the about dialog to diagnose issues?

For me this isn't working

For me this isn't working

@deepak1556 You forgot to update the Create Issue link, so people have created issues related to the wrong TPI.

@deepak1556 You forgot to update the Create Issue link, so people have created issues related to the wrong TPI.

@deepak1556 I don't have a silicon Mac. I'll just test with Intel, so you can potentially unassign yourself.

@deepak1556 I don't have a silicon Mac. I'll just test with Intel, so you can potentially unassign yourself.

If got an M1, I'll test the apple silicon -> universal direction.

If got an M1, I'll test the apple silicon -> universal direction.

universal check can be done like this:
❯ file Visual\ Studio\ Code\ -\ Insiders.app/Contents/MacOS/Electron
Visual Studio Code - Insiders.app/Contents/MacOS/Electron: Mach-O 64-bit executable arm64

Universal is like this:
app: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64:Mach-O 64-bit executable arm64]
app (for architecture x86_64):	Mach-O 64-bit executable x86_64
app (for architecture arm64):	Mach-O 64-bit executable arm64

universal check can be done like this:
❯ file Visual\ Studio\ Code\ -\ Insiders.app/Contents/MacOS/Electron
Visual Studio Code - Insiders.app/Contents/MacOS/Electron: Mach-O 64-bit executable arm64

Universal is like this:
app: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64:Mach-O 64-bit executable arm64]
app (for architecture x86_64):	Mach-O 64-bit executable x86_64
app (for architecture arm64):	Mach-O 64-bit executable arm64

authors: bpasero chrmarti deepak1556 joaomoreno jrieken kieferrm paulmillr


text:
Tooltip not show when hover codelens

VSCode Version: 1.52.1
OS Version: Windows 10 1909

Steps to Reproduce:

Open codelens-sample of vscode-extension-samples
Run yarn && yarn watch，then press F5 to run extension
Open any folder with some code.
Wait code lens show, then hover one of codelens.

Actual Result:

Is this an expected behavior of vscode extension?
Or is there any configation to show it?

I believe this is expected behavior, however forwarding to @jrieken so he can close

Yes. @TAUnionOtto what tooltip to you expect when hovering over a code lens?

Yes. @TAUnionOtto what tooltip to you expect when hovering over a code lens?

As the code, show Tooltip provided by sample extension maybe suitable I think. @jrieken

Ah, I see. That actually makes sense and would be a simple change

@jrieken I'm looking at contributing to this though I'm fairly new to the vscode repo and having trouble understand how to attach the hover event listener for the code lens feature. Do you mind pointing me to an example in the codebase for doing that?

Can I take a look at this issue and try to work on this?

This is where the dom-nodes for codelens are created: https://github.com/microsoft/vscode/blob/6260e655bc606e204ad51ce5b1cb34216cd36dd3/src/vs/editor/contrib/codelens/codelensWidget.ts#L91. Using  the title attribute on them should do the job

Is the native tooltip sufficient for the fix? @jrieken
Before fix
Windows & MacOS
:-------------------------:

After fix

Windows
MacOS

authors: TAUnionOtto hantatsang isidorn jrieken spetrescu


text:
Extension host terminated unexpectedly -- clean install, latest version

Extension host terminated unexpectedly.
This started happening with the most recent version.  To confirm, I deleted my VS Code application, deleted my .vscode directory, redownloaded the app from the VS Code site, enabled only the SFTP extension and tried to sync with the remote site using the sftp.json that I've been using successfully for weeks.  The extensions host crashed with the message above.  Log message below:
console.ts:137 [Extension Host] (node:68504) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
b @ console.ts:137
abstractExtensionService.ts:466 Extension host terminated unexpectedly. Code:  null  Signal:  SIGSEGV
_onExtensionHostCrashed @ abstractExtensionService.ts:466
log.ts:197   ERR Extension host terminated unexpectedly. The following extensions were running: vscode.microsoft-authentication, vscode.configuration-editing, vscode.extension-editing, vscode.json-language-features, ms-vscode.js-debug, vscode.npm, vscode.debug-auto-launch, vscode.git, liximomo.sftp, vscode.github-authentication, vscode.github, vscode.emmet, vscode.merge-conflict, vscode.testing-editor-contributions
notificationsAlerts.ts:40 Extension host terminated unexpectedly.
onDidChangeNotification @ notificationsAlerts.ts:40

Duplicate of liximomo/vscode-sftp/issues/883.

/causedByExtension - thanks @tamuratak

/causedByExtension - thanks @tamuratak

@gjsjohnmurray it's not caused by the extension(s), but rather a VS Code update (of late) has caused ALL of the extension crashes (plural) that us devs are actually using to sync to servers via FTP/SFTP/SSL etc.

@oberocks there can be many causes for an extension no longer working when VS Code updates to a new version. In my experience as an extension developer, the VS Code team works very hard not to make changes that break published APIs and features. But if an extension is no longer maintained by its author there's always a chance it will stop working at some point. Options include:

Fork the extension and fix it.
Switch to another extension.

Some extensions seem to end up abandoned because others show up and become very popular. Are you familiar with the remote development options described in https://code.visualstudio.com/docs/remote/remote-overview ?

Look that solution
https://github.com/liximomo/vscode-sftp/issues/883#issuecomment-778684682

bs. This is broken. Take responsibility and fix it.

See #116260
Electron update in today's Insiders is supposed to fix this.

@gjsjohnmurray Understood, and many thanks for the suggestion of remote-overview. I had not yet seen that option, which is great, especially considering the rather old-school way of working synced to a FTP - isn't always a fully supported thing.
So, my apologies if I came off as un-empathetic. That's not the case. My concern was just to flag the issue, as in time the OS world would work it's magic - hopefully allowing me to get back to updating VS Code whenever possible and still being able to use our collectively treasured old-school extensions from other underappreciated coders of the ether.
However, please do consider this comment as a plea for VS Code to just add in FTP client functionality with live watchers. It's a really great way to work in some fringe cases. In my case, I make web design systems that are integrated with static site generators - resulting in a ton of files generated and needing to be pushed to a live server to check for responsive and accessibility factors. Old-school FTP methods are by far the most direct way to do this sort of cross-device focused work IMO. I'm pretty sure I'm not the only one that has to work this way these days, but can't confirm that per say lol.
Anyhow, thank you kindly for the update about the electron patch as well. Hopefully I can find time to try out a recent VSC version (but still have the old version that's stable for this extension handy).

authors: DannyCrews cmparrela gjsjohnmurray oberocks tamuratak yasmin-bb


text:
Automatic click on right click button in Explorer menu

VS Code Version: 1.55.2
OS Version: Ubuntu 20.04

I had this problem before, but I think there is only in Explorer now
Steps to Reproduce:

Open Explorer menu
Click on file/folder
If the menu doesn't fit in windows and the menu placed under mouse and click automatic

Dup of some issue assigned to @sbatten

authors: fakhamatia isidorn


text:
Switch function key roles on MAC when visual studio code is in focus

Could we possibly switch the function keys to their standard mappings when visual studio is in focus?
The default/regular keybindings is for the typical OS functions like increasing screen brightness and search function while the user has to press the fn key to switch to the regular function keys.
I noticed that starcraft 2 actually switches the function keys to their standard mapping just as if you changed the settings like here and switches it back to normal when you exit the application. Could we possibly do the same thing while visual studio is in focus?

If you have a Mac with a Touch Bar, this is already possible to configure via

Open System Preferences.app >
Panel ‘Keyboard’ >
Tab ‘Shortcuts’ >
List Item ‘Function Keys’ >
You can add VS Code.app there from the file picker behind the +-button.

Unfortunately, it doesn’t appear like such a setting is available for non-Touch Bar keyboards.

authors: Digital-Nomad redmer


text:
Provide .ipynb file support out of the box

Work items

[x] Built-in extension that ships with VS Code and that can be disabled but not uninstalled
- Support both web and desktop
- Starter code https://github.com/joyceerhl/vscode-jupyter-notebook-serializer
[ ] Built-in support for creating a new Jupyter notebook via the New File... flow
[ ] Remove serializer from ms-toolsai.jupyter

[ ] Reimplement create new and export without serializer https://github.com/microsoft/vscode-jupyter/pull/6756
[x] Delay native notebooks survey notification when users dismiss (eventually remove survey) https://github.com/microsoft/vscode-jupyter/pull/6767
[ ] Do not update workbench.editorAssociations setting based on experiment (VS Code will continue to cache) https://github.com/microsoft/vscode-jupyter/pull/6768

[ ] New Jupyter notebook getting started experience in VS Code

[ ] Recommend Jupyter extension if missing renderers for output mimetypes
[ ] Recommend kernel extensions in order to run code
[ ] Remove existing defunct notification to install Jupyter extension for ipynb files (shows only for json, not for notebook editor UI which is the default experience today)
[ ] Syntax highlighting for ipynb json

We would also want to support syntax highlighting ipynb when it's opened in a text editor. We would need a grammar which can be identical to JSON (but we can't add ipynb as a file ext option for JSON ext otherwise it will break save).

Discussion items from meeting with @DonJayamanne and @roblourens:

Supporting newer versions of nbformat

Not currently necessary but in future this extension will need to be updated fairly regularly as nbformat ships updates

Notebook and cell metadata

The current serializer adds metadata under a custom property
Some of this is done to support .NET Interactive scenarios, e.g. see https://github.com/microsoft/vscode-jupyter/pull/6196
No immediate plans to change this but if we do we should inform .NET Interactive team and others

Compression of cell outputs on save

IIRC Don mentioned doing some compression of outputs on save rather than at the time that the outputs are updated, the built-in serializer will not do this

re

Compression of cell outputs on save
IIRC Don mentioned doing some compression of outputs on save rather than at the time that the outputs are updated, the built-in serializer will not do this

maybe it's related to terminal outputs which we currently compress in notebook controllers, which leads to performance issue. We may want to just do this on save.

@rebornix what do you mean it will "break save" if we call ipynb files JSON?

@roublourens if we call ipynb files JSON, when doing Save As on an untitled Jupyter notebook, the file picker attempts to save it as JSON by default and fails with an error.

@joyceerhl already gave it a good summary. The issues tracking them are:

No syntax highlighting for ipynb https://github.com/microsoft/vscode/issues/122589 and my original fix was adding ipynb to the JSON file extension list, which caused below issue
https://github.com/microsoft/vscode/issues/124918

Quick question: does this essentially mean that if a user has VS Code and the Julia extension installed, they would no longer even need the Jupyter extension to work with Jupyter notebook files?

This means that you wouldn't need the Jupyter extension installed to open ipynb files. Renderers, Jupyter kernels, and other functionality like export are currently still provided through the Jupyter extension.

We have the Julia notebook controller in the Julia extension now, so presumably the whole kernel functionality from the Jupyter extension wouldn't be needed at that point, and it would really only be renderers and export?
I hadn't even considered this scenario, but if we could get the Jupyter Julia Notebook scenario to work without even needing the Jupyter extension that of course would also be great! The less stuff users have to install, the better :)

the whole kernel functionality from the Jupyter extension wouldn't be needed at that point, and it would really only be renderers and export?

That's correct 😊

Are there plans to move the renderers into core as well?

Not currently because the renderers are very large.

re there plans to move the renderers into core as well?

We're looking into  shiping the renderers as a seprate extension, see here https://github.com/microsoft/vscode-internalbacklog/blob/main/plan-master-copies/current/July 2021 - jupyter.md#engineering
If this goes ahead, then Julia would not need Jupyter at all, just the renderer extension

That would be fantastic! I think in that case we would presumably just require the renderer extension as a dep of our extension so that it is always installed if someone installs the Julia extension.
@DonJayamanne the link you posted is private, so I can't look at that.

Oops, sorry forgot about that.

ust require the renderer extension as a dep of our extension so that it is always installed if someone installs the Julia extension.

Hopefully yes

Just one other bit of feedback: the biggest problem for the Julia extension at the moment is that we can't save language and kernelspec info in Jupyter notebooks, see here. This is blocking for us, and for now we have actually disabled the native notebook integration by default via a feature flag in the extension. We originally had hoped to ship the native notebook stuff on Wed as part of our Juliacon announcement, but what we're going to do instead now is ship it but have it disabled by default, and just tell people that if they are ok with notebooks not being saved properly, they can enable the Julia notebook controllers via config. Not great, but as far as I understand it the best we can do at the moment.
I don't understand how this scenario can be unblocked (i.e. whether we need something in VS Code or the Jupyter extension), but it would be fantastic if that could be a priority so that we can actually get the notebook stuff out to everyone :)

@davidanthoff Based on https://github.com/julia-vscode/julia-vscode/pull/2271#discussion_r665912172 it sounds like the Julia extension would be unblocked if the notebook metadata edit API is stabilized, since what you need is the ability to modify the "language_info" and "kernel_info" metadata properties. Is that accurate, and would the Julia extension need anything else?

Yes, exactly! We essentially just need the ability to finish this step.
I'll have a bunch of other feedback around kernel select, but as far as I can tell right now none of that is blocking, I think the metadata stuff is the only thing that I can think of right now that is a blocker on turning the switch to make the notebook functionality on by default.

Filed an issue that should unblock Julia (with a generic way to update metadata) https://github.com/microsoft/vscode/issues/129595

Great, thanks!

Closing, the only remaining task is the getting started experience which is covered by other issues

authors: DonJayamanne davidanthoff joyceerhl rebornix roblourens


text:
won't run chrome

Issue Type: Performance Issue
the visual studio won't run the projects on the chrome wed engine
VS Code version: Code 1.61.2 (6cba118ac49a1b88332f312a8f67186f7f3c1643, 2021-10-19T14:57:20.575Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz (8 x 2304)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.73GB (9.52GB free)

Process Argv
--crash-reporter-id a3841a29-5988-472d-9607-6e751b3a388e

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    1	    83	 17364	code main
    0	    85	  2140	   shared-process
    0	    74	 21956	     ptyHost
    0	    68	  8816	       C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
    0	     6	 18244	       console-window-host (Windows internal process)
    0	   142	  2688	   window (my_list.html - grishmon - Visual Studio Code)
    0	   111	 18184	     extensionHost
    0	    93	 14168	       "C:\Users\grishmon\AppData\Local\Programs\Microsoft VS Code\Code.exe" "c:\Users\grishmon\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\html-language-features\server\dist\node\htmlServerMain" --node-ipc --clientProcessId=18184
    0	    70	 14780	       "C:\Users\grishmon\AppData\Local\Programs\Microsoft VS Code\Code.exe" "c:\Users\grishmon\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\json-language-features\server\dist\node\jsonServerMain" --node-ipc --clientProcessId=18184
    0	    67	 23084	     watcherService
    0	   153	  4268	   gpu-process
    1	    76	 12888	   window (Issue Reporter)
    0	    24	 18480	   crashpad-handler
    0	    36	 21604	   utility

Workspace Info
|  Window (my_list.html - grishmon - Visual Studio Code)
|    Folder (grishmon): 21 files
|      File types: html(8) json(1) js(1) txt(1) scss(1) JPG(1) css(1)
|      Conf files: launch.json(1)
|      Launch Configs: pwa-chrome(3) node-terminal;

Extensions (1)

Extension
Author (truncated)
Version

remote-wsl
ms-
0.58.3

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
pythonvspyt639:30300192
pythontb:30283811
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
pythonvsuse255:30340121
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
vsccppwtct:30382698
pythonvssor306:30344512
bridge0708:30335490
pygetstartedt3:30385195
dockerwalkthru:30377721
bridge0723:30353136
pythonrunftest32:30373476
pythonf5test824:30373475
javagetstartedt:30364666
pythonvspyt187:30373474
vsqsis300:30386381
vsaa593:30376534
vssld246cf:30386378

vscode
doesn't debugging live on chrome
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations":
[
{
"name": "Attach to Chrome",
"port": 9222,
"request": "attach",
"type": "pwa-chrome",
"webRoot": "${workspaceFolder}"
},
{
"command": "npm start",
"name": "Run npm start",
"request": "launch",
"type": "node-terminal"
},
{
"name": "Attach to Chrome",
"port": 9222,
"request": "attach",
"type": "pwa-chrome",
"webRoot": "${workspaceFolder}"
},
{
"name": "Launch Chrome",
"request": "launch",
"type": "pwa-chrome",
"url": "http://localhost:8080",
"webRoot": "${workspaceFolder}"
},
]

}

@what exactly are you trying to do`?
Please provide reproducible steps.

authors: grishmon weinand


text:
Unable to resolve your shell env **(code null, signal SIGSEGV)

Does this issue occur when all extensions are disabled?: Yes/No
yes

VS Code Version:
OS Version:

Steps to Reproduce:

open vscode

I found that I can type code in my Iterm.app to open vscode and everything seems ok.

2 reports of SIGSEGV on mac universal build when resolving shell environments.

I have this problem now too after upgrading to Monterey (12.1) from Big Sur (11.6.1) on Intel (still using bash). I didn't change anything else, so perhaps it's Monterey-related.

Sorry missed this thread, can you give our exploration builds a try which comes a newer runtime version and see if the problem persists. Thanks!
MacOS Universal Download

I tried the exploration build you linked, but I'm afraid the problem is still present.
The exploration build I tried:
Version: 1.64.0-exploration (Universal)
Commit: 8a3f490b5f148653b87327b53a26550f695939f5
Date: 2022-01-25T10:40:09.616Z
Electron: 16.0.7
Chromium: 96.0.4664.110
Node.js: 16.9.1
V8: 9.6.180.21-electron.0
OS: Darwin x64 21.2.0

The main.log has lines like the following:
[2022-01-26 14:53:22.982] [main] [info] Starting extension host with pid 38016 (fork() took 4 ms).
[2022-01-26 14:53:22.983] [main] [info] ExtensionHostStarterWorker.start() took 11 ms.
[2022-01-26 14:53:23.237] [main] [error] RequestService#request resolving shell environment failed {}
[2022-01-26 14:53:44.375] [main] [info] Extension host with pid 38016 exited with code: 0, signal: null.
[2022-01-26 14:53:44.468] [main] [error] Unable to resolve your shell environment: Unexpected exit code from spawned shell (code null, signal SIGSEGV)

some of which might be related.
For comparison, the data from the stable release:
Version: 1.63.2 (Universal)
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:37:28.172Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 21.2.0

and main.log snippet:
[2022-01-26 15:05:15.701] [main] [error] Unable to resolve your shell environment: Unexpected exit code from spawned shell (code null, signal SIGSEGV)
[2022-01-26 15:05:16.267] [main] [info] Starting extension host with pid 41822 (fork() took 4 ms).
[2022-01-26 15:05:16.564] [main] [error] Unable to resolve your shell environment: Unexpected exit code from spawned shell (code null, signal SIGSEGV)
[2022-01-26 15:05:16.749] [main] [error] RequestService#request resolving shell environment failed {}

After having another application segfault, I found out through the crash report, that these crashes are caused by me setting DYLD_LIBRARY_PATH during shell initialisation. Removing that altogether fixes both VSCode and the other application (and also VSCode's exploration build).
The application depending on the setting of DYLD_LIBRARY_PATH (mysql server) also still seems to run fine; apparently this setting was useful in the past, but it is no longer necessary.
I've searched a bit why this started happening after upgrading to Monterey, and my hypothesis is that SIP now handles DYLD_LIBRARY_PATH settings stricter than before. I didn't even know it was 'under SIP', but apparently it is.

Thanks for confirming, closing as issue is outside the core.

authors: Ramblestsad Tyriar deepak1556 gerardkok


text:
Terminal command decorations: When I move the terminal to a side panel, the previous decorations stop working.

Testing #143433

Run command a decoration is created, when you click it show the options ro run again or copy the output.
Move terminal to a side panel.
Move back to the previous panel.
Clicking on the decoration now doesn't show anything, or do anything.

I believe this is now fixed in the latest insiders. Can you pls confirm?


text:
filter problems text area keeps stealing focus

I'm sure I need to provide some sort of trace, so please give me the instructions for that, but in the meantime here's what I know:

I've tried using the extension bisect feature and it still seems to be a problem even when no extensions are running.
It doesn't happen in every project. The one that it occurs in most often is rather large and it happens every minute or so, but in a smaller project it happens almost never
Both projects are typescript based

Happy to provide whatever additional info is required. Thanks!

Can you please record a video and share with us?


text:
Expanding windows destroys my arrangement

Does this issue occur when all extensions are disabled?: Yes
So I dont know how to explain this but while I was using split editor I found out that selecting small pane will cause it to expand and take the maximum area of the split editor.
Steps to Reproduce:

Split the two tabs left and right and add another tab below the right one
Arrange the tabs and select on main tab then move to small tab
Here's video for explanation

VS Code Version:

OS Version: Mac OS Monterey 12.4

The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.
Happy Coding!

authors: SamXtroyer VSCodeTriageBot


text:
Unable to use due to performance issues on Ubuntu 20.04

Issue Type: Bug
Open VS Code and try editing a text file.
The perfomance is very slow and unresponsive. The top window menu responds relatively fast. The slow part is the editor itself. Scrolling is very laggy and unresponsive.
This issue is new for me and VS Code was working fine until the last two updates I did. Then the performance issues started. Reinstalling did fix the issue initially, but now the next day I started VS code and the issue is back.
I am using Ubuntu 20.04.
Observations:

Devtools console has this warning:
"DevTools failed to load source map: Could not load content for https://ticino.blob.core.windows.net/sourcemaps/3b889b090b5ad5793f524b5d1d39fda662b96a2a/node_modules/@vscode/vscode-languagedetection/dist/lib/index.js.map: Fetch through target failed: Target not supported; Fallback: Unknown error"

When I run VSCode's built-in CPU process monitor alongside editing the text file, performance issue goes away. But as soon as I close the monitor it comes back.

What I've tried:

I uninstalled any extensions that I thought could cause issues.
I updated and reinstalled VS Code. I am running version 1.69.2 on Ubuntu 20.04. Here is the complete VS code version info:

Version: 1.69.2
Commit: 3b889b090b5ad5793f524b5d1d39fda662b96a2a
Date: 2022-07-18T16:14:10.636Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Linux x64 5.14.0-1045-oem
VS Code version: Code 1.69.2 (3b889b090b5ad5793f524b5d1d39fda662b96a2a, 2022-07-18T16:14:10.636Z)
OS version: Linux x64 5.14.0-1045-oem
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz (8 x 2300)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
1, 0, 0

Memory (System)
31.14GB (20.00GB free)

Process Argv
--unity-launch --crash-reporter-id 659a1ee4-e755-4056-8658-e418c204c36d

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

Extensions (14)

Extension
Author (truncated)
Version

jest-snippets
and
1.8.0

vscode-eslint
dba
2.2.6

es7-react-js-snippets
dsz
4.4.3

gitlens
eam
12.1.2

prettier-vscode
esb
9.5.0

vscode-firefox-debug
fir
2.9.8

vscode-peacock
joh
4.0.1

prettify-json
moh
0.0.3

vscode-docker
ms-
1.22.1

remote-containers
ms-
0.241.3

vscode-jest
Ort
4.6.0

vscode-sort-json
ric
1.20.0

partial-diff
ryu
1.4.3

jinja
who
0.0.8

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes516:30244333
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
pylanb8912cf:30529770
vsclangdc:30486549
841h4636:30532337

/needsPerfInfo

Thanks for creating this issue regarding performance! Please follow this guide to help us diagnose performance issues: https://github.com/microsoft/vscode/wiki/Performance-Issues
Happy Coding!

Maybe also use Start Extension Bisect command to investigate.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


text:
Add onWillSaveNotebookDocument

This would match onWillSaveTextDocument but for notebook docs instead
As parts of this, we should allow extensions to perform notebook edits before the save happens

Is anyone asking for this specifically?

@Yoyokrazy and I discussed as a way to clean up unused attachments in notebooks. For this we need to loop through all attachments in the notebook and remove them from the metadata if they are not referenced in the cell's markdown
We also talked about cleaning up these attachments when the notebook is closed. However that means we would need an api to modify notebooks when they are closed, which raises many more questions

@jrieken I am asking for it.
Related PR/issue: https://github.com/halcyon-tech/vscode-ibmi/pull/818#issuecomment-1220733058

@bpasero do we have a generic save participants for any working copy? onWillSaveTextDocument is done via ITextFileService.files.addSaveParticipant but for notebook we need something same, same but different

@jrieken yeah I think I had added that even though no client yet, can you try via IWorkingCopyFileService.addSaveParticipant and IWorkingCopyFileService.runSaveParticipants.

Note from API discussion: when looking into this, we should also look into format on save for notebooks

We would use this in nbdev (tracking here: https://github.com/fastai/nbdev/issues/952). We remove unneeded metadata from notebooks on-save, for cleaner diffs and less chance of merge conflicts. It's very easy to implement with Jupyter Notebook/Lab via ContentsManager.pre_save_hook. We add this to the relevant config file:
def nbdev_clean_jupyter(**kwargs):
    try: from nbdev.clean import clean_jupyter
    except ModuleNotFoundError: return
    clean_jupyter(**kwargs)

c.ContentsManager.pre_save_hook = nbdev_clean_jupyter

How could we get similar behaviour for our VSCode users? Is there any workaround while onWillSaveNotebookDocument doesn't exist?

Latest API https://insiders.vscode.dev/github/microsoft/vscode/blob/d3c2dcacf39c2a25c06547945ae13da4c8cf9f82/src/vscode-dts/vscode.proposed.notebookDocumentWillSave.d.ts

Based on the comment from @mjbvz , we can simply the API to
	export interface NotebookDocumentWillSaveEvent {
		/**
		 * A cancellation token.
		 */
		readonly token: CancellationToken;

		/**
		 * The document that will be saved.
		 */
		readonly document: NotebookDocument;

		/**
		 * The reason why save was triggered.
		 */
		readonly reason: TextDocumentSaveReason;

		waitUntil(thenable: Thenable<readonly WorkspaceEdit>): void;

		waitUntil(thenable: Thenable<any>): void;
	}

Two changes:

Reuse TextDocumentSaveReason despite the name is talking about TextDocument, it's generic and applied to all documents
Use single WorkspaceEdit as it can contain multiple edits already, also we can validate if the workspace edit is only applied in the target notebook document or its cells

The API is finalized and merged into vscode.d.ts.

authors: bpasero jrieken mjbvz rebornix seeM worksofliam


text:
program run issue

Type: Performance Issue
crome browser not opening when im run code
every time i have to open manually please do need fully
VS Code version: Code 1.70.2 (e4503b30fc78200f846c62cf8091b76ff5547662, 2022-08-16T05:35:13.448Z)
OS version: Windows_NT x64 10.0.22000
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-7020U CPU @ 2.30GHz (4 x 2304)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.91GB (2.53GB free)

Process Argv
--crash-reporter-id 3aa938bf-96e3-47e8-b88d-c1ddf630590e

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    1	   103	 19272	code main
    0	   124	  6304	   extensionHost
    0	    89	 17836	     "C:\Users\saipr\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node "c:\Users\saipr\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\json-language-features\server\dist\node\jsonServerMain" --node-ipc --clientProcessId=6304
    0	   155	 15324	   window (Visual Studio Code)
    4	    91	 18508	   issue-reporter
    0	   110	 19640	   shared-process
    0	    74	  1436	     ptyHost
    0	    73	 17944	     fileWatcher
    0	    41	 20664	   utility-network-service
    0	    26	 21132	   crashpad-handler
    2	   166	 21332	   gpu-process

Workspace Info
;

Extensions (1)

Extension
Author (truncated)
Version

code-runner
for
0.11.8

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
wslgetstarted:30449410
cppdebug:30492333
pylanb8912:30545647
vsclangdf:30486550
c4g48928:30535728
hb751961:30543456
dsvsc012:30540252
azure-dev_surveyone:30548225

Have you tried the Live Preview extension?
https://marketplace.visualstudio.com/items?itemName=ms-vscode.live-server

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

authors: VSCodeTriageBot codersaiprakash weinand


text:
VSC Terminal reports error: sed: illegal option -- r

Ever since latest release, but not beforehand, VSC Terminal reports:
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
on start-up and whenever a command is issued to VSC Terminal.
This does not occur in a macOS (non-VSC) Terminal window.

/duplicate
Please search for the term 'sed'

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!

authors: VSCodeTriageBot gjsjohnmurray posfr2


text:
The Terminal panel is always opened on the first launch

Type: Bug
Hey,
I noticed that since the release 1.73 the terminal panel on the bottom is always opened whenever I launch VSCode for the first time after booting the OS and every time I have to close it with mouse because the keyboard command to show/hide terminal panel is ignored. Is there any configuration flag which commands to hide it by default?
Steps to reproduce:

Launch VSCode for the first time

The terminal panel is opened by default (screenshot bellow for reference)

Press your keyboard combination for the command "View: Toggle Terminal"

The command is ignored

Take your mouse and click the cross to close the panel

Press again your keyboard combination for the command "View: Toggle Terminal"

Now it mysteriously works as expected

Thanks
VS Code version: Code 1.73.1 (6261075646f055b99068d3688932416f2346dd3b, 2022-11-09T02:22:48.959Z)
OS version: Darwin arm64 22.1.0
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Apple M1 (8 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
2, 2, 1

Memory (System)
16.00GB (0.37GB free)

Process Argv

Screen Reader
no

VM
0%

Seems its already fixed in vscode insiders as I cannot repro there

Can you please check disabling all extensions and reproduce it?

Can you please check disabling all extensions and reproduce it?

Alright, I turned them off all together and turned on one by one and now the bug just disappeared.
I don't know what to add to my complains. If you feel ok with this strange behaivour you may close this ticket.
Thanks for the help.

Ok weird. Closing it for now because there are no consistent steps to repro. Please reopen and provide steps and necessary info when you see it again. Thanks.


text:
--extensions-dir option to code cli ignored in 1.74.0

Type: Bug
Steps to reproduce

Make sure you have an extension installed in VSCode (any extension)
Run mkdir foo to make an empty directory
Run mkdir bar to make an empty directory
Run code --extensions-dir foo bar to open directory bar in VSCode using the empty directory foo as the extensions dir
Run "Extensions: Show Enabled Extensions" command from the command palette in the newly opened workspace

Expected behaviour
There should be no extensions in the list, because code was called with an empty extensions dir
Actual behaviour
It shows the full list of extensions from the default extension dir.  Also, I can confirm that these extensions are actually activated (ie not just displayed in the list)
Notes

This worked fine in 1.73.1
Interestingly, running code --extensions-dir foo --list-extensions lists the correct extensions

System info
VS Code version: Code 1.74.0 (5235c6bb189b60b01b1f49062f4ffa42384f8c91, 2022-12-05T16:43:37.594Z)
OS version: Darwin x64 21.5.0
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 2, 2

Memory (System)
32.00GB (4.14GB free)

Process Argv
--crash-reporter-id 99d35f96-61a9-461b-a60d-f915d32f3eee

Screen Reader
no

VM
0%

Extensions (102)

Extension
Author (truncated)
Version

better-comments
aar
3.0.2

Bookmarks
ale
13.3.1

tsl-problem-matcher
amo
0.6.2

andreas-talon
And
3.0.0

vscode-neovim-hacked
asv
0.0.85

agda-mode
ban
0.3.11

markdown-checkbox
bie
0.4.0

markdown-mermaid
bie
1.16.0

mermaid-markdown-syntax-highlighting
bpr
1.5.0

vscode-tailwindcss
bra
0.9.1

turbo-console-log
Cha
2.6.2

path-intellisense
chr
2.8.3

regex
chr
0.4.0

doxdocgen
csc
1.4.0

vscode-eslint
dba
2.2.6

vscode-dash
dee
2.4.0

dendron-markdown-shortcuts
den
0.12.1

chmod
dle
1.1.1

githistory
don
0.6.19

xml
Dot
2.5.1

viml
dun
0.1.7

gitlens
eam
13.1.1

EditorConfig
Edi
0.16.4

prettier-vscode
esb
9.10.3

shell-format
fox
7.2.2

remotehub
Git
0.48.0

vscode-pull-request-github
Git
0.56.0

mdmath
goe
2.7.4

vscode-graphql
Gra
0.8.4

vscode-graphql-execution
Gra
0.1.6

vscode-graphql-syntax
Gra
1.0.5

rest-client
hum
0.25.1

elixir-ls
Jak
0.12.0

better-cpp-syntax
jef
1.17.2

cmake-language-support-vscode
jos
0.0.7

jq-syntax-highlighting
jq-
0.0.2

vscode-tree-sitter-query
jri
0.0.1

bash-ide-vscode
mad
1.22.0

syntax-project-pbxproj
mar
0.1.3

rainbow-csv
mec
3.5.0

git-graph
mhu
1.30.0

vscode-edits-history
mis
0.1.6

lalrpop-highlight
mnx
0.0.1

vscode-talonscript
mro
0.3.13

vscode-docker
ms-
1.23.2

csharp
ms-
1.25.2

vscode-dotnet-runtime
ms-
1.6.0

black-formatter
ms-
2022.7.13271013

isort
ms-
2022.9.13271012

python
ms-
2022.20.1

vscode-pylance
ms-
2022.12.21

jupyter
ms-
2022.11.1003412109

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.12

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

remote-containers
ms-
0.266.1

remote-ssh
ms-
0.94.0

remote-ssh-edit
ms-
0.84.0

azure-repos
ms-
0.24.0

cmake-tools
ms-
1.12.27

cpptools
ms-
1.13.7

cpptools-extension-pack
ms-
1.3.0

remote-explorer
ms-
0.0.3

remote-repositories
ms-
0.26.0

vscode-github-issue-notebooks
ms-
0.0.128

vsliveshare
ms-
1.0.5788

vsliveshare-audio
ms-
0.1.91

vscode-react-native
msj
1.10.0

vscode-paste-image
mus
1.0.4

java-prettier-formatter
mwp
0.1.5

autodocstring
njp
0.6.1

angular-console
nrw
17.27.1

command-server
pok
0.8.2

cursorless
pok
0.26.522

git-branchless
pok
0.0.1

parse-tree
pok
0.24.0

ruby
reb
0.28.1

LiveServer
rit
5.7.9

format-code-action
roh
0.1.0

rust-analyzer
rus
0.3.1317

multi-command
ryu
1.6.0

scala
sca
0.5.6

metals
sca
1.20.0

vscode-scheme
sjh
0.4.0

vscode-fileutils
sle
3.5.0

sourcery
sou
1.0.1

rewrap
stk
1.16.3

vscode-open-in-github
sys
1.17.0

even-better-toml
tam
0.19.0

rest-book
tan
6.2.1

vscode-lua
tri
0.12.4

cmake
twx
0.0.17

commands
use
1.6.0

intellicode-api-usage-examples
Vis
0.2.6

vscodeintellicode
Vis
1.2.29

vscodeintellicode-completions
Vis
1.0.20

vscode-icons
vsc
12.0.1

vscode-alternate-file
wil
0.3.1

vscode-ruby
win
0.28.0

JavaScriptSnippets
xab
1.8.0

type-challenges
YRM
1.10.0

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vscaac:30438847
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848cf:30577861
nodejswelcome1cf:30587006
3biah626:30602489
gswce1:30612156
iaj6b796:30613358
dbltrim-noruby:30604474
f6dab269:30613381
fim-prod:30623723
vscsbc:30628655

I am not able to reproduce this. May I know if you have enabled profiles in stable?

Strange.  I do not have profiles enabled; here are my settings in case helpful https://github.com/pokey/dotfiles/blob/d9103190ac6bc32fcb1a5b875c242b3a0feeebf6/vscode/settings.json

By any chance, you have extensions.json file in the same directory as settings.json ?

Hey, I'm having the same issue here. On 1.73.1 it worked, on 1.74.1 it feels like --extensions-dir is ignored.
This command returns an empty list for 1.74.1, and on 1.73.1 it lists the extensions:
$ code --extensions-dir /usr/share/vscode-extensions --list-extensions

Before, vscode was used to install the extensions to this directory, via:
$ code --extensions-dir /usr/share/vscode-extensions --install-extension <ext>

By any chance, you have extensions.json file in the same directory as settings.json ?

Nope

Having same issue (1.74.1). Discovered on both

Linux debian 5.10.0
Linux ubuntu 22.10 (Kinetic Kudu)

I've created a minimal repo to demonstrate the issue in my case of extension development.
This repo consists of the default boilerplate for a vscode extension generated using these instructions with the following changes to specify the extensions dir.
I would expect that when I startup the extension development host using the shortcut fn+f5; that the host would not contain any extensions due to the fact that I have set the --extensions-dir to the empty directory at ./vscode-test/extensions in the launch.json config. Instead all of my personal extensions appear in the development environment. Furthermore; if I manually install additional extensions to ./vscode-test/extensions/ they do not appear in the extensions development host.

@pokey @rtpt-alexanderneumann Can you please try following steps and see if it fixes for you?

Open the extensions installation folder
Delete the files extensions.json and .init-default-profile-extensions
Restart VS Code

@jeswr I think you are having a different issue related to debug launches. Please file a separate issue.

Didn't seem to help: I deleted both files and am still seeing the same issue

@pokey Can you please re-describe the problem you are seeing and what steps you are following?

I'm sorry but I'm not sure how to make the description from the top of the issue clearer.  Is one of those 5 steps in particular not clear?

It does for me. I tried following:
code --extensions-dir ~/work/testing/setup/extensions-dir --verbose
And I can see code launched with different extensions dir as shown in the main log

Can you please try the same and share the log?

I'm here sorry I got tied up with a few other things I am NEW to this and it is a learning process trying to catch all the fine line details in between!  I am currently branching into my own part of merchandising so this part is new to me!

@sandy081 Removing both files (.init-default-profile-extensions and extensions.json) fixes it. VSCode creates both files anew.
I've diffed the content of extensions.json and I can see that the paths contained for each extension are different. Before (non-working), the paths were incorrect (pointing to a temporary directory that I used to install the extensions). After, the paths are correct.
In previous versions of VSCode, there was no extensions.json in that directory. In newer versions, VSCode insists on writing one, and fails if it cannot do that (as it is for our directory):
$ code --extensions-dir /usr/share/vscode-extensions --list-extensions
Unable to write file '/usr/share/vscode-extensions/extensions.json' (NoPermissions (FileSystemError): Error: EACCES: permission denied, open '/usr/share/vscode-extensions/extensions.json')

Our solution (for now) is to make sure that the paths in extensions.json are correct.
Reproducible example:
$ mkdir /tmp/extdir

$ code --extensions-dir /tmp/extdir --install-extension golang.go
[...]
Extension 'golang.go' v0.37.0 was successfully installed.

$ code --extensions-dir /tmp/extdir --list-extensions
golang.go

$ mv /tmp/extdir /tmp/other-extdir

$ code --extensions-dir /tmp/other-extdir --list-extensions
[empty]

$ jq . /tmp/other-extdir/extensions.json
[
  {
    "identifier": {
      "id": "golang.go",
      "uuid": "d6f6cfea-4b6f-41f4-b571-6ad2ab7918da"
    },
    "version": "0.37.0",
    "location": {
      "$mid": 1,
      "fsPath": "/tmp/extdir/golang.go-0.37.0",
      "path": "/tmp/extdir/golang.go-0.37.0",
      "scheme": "file"
    },
    "metadata": {
      "id": "d6f6cfea-4b6f-41f4-b571-6ad2ab7918da",
      "publisherId": "dbf6ae0a-da75-4167-ac8b-75b4512f2153",
      "publisherDisplayName": "Go Team at Google",
      "targetPlatform": "undefined",
      "isApplicationScoped": false,
      "updated": false,
      "isPreReleaseVersion": false,
      "installedTimestamp": 1671619270536,
      "preRelease": false
    }
  }
]

# fix paths
$ sed -i 's,/tmp/extdir,/tmp/other-extdir,g' /tmp/other-extdir/extensions.json

# works again:
$ code --extensions-dir /tmp/other-extdir --list-extensions
golang.go

# remove the files and make the dir r/o
$ rm /tmp/other-extdir/extensions.json /tmp/other-extdir/.init-default-profile-extensions
$ chmod u-w /tmp/other-extdir

$ code --extensions-dir /tmp/other-extdir --list-extensions
Unable to write file '/tmp/other-extdir/extensions.json' (NoPermissions (FileSystemError): Error: EACCES: permission denied, open '/tmp/other-extdir/extensions.json')

Can you please try the same and share the log?

➜ code --extensions-dir .vscode-sandbox/extensions --verbose ~/vscode-test
[main 2022-12-21T12:32:44.838Z] [File Watcher (node.js)] Request to start watching: /Users/pokey/Library/Application Support/Code/User (excludes: <none>, includes: <all>),/Users/pokey/Library/Application Support/Code/User/settings.json (excludes: <none>, includes: <all>)
[main 2022-12-21T12:32:44.855Z] Sending env to running instance...
[main 2022-12-21T12:32:44.858Z] [File Watcher (node.js)] correcting a path to watch that seems to be a symbolic link or wrong casing (original: /Users/pokey/Library/Application Support/Code/User/settings.json, real: /Users/pokey/pokey-home-files/vscode/settings.json)
[main 2022-12-21T12:32:44.861Z] [File Watcher (node.js)] Started watching: '/Users/pokey/pokey-home-files/vscode/settings.json'
[main 2022-12-21T12:32:44.863Z] [File Watcher (node.js)] Started watching: '/Users/pokey/Library/Application Support/Code/User'
[main 2022-12-21T12:32:44.907Z] Sent env to running instance. Terminating...
[main 2022-12-21T12:32:44.907Z] Lifecycle#kill()
[main 2022-12-21T12:32:44.907Z] Lifecycle#onWillShutdown.fire()

Note that this was after removing extensions.json and .init-default-profile-extensions from .vscode-sandbox/extensions (the extensions dir)

@pokey Do you have vscode running while you execute this command?
code --extensions-dir .vscode-sandbox/extensions --verbose ~/vscode-test

Yes I run it from the integrated terminal.  The same issue also occurs when I run VSCode from a launch config (the issue described in https://github.com/microsoft/vscode/issues/169734)

OK. As mentioned in the issue #169734, this was working by chance before. Extensions UI and Running Extensions are completely disconnected because both of them are using two different extensions directories. For this use case, I would recommend to start using our new Profiles feature so that it works flawlessly unlike before  -https://code.visualstudio.com/updates/v1_71#_settings-profiles

I can confirm that settings profiles solve the issue for me.  Thanks!


text:
"Reveal in Explorer View" misbehaves with out-of-workspace files

Current behavior: When the user selects "Reveal in Explorer View" from the context menu of a non-workspace file, the file is not always revealed in the Explorer View (for any reasonable definition of the word "reveal").
Expected behavior: When the user selects "Reveal in Explorer View" from the context menu of a file, the file is revealed in the Explorer View.

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.73.1 (and source code reviewed from the current main branch 7f65f0213caa93be075fedb6ce87885a4ce56eab)
OS Version: Linux x64

Steps to Reproduce:

Open a folder or workspace, and open some files from there (e.g., foo.c and foo.h).
Open a file which is not in the folder or workspace (e.g., /usr/include/stdio.h).
While a workspace file (e.g., foo.h) is active, right-click the non-workspace file and select "Reveal in Explorer View":

Observe how the non-workspace file is not revealed in the Explorer View. Instead, the active workspace file is highlighted:

The expected behavior could potentially be to "partially highlight" the non-workspace file like this:

The relevant section in the source code:
https://github.com/microsoft/vscode/blob/7f65f0213caa93be075fedb6ce87885a4ce56eab/src/vs/workbench/contrib/files/browser/fileCommands.ts#L330-L343

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.74.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Reveal in explorer view does not act on altering the open editors view. You can see this by repeating the steps described but what with a file in the workspace.

The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.
Happy Coding!

@lramos15 Please read the issue, and your response to it, a bit more carefully before closing. This issue is specifically about non-workspace files. Files in the workspace work as expected.
I added more verbose descriptions of the observed and expected behaviors to the beginning of the issue. These are further elaborated below.
Currently, when "Reveal in Explorer View" is applied to a non-workspace file, then, if applicable, the Open Editors View is expanded and the Open Editors View also gets the focus. No file-specific actions on the Open Editors View, or any other view, are taken. This is evident from the piece of code that I linked above.
If a context menu item for a file says "Reveal in Explorer View", then the expected behavior is - guess what - to reveal that file in the Explorer View. "No action" is not the expected behavior. Revealing another file is not the expected behavior.
In the third screenshot, I proposed one potential way to reveal a non-workspace file in the Open Editors View which is part of the Explorer View. I don't know the exact term for "partially highlighting" or "pre-selecting" a file, but what I propose can be emulated by switching focus to the Open Editors View and pressing up or down arrow keys.
There may be more appropriate ways to implement expected behavior. Moreover, even with the proposed approach, one should also ensure that the scrollable area of the Open Editors View is adjusted such that the file becomes visible. This automatically happens when the ordinary select method is applied (as in line 334 of the code), but I'm not sure if the proposed "pre-selection" unconditionally brings the file into the view of a scrollable area. I consider visibility as the very minimum requirement for fulfilling the expected behavior when something is "revealed".
If none of this is implementable, then the context menu item should be removed.

@lramos15 Are you able to understand or do you still need more help?

I propose we just disable the entry for out of workspace files as splitting the selection and focus can become very confusing.
cc @bpasero for thoughts.


text:
Option to configure tsserver to use nodejs installed locally

To get around the memory ceiling enforced by electron (https://github.com/microsoft/vscode/issues/127105), how about we add an option to let us specify a nodejs installed locally (instead of relying on the builtin electron one).
The eslint plugin does this by having an option called eslint.runtime, so theoretically we could do the same, but not sure if I'm missing anything here.

The same has been proposed here: https://github.com/microsoft/vscode/issues/151245#issuecomment-1151377537

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


text:
Source Control auto refresh every 5 seconds

Type: Bug
I cloned my repo by clicking Clone Repositary button in the Source Control tab. However by just leaving my cursor focus on my file, the Source Control tab auto refreshes every 5 seconds. You can see the Git Output:
2023-03-21 17:11:05.467 [info] > git config --get commit.template [93ms]
2023-03-21 17:11:05.481 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [93ms]
2023-03-21 17:11:06.357 [info] > git status -z -uall [862ms]

Turn off git.autorefresh can "solve" this issue.
Is this a normal behavior? Why would vscode auto refreshs in such a short time? There's no such issue with my another repositary which is very simple.
I see that another user also report this #175303.
I think this issue or feature is included in 1.75.1. I tried 1.74.3 and 1.68.1, they don't have such issue.
VS Code version: Code 1.76.2 (ee2b180d582a7f601fa6ecfdad8d9fd269ab1884, 2023-03-14T17:55:54.936Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 9 4900HS with Radeon Graphics          (16 x 2994)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
15.42GB (9.70GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewvextcfv2:30681851
azure-dev_surveyone:30548225
pyindex848:30662994
nodejswelcome1cf:30587006
2e4cg342:30602488
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
vsctsb:30677850
vscodedisable:30660115
azdwalk:30687957
pythonms35cf:30686773

@iouzzrj, that does not sound like normal behaviour. Could you please execute the "Developer: Set Log Level..." command from the command palette, select "Git" from the extension list, and pick "Trace". Reproduce the issue, and then share the contents of the git output window. Thanks!

@iouzzrj, thank you! I will investigate the issue and get back to you.

I am seeing the same think -- every 5 seconds the Git extension runs:
2023-05-05 15:08:09.913 [info] > git config --get commit.template [43ms]
2023-05-05 15:08:09.920 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [46ms]
2023-05-05 15:08:09.979 [info] > git status -z -uall [54ms]
2023-05-05 15:08:15.040 [info] > git config --get commit.template [41ms]
2023-05-05 15:08:15.048 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [45ms]
2023-05-05 15:08:15.106 [info] > git status -z -uall [54ms]
2023-05-05 15:08:20.168 [info] > git config --get commit.template [44ms]
2023-05-05 15:08:20.177 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [48ms]
2023-05-05 15:08:20.238 [info] > git status -z -uall [57ms]

I haven't found what triggers this -- my guess is that I have Git setup with file watching and maybe the Git extension is seeing that cache get updated (but its still odd that it would happen every 5s).
In GitLens, I crafted my file watchers (wish we had excludes), to avoid detecting changes in the fsmonitor--daemon/*  folder, since that is what Git updates. Also, this reproduces for me with and without GitLens (so there isn't some odd interaction there).

@eamodio, could you please enable trace logging for the git extension:

Invoke the "Developer: Set Log Level..." command from the command palette
Select "Git" from the list of extensions, and then "Trace"
Share the contents of the git output window

@lszomoru here you go, and it proves that it is the Git file watcher, as fsmonitor--daemon is where it stores that state
2023-05-10 01:49:51.828 [trace] Operation end: Status (blocking: false, readOnly: false; retry: false; showProgress: true)
2023-05-10 01:49:51.904 [debug] [wt] Change: c:\Users\Eric\code\gitkraken\vscode-gitlens\.git\fsmonitor--daemon\cookies\10552-6179
2023-05-10 01:49:54.283 [trace] [svte] Scan visible text editors. autoRepositoryDetection=true
2023-05-10 01:49:56.831 [trace] Operation start: Status (blocking: false, readOnly: false; retry: false; showProgress: true)
2023-05-10 01:49:56.869 [info] > git config --get commit.template [33ms]
2023-05-10 01:49:56.876 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [34ms]
2023-05-10 01:49:56.918 [info] > git status -z -uall [39ms]
2023-05-10 01:49:56.919 [trace] Operation end: Status (blocking: false, readOnly: false; retry: false; showProgress: true)
2023-05-10 01:49:56.988 [debug] [wt] Change: c:\Users\Eric\code\gitkraken\vscode-gitlens\.git\fsmonitor--daemon\cookies\10552-6180
2023-05-10 01:50:01.927 [trace] Operation start: Status (blocking: false, readOnly: false; retry: false; showProgress: true)
2023-05-10 01:50:01.964 [info] > git config --get commit.template [33ms]
2023-05-10 01:50:01.972 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [37ms]
2023-05-10 01:50:02.015 [info] > git status -z -uall [38ms]
2023-05-10 01:50:02.016 [trace] Operation end: Status (blocking: false, readOnly: false; retry: false; showProgress: true)
2023-05-10 01:50:02.086 [debug] [wt] Change: c:\Users\Eric\code\gitkraken\vscode-gitlens\.git\fsmonitor--daemon\cookies\10552-6181
2023-05-10 01:50:07.028 [trace] Operation start: Status (blocking: false, readOnly: false; retry: false; showProgress: true)
2023-05-10 01:50:07.063 [info] > git config --get commit.template [31ms]
2023-05-10 01:50:07.070 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [33ms]
2023-05-10 01:50:07.112 [info] > git status -z -uall [39ms]
2023-05-10 01:50:07.113 [trace] Operation end: Status (blocking: false, readOnly: false; retry: false; showProgress: true)
2023-05-10 01:50:07.188 [debug] [wt] Change: c:\Users\Eric\code\gitkraken\vscode-gitlens\.git\fsmonitor--daemon\cookies\10552-6182
2023-05-10 01:50:12.129 [trace] Operation start: Status (blocking: false, readOnly: false; retry: false; showProgress: true)
2023-05-10 01:50:12.166 [info] > git config --get commit.template [32ms]
2023-05-10 01:50:12.172 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [35ms]
2023-05-10 01:50:12.217 [info] > git status -z -uall [42ms]
2023-05-10 01:50:12.218 [trace] Operation end: Status (blocking: false, readOnly: false; retry: false; showProgress: true)
2023-05-10 01:50:12.288 [debug] [wt] Change: c:\Users\Eric\code\gitkraken\vscode-gitlens\.git\fsmonitor--daemon\cookies\10552-6183
2023-05-10 01:50:17.229 [trace] Operation start: Status (blocking: false, readOnly: false; retry: false; showProgress: true)
2023-05-10 01:50:17.266 [info] > git config --get commit.template [32ms]
2023-05-10 01:50:17.273 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [35ms]
2023-05-10 01:50:17.316 [info] > git status -z -uall [39ms]
2023-05-10 01:50:17.317 [trace] Operation end: Status (blocking: false, readOnly: false; retry: false; showProgress: true)

If it helps any, I crafted the file watchers in GitLens to only watch specific parts of the .git folder that I needed:
https://github.com/gitkraken/vscode-gitlens/blob/039d61184517af83f10f3ac582a26bcd9921d5f0/src/git/models/repository.ts#L273-L315

This bug has been fixed in the latest release of VS Code Insiders!
@iouzzrj, you can help us out by commenting /verified if things are now working as expected.
If things still don't seem right, please ensure you're on version f1258a5fbed44b8f84a097c73c1799c13c5c3646 of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.
Happy Coding!

@eamodio, could you please confirm that this is fixed in the latest Insiders release? Thanks!

I have looked into this and found out that this is a Windows specific problem and one can easily reproduce by enabling trace logging for the Git extension, making a change to a file, and then staging the file. In the Git output channel one can notice a extra file system event with the [wt] prefix that should have been filtered out but it is not.
The problem is this regular expression that uses / but not \:
https://github.com/microsoft/vscode/blob/d28916517030b85e1079c87b9f286ca466234f39/extensions/git/src/repository.ts#L772-L773

So is it just a case where using node's path.sep would solve the problem?

By the way, if anyone else is experiencing the same bug and is not using insiders' version, here is how I solved this issue palliatively:
Every time I open VSCode I need to disable the following setting and enable again:

authors: VSCodeTriageBot dami-i eamodio iouzzrj lszomoru


text:
keeps logging me out

Type: Bug
When i open vs code i have to login again. is it possible to stay logged in?
VS Code version: Code 1.77.3 (704ed70d4fd1c6bd6342c436f1ede30d1cff4710, 2023-04-12T09:16:52.732Z)
OS version: Linux x64 6.2.6-76060206-generic
Modes:
Sandboxed: Yes

System Info

Item
Value

CPUs
AMD Ryzen 7 5700U with Radeon Graphics (16 x 3573)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
2, 2, 1

Memory (System)
30.68GB (23.33GB free)

Process Argv
--extensions-dir=/home/xrgarcia/.var/app/com.visualstudio.code/data/vscode/extensions --open-url vscode://vscode.github-authentication/did-authenticate?nonce=c691ddf8741e4f7a&windowId=1&code=6f1f52d01d2a23e8fac6&state=vscode%253A%252F%252Fvscode.github-authentication%252Fdid-authenticate%253Fnonce%253Dc691ddf8741e4f7a%2526windowId%253D1 --crash-reporter-id d6ec10a4-2688-4c87-a222-ed2fb7170af4

Screen Reader
no

VM
0%

DESKTOP_SESSION
pop

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
pop

XDG_SESSION_TYPE
x11

Extensions (13)

Extension
Author (truncated)
Version

markdown-mermaid
bie
1.18.1

copilot
Git
1.84.51

vscode-docker
ms-
1.25.0

pylint
ms-
2023.4.0

python
ms-
2023.6.1

vscode-pylance
ms-
2023.4.40

jupyter
ms-
2023.3.1201040234

jupyter-keymap
ms-
1.1.0

jupyter-renderers
ms-
1.0.15

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

es6-string-html
Tob
2.12.1

vim
vsc
1.25.2

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vstes627:30244334
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30610679
nodejswelcome1cf:30587006
3biah626:30602489
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
a9j8j154:30646983
vsctsb:30705553
azdwalk:30721579
pythonms35:30701012
pythonfmttextcf:30716743

@xrgarcia do you have a keyring app installed like gnome-keyring?

Hi Tyler, I'm using Pop!_OS 22.04 LTS. I did figure out how to make it remember my login. I added a new profile, called it my name... THEN when i logged in, it remembers me. I wonder if the default profile location is somewhere my user doesn't have write access.

You added a new Profile to VS Code or to your OS? How did you install VS Code?

I create a profile in VS Code -> settings -> profiles -> create profile
https://code.visualstudio.com/download
.deb

Creating a profile shouldn't have any affect on logging in. We store the credentials in your OS keyring regardless of profile. Unusual. If you are able to reproduce the problem can you follow these steps so that we can get more information on what's going on?

Open the Command Palette
Run the Developer: Set Log Level... command
To the right of Trace, click the double check mark button. ✔ ✔ (enables trace logging as the default)
Wait for the issue to happen...
Open the Output pane (ctrl+shift+u I think on Linux)
drop in this issue he contents of the following:

Microsoft Authentication Output channel or GitHub Authentication Output channel
Log (Main) Output channel

Open the Command Palette
Run the Developer: Set Log Level... command
To the right of Info, click the double check mark button. ✔ ✔ (to set the default back to info)

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

Sorry, i didn't get back to you sooner. The problem was i had the flatpak AND .deb. Once i uninstalled the flatpak version everything worked perfectly!  I was opening/using the deb version but must be a conflict. thought i would share.

authors: TylerLeonhardt VSCodeTriageBot xrgarcia


text:
intellisense within the debugger (watch pannel and conditional breakpoint)

I really love vscode native debugger, or the one that have been added as extensions (ex PHP Debug)
What would take it to the next level i think,
is if all the great intellisense that VSCode is able to do was also working when :

we type something in the watch pannel.
we add a conditional breakpoint

I don't know if and how this also could be made possible for other debug extensions to easily make use of that,
but even if only for the native javascript debugger, that would already be a great start :)
Anyway, a big thanks to all the devs for this great IDE !

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!

Thanks, I'm aware of this missing feature

authors: VSCodeTriageBot roblourens vulkanosaure


text:
emmet abbrivation command is not working, please fix it

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

1


text:
Reading suggestions or autocomplete of extensions

Type: Feature Request
Depending on the extension we are using, when code suggestion information appears, it is not read by screen readers.
Steps to reproduce.
Install the codeium extension.
Open any project, and start typing or commenting the code;
You will hear a sound when a hint appears, but this hint is not read by screen readers like nvda.
I suggest that it is possible to activate a configuration in vscode, so that this type of information can be transmitted to screen readers.
VS Code version: Code - Insiders 1.79.0-insider (f6be5461f8bc69013a605f5baea834651c6589fb, 2023-05-20T01:18:53.811Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Remote OS version: Linux x64 5.15.90.1-microsoft-standard-WSL2

I can reproduce. We must not be getting the line content here https://github.com/microsoft/vscode/blob/43cf22b41a7d999b3bc7b535bf8db093fa05e615/src/vs/editor/contrib/inlineCompletions/browser/inlineCompletionsController.ts#L188-L189

@meganrogge I would like to inform you that I also tested it with the copilot and when listening to the sound that a suggestion was given, the screen readers also do not read.

You need to set editor.screenReaderAnnounceInlineSuggestion to true and it will work for copilot @jeanbrazcosta

@jooyoungseo do you think we should now set that to true by default?

Legal @meganrogge I defined it and it actually worked for the copilot.
My suggestion is that it would not be possible for these settings to go to the accessibility feature?
I know that it makes sense to stay where they are because it has to do with the editor, but they are difficult to find, or maybe we have some dock where all the accessibility features are and their respective paths where they should be activated, you get the idea.

Yes, we actually have help menus now for the copilot chat view / interactive editor session. When you focus those inputs, using alt+f1 reveals/focuses the help menu for each.
I think for this case, we should enable inline suggestion by default

Sorry, @meganrogge just found out that by enabling the setting, it also worked for codeium.
Should I then close this feature?

I think we should enable this by default, so will use this issue to track that

@meganrogge I agree with the idea setting the inline suggestion announcement to TRUE by default as it is now stable.

Verified the setting default is flipped

authors: Tyriar jeanbrazcosta jooyoungseo meganrogge


text:
XHR failed

Type: Bug
cuando intento instalar cualquier extension me pone el mensaje XHR Failed, he probado a quitar las reglas del Firewall y sigue todo igual, debe haber algo en la configuracion
VS Code version: Code 1.78.2 (b3e4e68a0bc097f0ae7907b217c1119af9e03435, 2023-05-10T14:39:26.248Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 x 3392)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.92GB (9.24GB free)

Process Argv
--crash-reporter-id 080023e7-a22f-4260-b755-7d1ba09fe0c6 --inspect-extensions=65101 --crash-reporter-id 080023e7-a22f-4260-b755-7d1ba09fe0c6

Screen Reader
no

VM
0%

Extensions: none

¡Gracias por crear este problema!
Sin embargo, como la descripción no está en inglés, es difícil para nosotros trabajar en ella. Si puede, edite este número para que esté en inglés. No agregue un nuevo comentario ni cree un nuevo problema, sino que edite el problema existente.
Desafortunadamente, los servicios de traducción automática no pueden manejar el lenguaje técnico necesario para comunicarse de manera efectiva sobre problemas de software, por lo que recomendamos encontrar un traductor humano que esté familiarizado con nuestra tecnología para ayudar a traducir.
De lo contrario, este problema se ha marcado como que necesita traducción y un miembro de la comunidad puede ayudar a traducirlo.

Thanks for creating this issue!
Unfortunately, as the description is not in English, it's hard for us to work on. If possible, please edit the original issue to be in English.
In our experience, automatic translation services are not able to handle the technical language needed to effectively communicate about software issues, so we recommend finding a human translator who is familiar with our technology to help.
Otherwise, we have marked this as needing translation and a community member may be able to help out.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

Hello
The description for my fix , would  to in this message?
El El vie, 26 may 2023 a las 1:27, VSCode Triage Bot <
@.***> escribió:

¡Gracias por crear este problema!
Sin embargo, como la descripción no está en inglés, es difícil para
nosotros trabajar en ella. Si puede, edite este número para que esté en
inglés. No agregue un nuevo comentario ni cree un nuevo problema, sino que
edite el problema existente.
Desafortunadamente, los servicios de traducción automática no pueden
manejar el lenguaje técnico necesario para comunicarse de manera efectiva
sobre problemas de software, por lo que recomendamos encontrar un traductor
humano que esté familiarizado con nuestra tecnología para ayudar a traducir.
De lo contrario, este problema se ha marcado como que necesita traducción
y un miembro de la comunidad puede ayudar a traducirlo.
Thanks for creating this issue!
Unfortunately, as the description is not in English, it's hard for us to
work on. If possible, please edit the original issue to be in English.
In our experience, automatic translation services are not able to handle
the technical language needed to effectively communicate about software
issues, so we recommend finding a human translator who is familiar with our
technology to help.
Otherwise, we have marked this as needing translation and a community
member may be able to help out.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/183390#issuecomment-1563627410,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A76AAWSVPWR3MH6V3LGP3CDXH7THJANCNFSM6AAAAAAYOKFTPM
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Un saludo
Atte Alejandro.


text:
Unbound breakpoint

Type: Bug
I am no longer able to set breakpoints in my Javascript code.  When I run, the red dot changes to a gray circle.  Hovering the cursor over it says it is an "Unbound breakpoint".  Opening the troubleshooter shows this:
This breakpoint was initially set in:
C:\Devel\web\tst2\test2.js line 8 column 1
We couldn't find a corresponding source location, but found some other files with the same name:
c:\Devel\web\tst2\test2.js
You may need to adjust the webRoot in your launch.json if you're building from a subfolder, or tweak your sourceMapPathOverrides.

I tried changing the launch configuration, and I don't know what "sourceMapPathOverrides" are.  Here is how to reproduce:
Workspace:
C:\Devel\web\
    tst\
        test.html
        test1.js
    tst2\
        test2.js

test.html:
<!DOCTYPE html>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
<meta name='viewport' content='width=device-width, user-scalable=no, initial-scale=1, maximum-scale=1, minimum-scale=1' />
<meta name="apple-mobile-web-app-capable" content="yes" />

test1.js:
function main(ip)
{
	document.body.innerHTML="

Hello world!

"
    Logit();
}
window.onload=js_startup;

test2.js:
function js_startup()
{
		main();
}

function Logit()
{
    console.log("What, me worry?")
}

Launch configuration:
		{
			"name": "Tst",
			"request": "launch",
			"type": "chrome",
			"file": "${workspaceFolder}/tst/test.html",
			"webRoot": "${workspaceFolder}/tst"
		}

Set a breakpoint in test2.js Logit on the "console.log" line.
VS Code version: Code 1.78.2 (b3e4e68a0bc097f0ae7907b217c1119af9e03435, 2023-05-10T14:39:26.248Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: Yes

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz (8 x 2712)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: unavailable_offvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.83GB (7.05GB free)

Process Argv
--crash-reporter-id 87c1d683-95a6-416a-b844-66ab3df3e049

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.4.0

gitlens
eam
13.6.0

shortcut-menu-bar
jer
3.0.4

remote-ssh
ms-
0.102.0

remote-ssh-edit
ms-
0.86.0

hexeditor
ms-
1.9.11

js-debug-nightly
ms-
2023.6.617

remote-explorer
ms-
0.4.0

intellicode-api-usage-examples
Vis
0.2.7

vscodeintellicode
Vis
1.2.30

(3 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
282f8724:30602487
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
a9j8j154:30646983
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
03d35959:30757346
pythonfmttext:30731395
pythoncmv:30756943
fixhidewlkth:30730051
hidesbindicator:30760978
pythongtdpathcf:30739705
pythonnosm12tcf:30757130

/jsDebugLogs

Please collect trace logs using the following instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.
⚠ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to connor@xbox.com

Please see the attached log file.
vscode-debugadapter-08f2d59c.json.gz

authors: VSCodeTriageBot connor4312 murrellr


text:
Integration test failure on macOS

Build: https://dev.azure.com/monacotools/a6d41577-0fa3-498e-af22-257312ff0545/_build/results?buildId=218532
Changes: https://github.com/Microsoft/vscode/compare/4f95907...4f95907
vscode API - workspace-watcher
MainThreadFileSystem#$watch(): failed to stat a resource for file watching (extension: vscode.vscode-api-tests, path: watcherTest:/somePath/folder, recursive: true, session: 0.4398481045774034): EntryNotFound (FileSystemError): watcherTest:/somePath/folder
    ✔ createFileSystemWatcher
  260 passing (4m)
  16 pending
  1 failing
  1) vscode API - tasks
       Tasks
         CustomExecution
           sync task should flush all data on close:
     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/runner/work/1/s/extensions/vscode-api-tests/out/singlefolder-tests/workspace.tasks.test.js)
      at listOnTimeout (node:internal/timers:559:17)
      at processTimers (node:internal/timers:502:7)

ENOPRO: No file system provider found for resource 'fake-fs:/1fe2f0a27cf14366': CodeExpectedError: ENOPRO: No file system provider found for resource 'fake-fs:/1fe2f0a27cf14366'
    at e.FileService.j (vscode-file://vscode-app/Users/runner/work/1/VSCode-darwin-x64/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:624:12371)
    at async e.FileService.exists (vscode-file://vscode-app/Users/runner/work/1/VSCode-darwin-x64/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:624:14796)
    at async js.tb (vscode-file://vscode-app/Users/runner/work/1/VSCode-darwin-x64/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2299:32349)
[main 2023-06-14T00:47:50.664Z] Extension host with pid 50455 exited with code: 0, signal: unknown.
##[error]Bash exited with code '1'.
Finishing: Run integration tests (Remote)

I'm confused because all of the tests are passing when I click on the link above. I think this was a fluke

Here's the raw log of the failed test run from Attempt #1, but it could be a flaky test that's been fixed since then:
https://dev.azure.com/monacotools/a6d41577-0fa3-498e-af22-257312ff0545/_apis/build/builds/218532/logs/980

thanks, i'm seeing this in that log, so seems maybe was a terminal issue that's since been fixed
 Exception occurred during xterm disposal {}