like Can you provide the extension that open extension-provided terminal and trigger this issue?
Some commits about the comment/design history of this context key


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.58.0-Insiders (insiders) OS Version: mac Steps to Reproduce: Cell Execution summary information is not passed to notebook deserializer PR submitted here /cc


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes (all other extensions disabled) <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- Version: 1.89.0 Commit: Date: 2024-05-01T02:09:22.859Z Electron: 28.2.8 ElectronBuildId: Chromium: 120.0.6099.291 18.18.2 V8: 12.0.267.19-electron.0 OS: Windows_NT x64 10.0. This is a continuation of I'm in the process of creating a product icon theme and noticed the following icons not being (properly) replaced. They either appear invisible or are unthemed. There may be more icons that suffer from the same problems described below, but I have not been able to find them as of writing this. The icon is invisible after applying the theme. This is due to the following CSS rule overriding the attribute: ! Same as settings editor tab icon, it's invisible for the same CSS rule overriding the attribute. Visible in, for example, output and terminal panel views (left next to close icon), editor tabs more actions (where the 'split editor' action icons is), etc. This doesn't appear to get any overrides at all, so it remains unthemed. The icon is invisible after applying the theme. This is due to the a second attribute always being present and overriding the first attribute that correctly retrieves which value should have. !
To verify: extends the with export it as VSIX, import select the theme verify that the settings editor has now a explorer icon, as well the more icons


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: OS Version: MacOS Big Sur latest Steps to Reproduce: Create a new profile Click on the Profile Activity Bar icon, then choose Result: the quick pick comes up... ! Now click on the menu item to bring up the view Click on the menu item again Result: focus just moves to the pane ! Expectation: Show the Quick Pick so the menu works the same regardless of whether or not the content view is open
I was also hit by this - that by clicking on "Export Profile..." it looks like it has no effect, when it fact it just passed the focus. we could always show quick pick as Chris suggests?
What about the contents view when you click on again? Does this has to be closed or remain like this? May I understand what is confusing in navigating to the contents view when you click on export profile button?
I think you can leave the view open, but I would open the Quick Pick right away, not force the user to click on the Export button (again).
Another idea (that was also mentioned in the UX call) is how about always open the view and ditch quick pick? This was initial flow actually.
I think that flow might work. My biggest concern is that users might not notice that the focus moved to the view (especially if the view is already open). Long term - maybe the view becomes a custom editor? fyi
Quick pick is removed and by default we show the contents view now.


VSCode Version: 1.7.2 () OS Version: Windows 10.0. Steps to Reproduce: a file a sentence of text such as Lorem ipsum sit dolar amet. your keyboard cursor after <kbdTab</kbdExpected: Spaces or tabs to be between and Result: word gets converted into an XML tag and auto closed, leaving us with <Lorem</Loremipsum sit dolar amet. !
This is coming from Emmet. To disable this, add: to your settings. Although this is currently the expected behavior, I think we should probably disable emmet expansions in markdown by default because this behavior can be annoying during normal writing. Any thoughts?
this behaviour is a consequence of , which has as the goal to not hard code in which language modes emmet is enabled for. As a heuristic uses the grammar's scope name hierarchy as a hint. This heuristic has worked pretty well. The scope of the markdown grammar is . This means Markdown is treated as a specialization of and since emmets supports , is enabled in Markdown as well. According the emmet doc there is no special syntax profile available for Markdown So a quick fix would be to: hard code an exclusion for markdown in #isEmmetEnableMode change the scope name of the markdown grammar, so that it doesn't inherit from html, not sure what the consequences of this are. do you have other ideas how to improve the support for emmet in Markdown and avoid the surprise described in this issue?
Hello, I see the same way as you suggested above. But, perhaps, we can also disable Markdown in the settings, as it was for . If you decide to disable Emmet inside Markdown, it is better to first option. But my 2 cents: Markdown is a lightweight markup language and it presupposes the existence of HTML constructs within yourself. Thus, it seems to me, to disable Emmet inside Markdown is not correct. P.S. Small news: the creator of Emmet had already started work on the second version aka 2.0.0
thanks for the feedback. I agree with your point that disabling emmet without some way to re-enable it, if someone really wants emmet is better than to totally disable it. Glad to hear about Emmet 2.0.
Could just be in the default setting for ?


That would stop most users from triggering emmet unexpectedly in markdown files, while still allowing users to opt back in to emmet for markdown if they wish
the idea is good. It has a small drawback. If someone defines in the settings, then they will not profit from this fix. However, if someone if familiar with this setting and then they know how to disable emmet in markdown, if they are annoyed by it. Bottom line I'm fine with this fix.
Ok, I've merged in which adds to the default list of excluded languages. Not a perfect solution, but it should stop many users from hitting this behavior unexpectedly


Type: <bBug</bCopilot and auto inline suggestion. , type the following comment in the first line and hit enter: soon as you hit enter to change a line, you will hear an audio cue and alert for the inline suggestion, such as . Press alt+F2 to see if you can open Accessible View. Notes: Accessible View is not open. VS Code version: Code - Insiders 1.83.0-insider (, 2023-09-28T05:34:00.540Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (92)</summaryExtensionVersion ------ android-dev-ext1.3.2 aiprm-lang0.0.2 Bookmarks13.4.1 openscad1.2.1 spellright3.0.118 zoterolatex0.4.1 mermaid-markdown-syntax-highlighting1.5.2 doxdocgen1.4.0 vscode-markdownlint0.52.0 vscode-eslint2.4.2 vscode-quick-select0.2.9 vscode-deno3.25.0 gitlens14.3.0 EditorConfig0.16.4 prettier-vscode10.1.0 vscode-google-translate1.4.13 codespaces1.15.4 copilot1.117.446 copilot-chat0.8.


remotehub0.60.0 vscode-github-actions0.26.2 vscode-pull-request-github0.72.0 overleaf-workshop0.2.4 cslpreview0.2.2 easy-snippet0.6.3 path-autocomplete1.25.0 latex-workshop9.14.0 lilypond-syntax0.1.1 scheme0.2.0 better-cpp-syntax1.17.2 vscode-bard0.0.10 google-search0.0.1 vscode-lua-format1.3.8 lilypond-formatter0.2.3 lilypond-pdf-preview0.2.8 lilypond-snippets0.1.1 vslilypond1.7.3 zotero0.1.10 git-graph1.30.0 vscode-docker1.26.1 black-formatter2023.4.1 flake82023.6.0 isort2023.11. python2023.16.0 vscode-pylance2023.9.20 jupyter2023.8.


jupyter-keymap1.1.2 jupyter-renderers1.0.17 vscode-jupyter-cell-tags0.1.8 vscode-jupyter-slideshow0.1.5 remote-containers0.313.0 remote-ssh0.106.4 remote-ssh-edit0.86.0 remote-wsl0.81.5 vscode-remote-extensionpack0.24.0 azure-repos0.36.0 cmake-tools1.15.31 cpptools1.17.5 cpptools-extension-pack1.3.0 js-debug-nightly2023.9.2717 powershell2023.6.0 remote-repositories0.38.1 vscode-github-issue-notebooks0.0.130 vscode-selfhost-test-provider0.3.18 vscode-serial-monitor0.10.0 vsliveshare1.0.5883 autodocstring0.6.1 pandocciter0.10.3 shiny-python0.1.4 shinyuieditor0.5.0 quarto1.100.0 r-debugger0.5.4 java1.22.1 vscode-xml0.26.1 r2.8.1 multi-command1.6.0 vscode-deepl1.0.6 abc-music0.4.0 lua3.7.0 latex-utilities0.4.10 cmake0.0.17 errorlens3.14.0 intellicode-api-usage-examples0.2.8 vscodeintellicode1.2.30 vscode-arduino0.6.0 vscode-java-debug0.54.0 vscode-java-dependency0.23.1 vscode-java-pack0.25.14 vscode-java-test0.40.0 vscode-maven0.42.0 markdown-all-in-one3.5.1 grammarly0.22.1 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
I see that's happening because the model says there's no content for that line. I notice that it goes into this cache and returns . Any idea what we can do about this? ! !
here's where is returned
this is a breaking issue for screen reader users. Any thoughts would be appreciated.


The type was updated for . Unfortunately, the constructor was not updated, so this would require that you still construct the object with a and subsequently update the with the tuple.
, looking into this :)


Issue Type: <bBug</bGitHub reported a security vulnerability related to the NPM package in my VS Code extension's . <img width="765" alt="Screen Shot 2019-06-18 at 5 49 45 PM" src="https://user-"In my VS Code extension's , I've a dependency for : When I run to see what packages are using , I see this: <img width="156" alt="Screen Shot 2019-06-18 at 5 49 23 PM" src="https://user-"And I see this reflected in my : VS Code version: Code 1.35.1 (, 2019-06-12T14:29:22.216Z) OS version: Darwin x64 18.6.0 <details<summarySystem Info</summary </details<details<summaryExtensions (15)</summaryExtensionVersion ------ vscode-css-formatter1.0.1 npm-intellisense1.3.0 path-intellisense1.4.2 bracket-pair-colorizer1.0.61 vscode-eslint1.9.0 gitlens9.8.2 vscode-npm-script0.3.7 auto-rename-tag0.1.0 beautify1.5.0 ibm-streams0.5.0 vscode-duplicate1.2.1 java0.46.0 change-case1.0.0 JavaScriptSnippets1.7.2 ReactSnippets2.3.0 </details


When the comment is too long to fit in the panel (which is common), the author name and the date get truncated first. Instead, we should truncate the comment: e.g. look at the last comment in ! Showing the author name (instead of ) should be more important than showing a few more characters in the comment preview. (cc
/verified It prefers the user name over comment now.


Issue Type: <bBug</bthe refactoring window over any element with many available refactoring options (e.g.: a widget in Flutter) tab selection won't move BUT if you hit enter it will choose an option other than the highlighted one VS Code version: Code 1.33.1 (, 2019-04-11T08:27:14.102Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </detailsExtensions disabled <!-- generated by issue reporter --
Assigning because this only happens when using custom title bars. Repo Windows with custom title bar enabled the ts file: code actions and press tab once or twice, then enter The second or third code action ends up being applied even though the visible selection never changes


Testing If I run "Continue working on...," I get many development environments to target, but I only see one Continue Working in command for the codespace option.
Verified from the remote repositories options. Looks like 1 and 2 (local folder and local container) still need to add entries to be consistent. <img width="355" alt="image" src="https://user-"
who should add the built-in command?


Issue Type: Bug folder ! VS Code version: Code - Insiders 1.21.0-insider (, 2018-02-21T09:22:14.399Z) OS version: Windows_NT x64 10.0. Reproduces without extensions <!-- generated by issue reporter --
Code pointer
does it mean that this is the expected behavior?
I m on it.
it is always debatable if something is a feature-request or a bug. I guess this is more of a bug, but I took the artistic freedom and assigned feature-request.
it does not seem to restore the full expansion state, only the first level is that true?
yes, only the first level. could improve the PR and try to restore more.
Yes, i can do that.
great, tree should have api to get the exapnsion state. And once the pr is ready just ping me on it.
Should i make a new method to return all the expanded children as array on treeModel?
Is this ready for verification?
ben already verified and can add a verified label. There are some limitation which will tackle in a pr for next milestone


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: OS Version: Version: 1.84.0-insider (user setup) Commit: Date: 2023-10-23T05:34:05.496Z Electron: 25.9.1 ElectronBuildId: Chromium: 114.0.5735.289 18.15.0 V8: 11.4.183.29-electron.0 OS: Windows_NT x64 10.0. Steps to Reproduce: two workspaces a couple of files Active Editor into a New Window on the new window and Press Alt+F4 : aux window closes. Actual: VS Code closes the workspace and both windows associated with it.
Can you see if is assigned as keybinding? I assume this goes through our global window close handler that has not yet adopted aux windows.
I have default keybindings { "key": "alt+f4", "command": "" },


To load local resources (for example ones bundled with an extension), the  method must be used. As far as I can tell, when a URI produced in this way is requested by a webview, VSCode serves it via something like a local webserver. But there is no way to configure the MIME type that the URI gets served with. This request is to add a way to set the MIME type. This is important for extensions which want to load WebAssembly resources in the webview. The most efficient method to do so is , but this only works if the WASM blob is served as . So currently it doesn't seem possible to load WASM in a webview in this way. Since fallback methods may fail to cache WASM compilation results, I've measured that for a large WASM blob it's actually more efficient to load it from the internet via , as then subsequent loads reuse WASM compilation results, than it is to load it from a local resource.
/verified


When I run all tests, the label resets back to after all tests were run. This is very confusing. !
This was a result of a bad filter function that caused all test runs to be treated extension-triggered. The "real" test run would then never have results, or get any output. More importantly, this results in "show test output" usually showing nothing. Taking this as a candidate. Essentially the sequence is: is triggered from the UI, so we prepare TestResults for incoming data and send the TestRunRequest precursor over to the EH EH doesn't associate that request with the existing run calls from its , which gets treated as a brand new run, so we make new TestResults for that run run and states get updated... 's resolves automatically marks the UI-triggered run as complete since the runHandler returned and there are no ongoing TestRuns latest completed TestResults is now the empty one that core created and was never updated so things that use the last result, like "show test output", are empty The code path in is meant to only be taken by the new Continuous Test runs, where the request is long-lived and doesn't have a single associated set of TestResults.


Type: <bBug</bThis issue was supposed to be fixed in , but we have recently received complaints from some users regarding this. I counted the first 50 issues with Vue extension installed in , and 25 users are using 1.8.27 ~ 2.0.10 (2.0.10 was released 4 months ago ), only 19 users are using the latest version (2.0.22 ~ 2.0.28). Numbers: 2.0.10: 13 (Issue , Issue , Issue , Issue , Issue , Issue , Issue , Issue , Issue , Issue , Issue , Issue , Issue ) 2.0.8: 6 (Issue , Issue , Issue , Issue , Issue , Issue ) 2.0.7: 2 (Issue , Issue ) 2.0.6: 2 (Issue , Issue ) 1.8.27: 2 (Issue , Issue ) 2.0.22~2.0.28: 19 Since some versions in 2.0.0~2.0.10 may have serious problems, this is probably the reason why the Vue extension has continued to receive negative reviews on the Marketplace and VSCode has continued to receive bug reports about the Vue extension for several months. I found a Windows computer with 2.0.7 installed and was able to reproduce the issue of not being able to update the version. The following is the content of . (Formatted for easier reading) And I can reproduce the problem of not being able to update by overwriting the above metadata to the file of another macbook. is installed, uninstall it and then close VSCode and reopen it. 2.0.7 from https://open- and install it to VSCode, VSCode can normally prompt that Vue extension needs to be updated. and modify the metadata of the last extension to: VSCode will find that the Vue extension cannot detect newer versions. VS Code version: Code 1.92.1 (, 2024-08-07T20:16:39.455Z) OS version: Darwin arm64 23.1.0 Modes: <!-- generated by issue reporter --
cc
I just checked our telemetry for the most popular combinations of VS Code version and Vue extension version and here's what I see.


This proves that vue version and are indeed not getting properly updated. The root cause of this is the fact the vue extension, unpublished from the Marketplace and published again the same name (thus exposing a bug in the Marketplace) as explained here We still want to help transition your users, and I will go ahead and move this issue to the VS Code repo and Sandeep will investigate next week once he is back from vacation. Thank you !
Update is not detected automatically. It is detected only when user is searching for the extension.
Sorry about this inconvenience caused. Fixed it - We will now detect the update automatically.
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
I just tested it and confirmed it's fixed in the latest insiders version, thanks a lot!
Adding label based on above comment


VSCode Version: Version: 1.67.0-insider (Universal) Commit: Date: 2022-04-06T05:15:27.397Z (8 hrs ago) Local OS Version: macOs 12.3.1 / arm Remote OS Version: Centos 7 Remote Extension/Connection Type: SSH Logs: Steps to Reproduce: SSH Session the popup, hey Python and Jupyter extensions have pre-release versions or install / switch to pre-release on the extension page Error (but the extensions shows the pre-release state), but afaik that's not the case Note: I removed the vs code server on the remote host and did a new installation (starting from locally with the remote extensions versions), but it actually just installs the stable version on the remote and then the switch is not possible. It should actually consider and install the same version that is used locally, shouldn't it? Can't install pre-release version of 'ms-toolsai.jupyter' extension because it is not compatible with the current version of Visual Studio Code - Insiders (version 1.67.0-insider). Does this issue occur when you try this locally?: No Does this issue occur when you try this locally and all extensions are disabled?:No logs: [2022-04-06 15:51:45.599] [renderer1] [info] Downloading the 'ms-toolsai.jupyter' extension locally and install [2022-04-06 15:51:45.626] [renderer1] [error] Can't install pre-release version of 'ms-toolsai.jupyter' extension because it is not compatible with the current version of Visual Studio Code - Insiders (version 1.67.0-insider).: IncompatiblePreRelease: Can't install pre-release version of 'ms-toolsai.jupyter' extension because it is not compatible with the current version of Visual Studio Code - Insiders (version 1.67.0-insider).


at l.checkAndGetCompatible (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-) at async l.downloadAndInstall (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-) at async l.installFromGallery (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-) at async (index 0) at async Object.j [as settled] (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-) at async Ms.installFromGallery (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-)
Would you mind sharing your Remote SSH logs as well? And if you have any gifs or videos of what you're seeing?
! ! And this - but it's just a "refresh" problem, once I switch between extensions it shows the old and unfortunately correct version again: ! And logs...
Your SSH connection looks successful. I'll transfer this issue to the Python extension team to see if they have ideas why this state is happening
This is an error thrown by VS Code, not sure what an extension can do about this as installing extensions is completely managed by VS Code. I'm transferring this back to VS Code.
Same issue happends to me.
I was able to install this manually (remote) by downloading the new extension that I got from this link: By this, you'll switch to the pre-release version. After installing it once manually, all updates work as usual.
Can you please try our latest insiders and see if you can reproduce this issue still?
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
Sorry, I had it already solved and thought it wouldn't occur again + I moved away from using Remote SSH whenever I could. I am now on the latest 1.68 insiders and for whatever reason the jupyter extension reverted to "non pre-release" and the same issue still exists - same error. Same workaround as above fixed the issue for me.
Were you using any remote set up when this happened again? Are you still able to repro it?
Yeah, it's exactly the same setup, just updated (yesterday's) insider build.


And yes, if I uninstall the extension, install release, try to switch, the same happens over and over again. I discovered another bug: switch back to stable is not possible [2022-05-24 12:03:11.208] [remoteagent] [warning] Overwriting user extension with It always pushes me back to the pre-release. I think this may be related to keep local/remote on the same version/track. EDIT: Okay, actually this blocks everyone using insiders with the jupyter and/or other plugins in combination with remote ssh. Since insiders are updated daily, the "vs code server" is updated daily and the plugin is revert/installed again in the non preview version. So my hotfix has to applied daily which is really annoying. EDIT 2: I realised that the current (release today) stable "jupyter" version also has the latest insiders api implemented. So for now and for me that is solved - but the actual bug is still there, I can't switch to pre-release versions in a remote ssh setup.
Sorry that you are having this annoying issue and glad that you are able to reproduce it so that we can investigate. If you don't mind, can you please summarise your repro steps?
So, I now understand why it's a bit complex to reproduce this - I guess... I was even confused myself. So, currently the only way to reproduce it was for me: 1) deinstall the server (rm -rf .vscode-insiders-server) 2) connect/install + install jupyter extensions (local: pre-release) -pre-release installation successful 3) switch to release on remote 4) reload window -I am then on release try to switch to pre-release -issue appears. And now the important part: I realised that I still had the setting because within our company we had restrictions before... setting this to false also fixes the issue - even when it appeared before.
Thanks for the steps. I can reproduce it now and fixed. To verify: Open a remote window and set setting Install pre-release of ESLint extension Reload window Switch to release version of ESLint extension Reload window Switch to pre-release version of ESLint extension Make sure switch happens


Issue Type: <bBug</bThe source control pane allows discarding changes by right-clicking on selected items and then choosing "Discard Changes". If items are selected in a tree view, and part of the selection is a directory, then the confirmation dialog shows a wrong (impossible) number of files to be discarded. Steps: open vscode in a git directory, with no current changes switch to the source control pane, note the changes make sure that "View as Tree" mode is active select all three items in the treev view, comprising of 1 directory and 2 files right-click onto select items -"Discard Changes" //exp: Confirmation - "This will DELETE 2 untracked files" //act: Confirmation - "This will DELETE 3 untracked files" IOW, the directory is counted as a file. This is rather irritating if one expects to discard a very well-known number of files, only to discover that the UI confirmation dialog is off. VS Code version: Code 1.60.1 (, 2021-09-10T17:06:57.931Z) OS version: Linux x64 5.13.15-200.fc34.x8664 Restricted Mode: No <details<summarySystem Info</summary </detailsExtensions disabled<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Just noticed a simpler scenario: Just use tree view mode, have 1 file in the directory, and directly discard the directory. The confirmation dialog will ask for confirmation to delete 2 files, while there is 1 file only (the directory will not be touched by the git revert)
Funny enough - clicking on the "Discard All Changes" icon reports the correct number of files (2 files in the scenario above).
I see multiple options for implementing a fix for this: 1) Deduplicate the resources in the command 2) Deduplicate the resources in core before the are passed to the command as args
1 sounds great!


When I was debugging SVN extension () I saw this message in console: ! Then I've discovered that this promise is unhandled in another extension, after I've edited file and inserted breakpoint. Please provide some stacktrace or message of rejected Promise it's hard to find the root of the problem.
This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the for VS Code. See also our guidelines. Happy Coding!
I think the ask here is that we improve our handler to display the call stack of the unhandled error...
Yeah, I got that. I have for that (thanks to


Version: 1.38.0 Commit: Date: 2019-09-03T21:47:00.464Z Electron: 4.2.10 Chrome: 69.0.3497.128 10.11.0 V8: 6.9.427.31-electron.0 OS: Darwin x64 18.0.0 Steps to Reproduce: 1 open multiple tabs and only save some of them. 2 commit and click <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.559 --- <!-- score: 0.518 --- <!-- score: 0.492 --- <!-- score: 0.483 --<!-- potentialduplicatescomment --
Oh yeah. Good catch. Want to submit a fix? Problem is
Hey, I am a new contributor here. I want to give a try on this issue.
Great. Go ahead.


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.56.2 OS Version: MacOS Catalina 10.15.6 Steps to Reproduce: VSCode Version any typescript file (for example in ) /Ctrl + Click on any native dom method, for example , there should be a error message popups ! I thinks this is caused by the wrong type definition file path in below code:


sure the File Explorer is visible temporary profile window Welcome editor fails to open. cc
Due to:
and I also reproduced this when testing out her walkthrough changes:


Steps to Reproduce: a directory with Git initialized. "Incoming/Outgoing" section in the SCM pane appear. Could be done by either: Make sure the current branch has an upstream branch, then commit something. Or Set and to . the page. a change to a file. Expected result: the file appears under "Changes" section in SCM pane. Actual result: the "Changes" section doesn't appear in SCM pane. Expected result: the file appears under "Staged changes" section in SCM pane. Actual result: the "Staged changes" section doesn't appear in SCM pane. Happens on Firefox 121.0, Ubuntu 22.04. Doesn't seem to happen on Chromium 120 and WebKitGTK 2.42.3. Happens in GitHub Codespaces: Also happens with code-server: Also happens with OpenVSCode Server insider:
I'm experiencing the same or a very similar issue in latest code-server using Firefox. I can no longer open the repository in source control if there are any incoming/outgoing changes and instead am getting an exception in the browser console without the repository opening. Likely the reason the issue appears slightly differently for me is because I have multiple repositories in source control. For anyone else affected the following settings are making this issue to not occur:
Same here but not consistent: Version: 1.85.1 (user setup) Commit: Date: 2023-12-13T09:49:37.021Z Electron: 25.9.7 ElectronBuildId: Chromium: 114.0.5735.289 18.15.0 V8: 11.4.183.29-electron.0 OS: Windows_NT x64 10.0.
could you please try VS Code Insiders and see if you are still able to reproduce the problem? I have fixed couple of issues in this area and it would be great if you could try Insiders to make sure that this issue is covered by my fixes as well. Thanks!
Tested with OpenVSCode-server insiders, which is rebased on top of commit ("Sanity Bounds for "window.zoomLevel" ( ()") [1]. The issue still exists.


code-server doesn't release insider builds, and I don't know how to test insider builds of GitHub codespaces' web UI, so I can't test those. (Off topic, but does GitHub codespaces provide an insider build for web interface by any chance?) [1]:
if you open a GitHub Codespace, you can click on the "Gear" icon in the activity bar, and there is a menu item to switch to VS Code Insiders. You can try that out and let me know if you are still able to reproduce the issue. Thank you!
Thank you. Tested with the GitHub Codespaces + VSCode insiders [1], the issue can still be reproduced. Interestingly, if I change the to and then to again, the "Source control" pane essentially freeze: the "Incoming/Outgoing" section doesn't comeback, and further changes to the working directory is not shown anymore (like, if you add another file, it doesn't show up, even after I click "Refresh" button). [1]
thanks for trying this out. Could you please confirm that this indeed can only be reproduce in Firefox and everything works as expected in a Chromium based browser (ex: Chrome, Edge, etc)? Could you please the developer tools console and see if there are any relevant errors there? Could you also invoke the "Git: Show Git Output" command and send me the contents of it?
Yes. This only happens in Firefox. It doesn't happen in Chromium [1], and Gnome Web (WebKit-based) [2]. <details[1] <preVersion: 1.86.0-insider Commit: Date: 2024-01-23T06:18:07.155Z Browser: Mozilla/5.0 (X11; Linux x8664) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 </pre[2] <preVersion: 1.86.0-insider Commit: Date: 2024-01-23T06:18:07.155Z Browser: Mozilla/5.0 (X11; Ubuntu; Linux x8664) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.0 Safari/605.1.15 </pre</detailsThere seems to be.


As soon as I change to , this error pops up in the brower's console. And it seems to pop up every time I press "Refresh" in the source control pane too. <details<preUncaught (in promise) Error: Invalid comparison compare K K z w F E D C B z updateChildren Cc a promise callbackqueue Cc queue Cc W y fire z y z fire Lb wb reloadLocalUserConfiguration Hb updateValue updateValue Pc Mc b promise callbacktrigger Mc Lc ge y </pre</detailsHere it is. Although, I'm not sure how useful it is. <details<pre2024-01-23 10:40:31.442 [info] Log level: Info 2024-01-23 10:40:31.442 [info] Validating found git in: "git" 2024-01-23 10:40:31.442 [info] Using git "2.43.0" from "git" 2024-01-23 10:40:31.442 [info] git rev-parse --show-toplevel [126ms] 2024-01-23 10:40:31.442 [info] git rev-parse --git-dir --git-common-dir [9ms] 2024-01-23 10:40:31.442 [info] Open repository: /workspaces/core-base 2024-01-23 10:40:31.442 [info] git config --get commit.template [78ms] 2024-01-23 10:40:31.442 [info] git rev-parse --show-toplevel [65ms] 2024-01-23 10:40:31.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 [22ms] 2024-01-23 10:40:31.483 [info] git rev-parse --show-toplevel [5ms] 2024-01-23 10:40:31.501 [warning] ENOENT: no such file or directory,


open '/workspaces/core-' 2024-01-23 10:40:31.523 [info] git rev-parse --show-toplevel [5ms] 2024-01-23 10:40:31.523 [info] git rev-parse refs/remotes/origin/main [23ms] 2024-01-23 10:40:31.630 [info] git status -z -uall [89ms] 2024-01-23 10:40:31.631 [info] git rev-parse --show-toplevel [70ms] 2024-01-23 10:40:31.674 [info] git rev-parse --show-toplevel [18ms] 2024-01-23 10:40:31.675 [info] git config --get commit.template [4ms] 2024-01-23 10:40:31.716 [info] git rev-parse --show-toplevel [26ms] 2024-01-23 10:40:31.718 [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 [12ms] 2024-01-23 10:40:31.736 [warning] ENOENT: no such file or directory, open '/workspaces/core-' 2024-01-23 10:40:31.755 [info] git rev-parse refs/remotes/origin/main [20ms] 2024-01-23 10:40:31.784 [info] git merge-base refs/heads/main refs/remotes/origin/main [30ms] 2024-01-23 10:40:31.855 [info] git status -z -uall [84ms] 2024-01-23 10:40:31.863 [info] git rev-list --count --left-right [17ms] 2024-01-23 10:40:33.111 [info] git config --local [138ms] 2024-01-23 10:40:33.


111 [warning] git config failed: Failed to execute git 2024-01-23 10:40:49.678 [info] git config --get commit.template [2ms] 2024-01-23 10:40:49.709 [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 [5ms] 2024-01-23 10:40:49.732 [warning] ENOENT: no such file or directory, open '/workspaces/core-' 2024-01-23 10:40:49.733 [info] git rev-parse refs/remotes/origin/main [1ms] 2024-01-23 10:40:49.768 [info] git status -z -uall [9ms] 2024-01-23 10:40:49.854 [info] git merge-base refs/heads/main refs/remotes/origin/main [2ms] 2024-01-23 10:40:49.873 [info] git rev-list --count --left-right [2ms] 2024-01-23 10:41:41.011 [info] git config --get commit.template [15ms] 2024-01-23 10:41:41.012 [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 [3ms] 2024-01-23 10:41:41.026 [warning] ENOENT: no such file or directory, open '/workspaces/core-' 2024-01-23 10:41:41.029 [info] git rev-parse refs/remotes/origin/main [2ms] 2024-01-23 10:41:41.049 [info] git status -z -uall [7ms] 2024-01-23 10:41:41.


112 [info] git merge-base refs/heads/main refs/remotes/origin/main [2ms] 2024-01-23 10:41:41.131 [info] git rev-list --count --left-right [3ms] </pre</details


Refs: x, open our in a docker container with node10 install, open debug viewlet create a by clicking on the launch gear and press debug start a port 3000 to your localhost 3000. Hit the port locally and notice how you get the application Forwarding port 3000 a port localy and notice that you still get the application even though you stopped the forwarding :bug:


]- Identify accessibility bugs before check-in and make bug fixing faster and easier. #A11yTCS; #A11ySev2; #DesktopApp; #Win32; #Visual Studio Code Client; #BM-VisualStudioCodeClient-Win32-Jan2024; #WCAG1.4.11; #Non-text Contrast; #A11yWCAG2.1; Visual Studio Code insider version 1.86.0 Microsoft Windows 11 Enterprise (22H2) OS Build .3007 Visual studio insider the Visual Studio Code Marketplace, go to the GitHub Copilot extension page and click Install. a sample code and press CTRL+I to open the Copilot inline chat. that the contrast ratio of focus is on "Make request" button is (1.787:1) which is less than required. While navigating with Keyboard tab key to the "Make request" button the contrast ratio of focus is (1.787:1) which is less than required. While navigating with Keyboard Tab key to "Make request" button the contrast ratio of focus should be greater than or equal to required (3:1). Keyboard users will face difficulty while navigating through keyboard if the focus is not clearly visible to the user and ratio is less than required. !
Verified the issue in below environment: Visual Studio Code Insider Version: 1.87.0-insider (user setup) Issue is not fixed. Please find attachment for reference. Could you please confirm us in which build the fixes will be available. <img width="785" alt="203773_not fixed" src=""
The focus border now has increased contrast and is now the same colour as everywhere else in VS Code. We don't have any indication from users that this accent colour is a problem anywhere in the dark theme.


! VS Code Version: Version: 1.64.1 Commit: Date: 2022-02-07T17:17:47.733Z Electron: 13.5.2 Chromium: 91.0.4472.164 14.16.0 V8: 9.1.269.39-electron.0 OS: Linux x64 5.13.0-28-generic OS Version: Ubuntu 20.04 Steps to Reproduce: a Jupyter notebook, just do Ctrl+H and put some strings in find and replace boxes.
Hi - Apology to bother. Is there any update on this issue or any work-around that I can do. Because without the replace-all functionality, it's becoming very hard to manage long notebooks in VSCode.
Just realized this is a regression from previously stable.
NOT Resolved in the latest stable version of code.
Not working on the latest Insiders Version: 1.66.0-insider (user setup) Commit: Date: 2022-03-29T07:31:54.286Z Electron: 17.2.0 Chromium: 98.0.4758.109 16.13.0 V8: 9.8.177.11-electron.0 OS: Windows_NT x64 10.0.
After updating to version 1.66.0 - I get the "Replace All" button activated (as in not grayed-out any more) - But it does NOT work. i.e. after clicking on the button naothing happens.
Hi, this is still not resolved after today's release to Version: 1.67.1 Below my current version details.
can you try again on VS Code Insiders? Otherwise, you'll have to wait for version 1.68.
Great its working in the Insider version. Thanks.


Issue Type: <bBug</bTesting: Steps: a with one or more npm scripts a and add one or more npm tasks but do not add a details field to each task the run tasks command that the npm scripts in have a details field shown but the npm task in does not Expected: All npm tasks/scripts to be rendered consistently. The npm task in should show the script as the detail field just like the ones in ! VS Code version: Code - Insiders 1.40.0-insider (, 2019-10-30T05:39:27.063Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (12)</summaryExtensionVersion ------ tslint1.0.44 vscode-github-releases-updater0.18.0 vscode-docker0.8.1 python2019.10. remote-containers0.82.0 remote-ssh0.47.2 remote-ssh-edit0.47.2 remote-ssh-explorer0.47.2 remote-wsl0.40.0 vscode-remote-extensionpack0.17.0 azure-account0.8.6 test-search-rg0.0.3 </details<!-- generated by issue reporter --
which of the tasks listed in your screen shot are from the If it , you have npm task detection turned on, and the script is also in your then it should show a detail (except for npm:install).
The npm install task is the one in
Sorry, seemed to close the issue by mistake while trying to paste a snippet from { "type": "npm", "script": "install", "problemMatcher": [] }
And this is in "scripts": { "test": "echo "Error: no test specified" && exit 1", "random": "do something else" },
Thank you! There is no detail to provide for install since it's not running a script defined in to pull the detail from. I figured there wasn't a good detail to show for it, but I'm all for it having a detail if there's something relevant we can put there. Is there something in particular that you want to see as the detail for the install task?
I just thought it should do similar to the scripts in the and show the script field?
I see, so it should just show "install" as the detail.
Upcoming behavior: !


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.67.0 OS Version: Windows 10 Steps to Reproduce: Please add some margin there, I've Provided img below and pointed out that place with red clr It's Just Sticking each other !
Sorry can you clarify what you mean?
As, You can see in the img I've pointed out a terminal place with red clr circle where Source Control is there and ahead of it 1 Badge is there. So, Then it's below line and the Badge does not have any space/margin they both are sticking.
I see space between the badge and the active indicator,
I think it's too small.
I think these changes when the panel padding got updated with the secondary side bar. Not sure what else we can do besides add the padding back. It is quite tight right now.
Should be fixed now thanks to <img width="127" src="https://user-"


I would expect a "..." overflow behaviour here: !
Fixed in , please review


<img width="584" alt="image" src="https://user-"//cc for views
I assume this is nothing to do with the views instead its about how entires are rendered in list/tree. CC
Tree row contents are outside of the tree's jurisdiction, but are in fact responsibility of the widget user.
Timeline doesn't use the extension tree view and instead does it's own thing. I think works on timeline.
curious, do we have an understanding what caused this? it seems relatively recent?
Might be related to . any ideas here?
It was caused by , can you check? I see a visual difference not only with the alignment but also the spacing: Before <img width="254" alt="image" src="https://user-"After <img width="269" alt="image" src="https://user-"
it looks like timeline relies on the custom tree view css. I made a change in the nesting/ordering of elements in the tree view recently and I updated the css to reflect that. Because timeline relies on the css but doesn't actually use the custom tree view, this broke the timeline. I've opened a PR with a timeline specific css fix.


VSCode Version: 1.2.0 OS Version: all Steps to Reproduce: from the command palette while not debugging a error: !


Most macOS apps (like ) use em dash () instead of en dash () as window title separator. I suggest VS Code use em dash for better consistency.
PR welcome.
Can anyone explain a bit about it ? Thanks


<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.41 OS Version: Ubuntu 18.04 Steps to Reproduce: a debug adapter the pause feature the debug adapter and see that pause works the debug adapter using the restart button that pause no longer works <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No The commit is used to slow down fetching threads from a debug adapter. However, when using the default restart mechanism, is disposed (via and therefore no longer runs after restarting the debug adapter.
Thanks for filling this issue. Can you be so kind to fork Mock Debug and to create changes on top of it such that this issue is reproducable. Since I can not reproduce it using node - gif attached !
It looks like I was missing sending an so the same debug session was being reused after restart.
I also made this comment in the pull request: The says "A debug adapter is expected to send this event when it is ready to accept configuration requests (but not before the ‘initialize’ request has finished)." So either the specification needs to say "required" instead of "expected" or there is a bug in VS Code. VS Code doesn't seem to correctly handle the situation where the debug adapter never sends . Although the fix may be to create a new debug session object instead of the fix that I have proposed.
Simply removing the line that sends from the mock debug unfortunately extension doesn't seem to be enough to reproduce the problem, but since I found a workaround, I can't really justify spending more time on it.
did you verify that this works with the latest VS Code insiders as expected?


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --- VS Code Version: 1.50 OS Version: Windows 10 and Mac OSX Catalina Steps to Reproduce: to a remote server the remote server's extension host to crash, possibly by running out of memory or by killing the process yourself. the remote server's extension host has crashed, attempt to file a bug by clicking the bug nub icon in the bottom right corner of the main window. Expected Result: Issue reporter window appears and allows user to file a bug Actual Result: Issue reporter window fails to launch. If you check the debugger, you will see that an exception stack trace for "ExtensionManagementService.getInstalled". Since the remote extension host is not active, doesn't work - it throws an exception rather than returning an empty list. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported direct to the extension publisher. The 'Help Report Issue' dialog can assist with this. --


VSCode Version: Code 1.14.2 (, 2017-07-19T23:34:09.706Z) OS Version: Windows_NT ia32 10.0. Extensions: ExtensionVersion ------ cpptools0.12.1 csharp1.11.0 Steps to Reproduce: an empty folder with VSCode a new MSBuild task building (execute task) Expected: Fails gracefully somehow Actual: Just spins forever and never dies until I manually kill the task. Note: this also happens when I mistype a path or something in the command to a directory that say for example doesn't exist. If the command is wrong in some way, the task will just spin forever. <!-- Launch with to check. --Reproduces without extensions: Yes/No
The terminal doesn't send an onExit or any other event in this case so that the task system could determine that the process has finished / died. Steps to reproduce: Windows, no msbuild installed fresh workspace configure task runner select MSBuild from the list of templates F1 Run Task Select Build Observe: the spinner never stops. Could can't even terminate the task. The reason is that the shell actually fails to execute msbuild however the terminal never send an onExit event. Look at the process explorer there is a lingering vscode process of --type=terminal <img width="521" alt="capture" src="https://user-"
I upgraded to node-pty which may improve the problem, if not I'd guess this is related towinpty is not terminating the processes correctly.
I retested this and it is still happening under Insider today.
terminalProcess stalls on this native call: , meaning this function never returns Not sure why a or native exception isn't happening.
This has the same root cause as
Moving to September as this is a more involved change than I anticipated. More testing in Insiders would be ideal.
any news on this. Do I need to adopt something here ?
No progress, I moved this to September before I knew that I would be out for 2 weeks in September.
It does look like it affects Windows only.
Hmm, I believe that I just came across this while trying to run some tests, and exited with an error code. I was able to reproduce it using this: Everything works fine if the error code is changed to .
Was this never solved?


when I last tested this I had the impression that this is still a bug and the terminal hangs (doesn't signal on exit).
Yes, this is still an issue.
Is this in line to be fixed btw?
This still happens btw when I'm doing my PowerShell development.....I have to keep restarting all of VSCode because my debugging sessions won't end properly.
does this sound like something that will be fixed by conpty?
it probably needs a check in node-pty that the file exists before attempting to fire it. It's possible that conpty would fix this but that would only fix it for newer Windows versions when the fix should work when we fallback to winpty.
There's already a check in node-pty before attempting to execute the file. I can't actually reproduce this with a garbage command in my task (ex. ) I do think I'm seeing this when I pass garbage in for the that results in a failure though: 'c:usersalrosdesktop' is not recognized as an internal or external command, operable program or batch file.`


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.58+ OS Version: Windows Steps to Reproduce: with and . the browser launches, the server throws. This is due to: It should just be . I have a PR to fix this, but needed an issue to reference.


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --- VS Code Version: From sources !
That looks grid related to me.
Web bisect points out this commit range which includes the move to the new table widget: This seems to require the custom menu (Windows, Web) to reproduce.
fyi, not sure if anything within the keybindings editor could have caused this other than adopting the table widget.
Can also be reproduced by focusing the search input and then tabbing until the table is focused Created a PR fixing this.
Tagged this as candidate as the experience is bad with custom menu and it is a regression. As mentioned it can also be reproduced everywhere with following steps: Open Keybindings editor Focus search input Tab until table is focused Editor title bar is not visible


I can reproduce this in my Stable VS Code 100% of the time. I can not reproduce in VS Code Insiders. Click on the Account icon in the activity bar -nothing happens Open developer tools console and notice exception
Assigning to as well, since and me investigated and it seems like the value in my KeyTar got corrupted and can no longer be JSON parsed. We tried with a fresh user data dir and we could still repro since the same KeyTar is used.
can you run this simple one-liner and tell me if you get a value?: This is using the following open source package: What you should get is something like this: If that returns a value, then I'm shocked that it did because nothing in core sets that (only embedders do this in the web)... could an embedder be writing to this on accident? If it doesn't.... that's also odd since your stacktrace is
I just ran that, and yes I get
verification: this: vscode insiders in to an account/open the account menu It shouldn't throw the error above.


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.45.1 OS Version: OS X 10.15.5 Beta Steps to Reproduce: a text file whose name is just a number, e.g. , , etc to launch the file from the command line file is opened. If VSCode was closed, it starts and just shows the welcome screen. If VSCode is running, you see another VSCode icon bounce in the dock and go away. to file to something else, it works fine <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
I have a feeling we've seen this before?
yes I remember something was not right with our argv lib (minimist?) with regards to handling numbers?
Hi, was having this problem too and I think I found the cause We were discarding empty args as part of , however this would discard numbers too as they were not strings when the check took place Have made a PR to remedy this if that's ok


Since we already have the command in the pallet, it would be nice to expose it in the UI. Here: <img width="302" alt="screenshot 2018-10-29 at 09 51 10" src="https://user-"


I'm seeing the following message in Insiders: The setting is also not in the user tab of the Settings editor with profiles enabled.
Fixed in commit, github just didn't close this issue :(


create a notebook and save it. Run a cell with a kernel. Change the kernel and run another cell reopen the notebook as plain text and note the kernel spec in the metadata. metadata should specify the kernel that was most recently used, but it specifies the original. Seems to repro with both local and remote kernels
impacts microsoft/vscode-jupyter since we're not getting the correct suggestion
I think this is a regression. please could you verify this works as expected in stable.
yes, the kernelspec updates in stable as expected
This is actually a bug in the new metadata API. Transferring to vscode core.
This should've been assigned to since we are adamant in verifying each issue that gets shipped in a recovery release individually. I found this out by looking into . Please find someone to verify this issue in the latest release candidate build.
Oh my bad... this was released already in ... My mistake.
But there's still a recommendation: this should've been assigned to all along so people verify the issue was fixed. Can you find someone to verify and mark it as ?
I had actually verified back when it was fixed, just didn't add the label since it wasn't marked verification needed. I'll do that now tho
Thanks!


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: OS Version: Windows 10 -- Ref: Steps to Reproduce: theme to new terminal cursor is white on a light background which is hard to see for most I'm about 99% sure this is not associated with any customized profile in use for PowerShell session. Starting with no profile shows the same thing. !


VSCode Version: 1.34.0-insider (1.34.0-insider) OS Version: macOS mojave 10.14.4 Steps to Reproduce: in activate method of any extension. the developer tools. What is expected? Show the file dialog like following: ! What is actually happening? Following error message shown in the Developer tools. Does this issue occur when all extensions are disabled?: Yes According to the code here: , I think the reason is " is ", then I got as the of see here: If you confirm this is a bug, I'd like to create a pull request to fix it.
I think I find the commit which cause the bug, see: Here we transform the " and " to " and ", but the args that send is still , and because it send undefined in my case, I got as , then the error throws. Since I find the cause of this bug, I feel confident to create a pull request to fix it. : )
Yes, PR is welcome!


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: OS Version: Steps to Reproduce: Python issue reporter selects (, instead of )


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: Version: 1.81.0 (user setup) Commit: Date: 2023-08-02T12:37:13.485Z Electron: 22.3.18 ElectronBuildId: Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0. Steps to Reproduce: a .cpp file (or a .c file). Don't have the C/C++ Extension Pack installed. Bug: The extension recommendation popup uses text "for C++ language", which isn't grammatically correct. It's possible the same issue repros for other languages. I wasn't able to locate the source of the text (maybe it's from a private repo). ! Potential fix 1: It should use "for the C++ language" to be grammatically correct. Potential fix 2: Well, to be even more accurate, for the C/C++ extension pack, it should say "for the C and C++ languages". Potential fix 3: Or, if it can say "for the C++ language" when triggered from a "cpp" language file and a "for the C language" when triggered from a "c" language file.
can I work on this issue?
Are you able to locate where that text is coming from?
been searching the text source for some time but not able to find it. Did you find anything?


No, but I don't work on VS Code (just an extension) -- I assume someone who works on VS Code would know how to find it.
I was just searching some beginner friendly issue to solve to start my open source journey.