{"_id":"doc-en-vscode-82b12bc7b10cd2ceb7c08b184832e12ac5b908a468b6a1858a1b6f631f8d5aba","title":"","text":"I'd like a setting to optionally prevent deprecated things from showing up in intellisense suggestions. For example, I'd like a way to prevent from being suggested here, so that I don't use it despite a non-deprecated version being available. ! My linter can catch it, but it'd be even nicer never to see the deprecated option. There are several documentation systems that use the tag: JSDoc: TSDoc: JavaDoc: Yard (for Ruby): Other systems use different, similar tags. I'm not sure if this is an issue for the VSCode core, or for something language-specific.\nSorry if this is a duplicate or is already possible. There are enough issues here and questions/answers on Stack Overflow that it's hard to be confident. This issue is related:\nNot showing deprecated suggestions can be implemented by individual language extensions today (not striking out but tracks that). Adding just to see this is something we want better VS Code api support for in some way Otherwise, we can track this as a feature request for js/s\nI'd say this is a dupe of and it would be us adding some API flag and then allows users to configure how the suggest UX is handling that flag\n/duplicate of\nThanks 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 existing issues . See also our guidelines. Happy Coding!\nOkay, that makes sense. What does \"js/s\" mean?\nis it possible to add a setting like , so I can disable it to prevent deprecated from showing up in suggestions list?\nHey any update on that?\nVerify that the setting exists and that it filters deprecated elements from IntelliSense"}
{"_id":"doc-en-vscode-840d76df06b21f03500dc82e2855aaf3080c8dc3c975d89a1918440e84e0180a","title":"","text":"To be verified with: : : set the new config options start debugging The hover provider should be invoked."}
{"_id":"doc-en-vscode-017f185dc350d5372d9054b30d14363e83f9f53d07ab4ab55ac5233b9c354e20","title":"","text":"Add support for setting the contents of files created by workspace edits My proposed would be to add a option to : For , we want to support copying images from desktop into with drag and drop. Right now we have to use the apis to create the image file Using a workspace edit would let us express the entire operation in a single , which will play more nicely with undo/redo\nLooks like support for this may already exist internally: However getting a of new file data from the extension host to the main process may be tricky. We can only efficiently serialize a if it is a top level argument to an RPC call or if the entire object is wrapped in a (which has a perf cost). Open to ideas on how to handle this\nI do like the and believe the cost is manageable - we don't send edits is large frequencies and of large sizes. I can take a look at this but it honestly is stretch for June - there is some debt in how workspace edits are represented on the wire and I would take this issue as a reason to clean things up\nwork started here: I didn't bother with or hoisting the data to the top but instead it uses quick and dirty base64 encoding. I'd suggest we go with that and see how it works out over time."}
{"_id":"doc-en-vscode-df574441d5ead7df321170d1878ee77f2392b250feeacadf74c8511b7a8916fd","title":"","text":"It appears that this is possible now, and we should consider adopting this in VS Code ()\nThere is community interest:\nPlease add this!\nSteps for verification: Connect to Windows arm64 using the latest pre-release of SSH extension () Verify that connection is successful Use or similar tool to confirm that executable is of architecture."}
{"_id":"doc-en-vscode-74a2c415efe388a711988b38ad25f31e1521831d925da699b08074c21030243f","title":"","text":"Testing Just like I can set the display language in the compact presentation of the extension view, I'd have expected to be able to reset the display language there in addition to the details page of the extension. <img width=\"1118\" alt=\"image\" src=\"https://user-\""}
{"_id":"doc-en-vscode-ba5bd6d17e1523864461014f8543a8171251190b2735023d5b9d38fbb1bf33c4","title":"","text":"Collapse an output, it is not hidden in the webview <img width=\"596\" alt=\"image\" src=\"https://user-\"\nmaybe ?"}
{"_id":"doc-en-vscode-3719c789f525efbbd73143a892b037ae53682d56cc2f30a1bafc110f49da2acf","title":"","text":"I tested on Win11 & Win10. It works as long as you start a new workbook and don't save the jupyter notebook. Once you save the notebook, your pastes of images from the clipboard will no longer be treated as inline attachments. Originally posted by in\nPossibly getting overridden by a markdown file paste provider?\nwere you able to replicate my findings?\nReviewed this thoroughly, and found the following. All cases are performed with a screenshot copied to the clipboard, and pasting into markdown notebook cells using ctrl+v. Using Windows 11 and current insiders. With setting unsaved notebook (command pallete -new jupyuter notebook -) results in broken markdown image link pasted, broken rendering (see screenshots attached) ! ! saved notebook creates image file on disk, creates markdown image link, renders correctly. With setting unsaved notebook (command pallete -new jupyuter notebook -) results in correct inline attachment image link pasted, renders correctly saved notebook results in correct inline attachment image link pasted, renders correctly\nWith the above investigation, I believe this is likely an issue with markdown paste providers, assigning to take a look at this. to clarify, are you expecting the images to be created on-disk upon paste, and referenced via an image markdown link? Or are you looking for the experience, with images stored in the notebook itself. The latter can be achieved and still works properly with the setting\nI prefer the later, where the images are stored in the notebook, this makes it easier to share with others in these scenarios. This used to be working and then stopped working in the build I noted in the original question refenced, but I just tested in the latest build and it is back to working as expected, so must have been a bug that has now been fixed: The version I just tested with is updated now and it is working as expected with the Version: 1.83.1 (system setup) Commit: Date: 2023-10-10T23:48:05.904Z Electron: 25.8.4 ElectronBuildId: Chromium: 114.0.5735.289 18.15.0 V8: 11.4.183.29-electron.0 OS: Windows_NT x64 10.0.\nWorks fine for me too with the default settings. Will disable pasting into untitled notebooks with the setting off"}
{"_id":"doc-en-vscode-7f49814325ee7c26f3f0d46285c2398619dc635994645fb73928ed99a04688d9","title":"","text":"<!-- 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: 1.86.2 OS Version: Not relevant Steps to Reproduce: a new file <kbdCTRL</kbd<kbdSHIFT</kbd<kbdP</kbdand choose YAML <kbdCTRL</kbd<kbdS</kbdthat the extension is ! YAML's documentation recommends the extension: see"}
{"_id":"doc-en-vscode-e70c99c61059d4634bd40b3f9132f0123f8361937f5d4f5481c7209c06369086","title":"","text":"In VS Code we able to push git repos to different places with \"git push to\" and choosing the remote server to push. I'll be nice if we can be able to choose from the repo to pull files, and manage the default remote, today the first remote repo is the default isn't possible to change that via VS Code\nThanks for all your contributions. You all created a PR to solve the same issue; all in a surprisingly similar way. I wanted to keep the record of all your work so I did an octopus merge with git, thus keeping your names in history. Thanks once again!"}
{"_id":"doc-en-vscode-18f92fc07cc41a5a3a9fbb564356ec5991fcd2309660beb1b885f44016f53c86","title":"","text":"Issue Type: <bBug</bsearch.maxResults to a value larger than some text in file which may have results more than \"Open in editor\" in search panel search editor shows \" results - 1 file The result set only contains a subset of all matches. Be more specific in your search to narrow down the results.\" and only results shown in search editor VS Code version: Code 1.58.0 (, 2021-07-08T06:54:55.083Z) OS version: Windows_NT x64 10.0. Restricted Mode: Yes Remote OS version: Linux x64 4.15.0-136-generic <details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\n(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.468 --- <!-- score: 0.45 --<!-- potentialduplicatescomment --\nAccidentally already created a walkthrough of how to resolve this in so I'll post it here: To reproduce, set the max results setting to some larger value, and run a search in the search editor which has more results than the value: ! ! Access search editor with: ! You can start by changing the limit passed here to read from the Then, you should add a way for the search to be re run with no limit. See what happens in the search from the sidebar, whose code is here: for how to make that change.\nHello, , I would like to work on this issue. As-is: Search Editor has maxResults fixed to To-Be: Should use a maxResult value from configureationService and with no limit if value is null Am I understading the issue correctly?\nyes that is correct. Thanks!\nHey have you started working on this? If not, I'm interested on picking it up.\nI've been busy so I have not done much, so you can pick it up. I realized it requires more time than I previously expected. As far as I see, making search editor to rerun the search results with polling like the search view requires some work...\nIt is by design that the search editor does not stream results, this causes undesirable behavior in an editor context when you may be in the process of manipulating the results. For this ticket simply respecting the setting is sufficient."}
{"_id":"doc-en-vscode-d9266651ba1dd37c5be5f99c63fb8c05f560e46002463ee37e8b32dcdd866286","title":"","text":"In that case, I have just done that, however, I still need to resolve what to do when the maxResult is null, because the editor will hang and crash. What would you suggest I do?\nIt's cool, I'll pick up another issue."}
{"_id":"doc-en-vscode-e4c135855d2f128ad002426ad26c970030072ab59d9b0e1324d77410c1f2df1a","title":"","text":"Testing There no documentation on signalOptions: ! There is some documentation on the leaf properties in the JSON, but it is unclear what refers to.\nI think the request was to have an overall description for the setting, as right now there's nothing until a user starts to complete properties in the <img width=\"636\" alt=\"image\" src=\"\""}
{"_id":"doc-en-vscode-eda9d7ff9d923b4b4da2286edfa193f00b53a40fc9d5236fbb55dbd5c8b897a9","title":"","text":"Type: <bBug</bHow to reproduce the issue: and Run the Extension the , and then the pane. Use the dropdown and select the Dynamic Configuration Provider . With the checked out branch, it will show the quick pick options for Option 1 - 3, but will not show a quick pick for the resolved configurations. This seems to work for , but not Expected: ! Actual: ! VS Code version: Code 1.77.3 (, 2023-04-12T09:16:02.548Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nThanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.78.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!\nI've updated to: and it still reproduces.\nfor prioritization help as per email thread\nSent a PR for this. But what is the inner quickpick? I'm a little unsure about the approach, I don't think we expect a provider to include some UI. Your extension doesn't own the UI in this flow- you are just implementing a provider method which will be invoked at different times, expected to return a list of configs. It might make sense in one situation to show the quick pick, but we could make changes in vscode to call your provider at a different time where it would be unexpected to have a quick pick pop up. And, any extension can implement a config provider for your debug type. So for example, multiple extensions could all be showing their own UI in this scenario. However, from memory, I think the Python debug extension might already have a similar multi-step picker UI for a scenario like this."}
{"_id":"doc-en-vscode-7f8130b888cea50f1aa3a5d64fa147b3c38ab865e83ffe613b6cbfe981629aaa","title":"","text":"Testing an extension that logs some infos and some debugs. the extensions log and see the infos \"Developer: Set Log Level...\" and choose \"Debug\" something in the extension that causes the debug logs to happen. at the log again and see that the debug logs are not there.\nError and trace also don't log."}
{"_id":"doc-en-vscode-1f40c5aff5f9bdc441e154cc96afaba3e209d322d9f0b0e67cdd4f03e077048c","title":"","text":"Testing When my cursor isn't inside of a conflict, this command does nothing. Should it only be visible in the quickpick when it does something? Or should there be an error message when you try to run it but it doesn't do anything? Same with the \"Toggle Current Conflict from Right\". <img width=\"549\" alt=\"image\" src=\"https://user-\"\nI fear if we hide it when there is nothing to toggle, users won't discover that there is a (keybindable) command for this functionality. How did you find this command? Was your cursor in a conflicting region?\nIt wasn't in a conflicting region at the time\nLet's show an error message if this command does not do anything.\nIf I run the toggle command in an invalid region, I get a notification, which is good. But, if I then toggle a valid region after, the notification still stays on the screen for a while. Can the notification be hidden when the user toggles a valid region?\nCan notifications be removed? I thought that is not possible. Also, I think this use-case is quite rare. The notification is just to teach that you should be in a conflict."}
{"_id":"doc-en-vscode-ce9390599de0f5a15f300ae7a2d74be908519210bdfb54f2049a08f755a13935","title":"","text":"<!-- 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?: 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: Current OS Version: Web issue only (repro) The repro steps for this are entering via the VS Code for education route for Steps to Reproduce: to with MS credentials the courses list, select the 'Getting Started' course should be launched with our extension and course loaded this point you can already see the errors in the dev console to see the specific issue select the \"Coding Challenge\" section ! In this section a code editor file should have been opened up in the editor, but it is missing. We see the following in the dev console when the course is loaded. I don't have a full bead on exactly what is happening here, but we have not been changing the extension this sprint, so it seems to be a recent new issue that is just in insiders and not in stable (which works fine still and does not have the errors). ! I took a look at recent issues and this one comment appeared here that might be related?\nAdding the log file here.\nFor comparison, this is the same scenario in stable ! And insiders: ! Note the errors, plus terminal and editor have not opened up.\nHope you don't mind a direct ping here, but I think you might have context both on the VS Code for Education route and possibly on the issue above?\nthis is related to Looks like we may need to add to the iframe content security policy. Taking a look at this now cc\nI was able to verify the issue has been addressed in latest insiders following the steps from OP. please also confirm on your end. Thanks!\nLooks good now. Thanks for the quick fix!"}
{"_id":"doc-en-vscode-59ec34fa0d2c580a0fd711934974f78d78aa15bb093f370657f6d275031f4d4d","title":"","text":"returns the same results as . The first should have applied, the second should have no exclude settings applied. The parameter in the findFiles API treats differently from . Strict null checking extHostWorkspace broke that:"}
{"_id":"doc-en-vscode-7b16029728ed5b4c7ccf1a32b60f62af55e833c72d69818217f4b42969c9c6cf","title":"","text":"From Probably a regression from making aarch64-linux ripgrep build statically compiled to fix We might need to dynamically compile ripgrep instead of using musl, and find a container to compile it in. related // cc\nLooks like jemalloc just needs to be configured with to support 16K page size. This can be achieved by setting the environment variable: (16K page size) Or to support 64K page size as well: (64K page size) In either case, it'd still work for 4K/16K(/64K) page sizes.\nDo we have any good news on this? I found the similar thing happened before on other application like , probably we can use the same approach to solve this one?\nAny update on this issue ?\nTemporary Workaround: To address the issue until it is fixed, follow these steps: Install ripgrep and obtain its path. For Rocky Linux or any RHEL-based Linux distribution, run the following command with root privileges: For Ubuntu, use the following command: Alternatively, you can install ripgrep using Cargo: Verify the installation and retrieve the path by running: Replace the broken rg with a symlink by executing the following script. Please note that you should remove the echo commands to commit the changes: This workaround should help resolve the issue temporarily.\nThis should be fixed in tomorrow's VS Code Insiders. Please try it out and let me know if it works for you!\nI tried but it seems not fixed or not included the fix. execute from the remote server(aarch64) and got <jemalloc: Unsupported system page size <jemalloc: Unsupported system page size memory allocation of 5 bytes failed find: ‘.vscode-server-insiders/bin//nodemodules/ terminated by signal 6 (after resetting the remote environment by deleting .vscode-server-insiders folder on the remote, and vscode reloaded. - 'Developer: Reload Window')\nAre you running 16K page size or 64K?\nI got $ getconf PAGESIZE on the aarch64 remote (Rocky Linux 8, aws r7g instance/Graviton3 processors)."}
{"_id":"doc-en-vscode-c9597dd3daa9a2fbaf733df747db87bc72326aa409b2afb0a05cd736034c940c","title":"","text":"Meanwhile, executing the same command above on x86-64 remote, I got the normal rg help print out as like error: The following required arguments were not provided: and correcting the hand typed typo above of vscode insider version info Version: 1.79.0-insider (user setup) Commit: Date: 2023-05-19T20:39:14.598Z Electron: 22.5.2 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: WindowsNT x64 10.0.\nHmm ok. I tried setting the env variable to increase max page size for jemalloc, but it seems to not be working. I'll try another approach.\nIf you let me know what you are attempting, I can also try out some stuff. Page size here is\nIs this fixed in the latest release version of VScode? I just check on my arm64 container but it seems not working. VScode Version: 1.79.0 (Universal)\nSame with Switched to newest insider build. . Problem not solved. Went to server, killed and deleted . Tried again to bootstrap. Problem is still NOT resolved. Search is still limited to open files.\n!\nHere is some useful link detailing what I think is the problem. Not sure if it is resolved by now. But if info from the discussion is current, I think you will have to either compile on the target system, or ship different precompiled versions of binary and select the correct one depending on the system specs (see ).\nWe do cross-compile for different systems for ripgrep I'll have to take another look.\nSo, my interpretation is, that the page-size is hard-coded into jemalloc. When the system page size at runtime differs from the one it is compiled for, it will fail. In other words, the one shipped right now fails out of the box: From your linked repo, I understand that you now focus on 16k page size. That would also not help me (if my suspicion is right), as my system's page size is: 64k\n: Temporary fix. Bootstrap on target ARM system. You should have a directory called now. That is where the vscode server lives."}
{"_id":"doc-en-vscode-c3fff5616eafff128e9e194bda94d5c726af0283e1c82fe3f48a8b3006f1c405","title":"","text":"Download and compile : Replace binary deployed by with custom compiled version. Now search should work as expected.\ncan you check if the following runs fine on your aarch64 setup ? The build is generated from to use 64k for jemalloc.\nThanks built from source works for me!\ncan any of you verify this:\nI untar-ed the file and the binary 'rg' is working good with remote search. (I sym-linked it with vscode 1.79)\n<!-- 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!\nI can confirm it is fixed with the vscode insider downloaded a minute ago of (assume the commit hash changed since)\nthanks so much for checking!"}
{"_id":"doc-en-vscode-1cadd7d624ac7a7ff7bf100e6cdad2a8dc3ae8df623f7da0a035d0234829a832","title":"","text":"Reproduced on OSS, Mac Steps to Reproduce: Code OSS a file cmd+w Closes the window Bisect points to this commit -\nI can reproduce and this is likely context keys not being set properly because conditionally closes the window if no active editor. !\nThere are context keys that are now loose, for example\nFollow up work"}
{"_id":"doc-en-vscode-70a50f05db4cdfd9d8760f70594cc5dc9b23147606cbc2654d9e82941629cf23","title":"","text":"Composer is the dependency manager library for PHP. Its lock file is a JSON file, but it's called by default, so Code doesn't treat it as JSON. It would be neat if Code treated this as a JSON file instead of a plain text file."}
{"_id":"doc-en-vscode-53e8d6a6188c11969daa3ca718392931fc199a2e414ec2188fe17881c371dd37","title":"","text":"Same as when opening a diff editor, a merge editor should offer a way to open the regular file (not in 3 way merge mode). Same as diff editor it could use an action in the editor title area !\nLet's move this to July\nTo verify: open a merge editor verify its title bar has a command to open the result file\nI wonder if \"Open Changes\" button should go back to the merge editor then? !"}
{"_id":"doc-en-vscode-7b8513057f217d56819380bc073721412a78103086d8fefbfafb2165c9b6e57c","title":"","text":"!\nCaused by I caused when I fixed an issue when there are multiple text editors open with the same uri with comments. When I tried to fix I made it so when extensions call and pass in for the comments, we always expand the reply editor, resulting in the bad behavior above. I took a quick look, and it seems very common for extensions to pass in for the comments and then immediately set them.\nTo verify: Check out PR with comments that you left Reload to make sure there's not state left over from when you left the comments Open the file with the comments and click on the comment icon in the comment bar to expand a comment that you left Verify that the reply input button is collapsed and isn't a big empty rectangle.\nWorks great -verified.\n<!-- UNABLETOLOCATECOMMITMESSAGE repo --Issue marked as unreleased but unable to locate closing commit in repo history. If this was closed in a separate repo you can add the label directly, or comment .\n<!-- UNABLETOLOCATECOMMITMESSAGE --Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting , or directly add the label if you know this has already been releaased"}
{"_id":"doc-en-vscode-720078617db905967f399b60621c0c6d35a7b73719eb5c6faa30832b73f0b213","title":"","text":"Code, search for \"bracket pair colorizer\" how it is nicely rendered as deprecated on install -notice dialog The dialog should offer a third button to configure built-in settings instead. Same if an extension had an alternative extension. Example: ! fyi\nI assume you want the extra button to replicate this link in the hover tip, right? ! As an aside, any doc yet about how an extension gets tagged as deprecated?\nyes, a button that will replicate that behaviour correct. No docs yet written. I plan to add them soon. The process is to write an email to us or to ping us on GitHub. In the future we will have a more straightforward approach when MP adds UI.\nI feel, the third option would be a general options like More Information... clicking on this shall open the extension editor. This will be consistent and useful so that user will get enough info before taking an action\n\"More Information...\" might work, but in order to have one less hop we could render: \"Install EXTENSION_NAME Instead\" \"Enable Native Settings Instead\" That would just do the action right straight away. I am not sure if those button names are too long. So just a suggestion. Whatever you prefer...\nYah I see your point, but going to extension editor gives user more information and an opportunity to look at the alternative extension before installing. And also I do not like that this button changes with extension. More Information... would be consistent.\nThat's fair. We can start with your proposal and see how it goes. My only concern with \"More Information\" is that the user might think it is more information about the deprecation. While we actually want to guide the user to a solution. So it is something like \"More about the alternative\". I am not sure if there is a good button label to represent this.\n<img width=\"308\" alt=\"image (1)\" src=\"https://user-\"\nChanged the second button as follows ! !\nAwesome!!"}
{"_id":"doc-en-vscode-1f839a0658636b6cfa9fe3c6928a867cebf29c9e1a8f3bbf9baa5ed96cf06eba","title":"","text":"<!-- 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: 1.75.1 OS Version: Windows 11 Steps to Reproduce: a link in the terminal of the form the link would be automatically detected correctly and made clickable (although in the debug tab, by contrast, it was not detected properly). version 1.75.0, the link detection wrongly terminates at the so the link cannot be easily clicked to open it. I appreciate that you can never please all the people all the time with URL guessing, but I thought it was worth mentioning given that it used to work fine, and to be fair all the characters , and are standard normal URL code points and always have been.\nCan repro after, not before: !\nThis is actually a regression in monaco's link detection which the terminal leverages for uris: 74: <img width=\"259\" alt=\"image\" src=\"https://user-\"75: ! So this was unrelated to the recent terminal link improvements which focused on file detection\nintroduced this change to fix\nCommas are used pretty often in certain links, not sure how advanced the detection is but it could be improved by only treating it as a separator if after a / or if the word before has a period?\nGitHub also doesn't split at comma: , I'd probably revert the fix, but I'm fine with either. Up to you\nThis issue doesn't just affect the links in the terminal. It also applies to , and files (and maybe more)."}
{"_id":"doc-en-vscode-7ce62271574221abccc858eac3176b93cb2ba3e5ab286573b84fc4a1490c5ae3","title":"","text":"VS Code Version: 1.75.1 OS Version: Windows 10 Steps to reproduce: a file and paste the following code into it: an file and paste the following url into it: . both cases the link detection wrongly terminates at the so the link cannot be easily clicked to open it.\n:+1: I'm OK to revert."}
{"_id":"doc-en-vscode-94de4d64a3717014b90f1705aa5c3c6a7ffe86149a37ee58fab1026e8ab4032b","title":"","text":"<!-- 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. --<!-- 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.93.0-insider (user setup) Commit: Date: 2024-09-04T13:13:15.344Z Electron: 30.4.0 ElectronBuildId: Chromium: 124.0.6367.243 20.15.1 V8: 12.4.254.20-electron.0 OS: Windows_NT x64 10.0. OS Version: Windows 11 Insiders Steps to Reproduce: in the first paragraph doesn't appear to be a link, which I was surprised about: ! I hover over it, I see it's supposed to be a link, but clicking on it does nothing: ! The other docs links at the bottom of the playground appear correctly as links and do open when I click on them: !\nThis seems related to the bookmark issue we had in the release notes. The other bookmark links in the interactive playground don't work either.\nFixed the toc links. Need another fix for the documentation link too (which use command uris)\nThe Editor Playground is not showing at all anymore in the latest insiders. When selecting the Editor Playground menu item, a black editor comes up.\nhm working from oss builds. Insiders, it seems like the error is:\nActually unrelated. Seems like a duplicate of and fixed by"}
{"_id":"doc-en-vscode-5be576dab2f77650f29374110e76ed8a38947da8ab4dbb0f75e97c1e21c70742","title":"","text":"A similar error has appeared for other Azure Pipelines tasks\nOdd: one is about extracting first one shows no error at all (copy paste mistake?) second one is about creating a zip\nThis might actually be a bug on AZDO:\nAnd we might be hitting it due to logging every single file. Let's stop doing that.\nI reran the failure for the first one which is why it no longer shows an error here's the precise link to the failure\nThanks!"}
{"_id":"doc-en-vscode-4e54b4ef7b2508ae61299ebd0fd6ca2f0260fc1296885eb3c6be3631b8d7bce8","title":"","text":"<!-- 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 VS Code Version: 1.67.0-insiders OS Version: macOS 12.3.1 Steps to Reproduce: the terminal scrollback to 30'000 for With version 1.65.0 this was not a problem, but there was no highlighting. It would be enough if I can disable the highlighting or disable the highlighting automatically if the history is longer than x lines. https://user-\nThat doesn't look or feel slow to me - can you elaborate on what the issue you're dealing with is?\nIs it Upstream or VSCode Core.\nHappens for me too, when you search then type abs quickly and it takes ~5-10 seconds for the letters to appear, same goes with erasing letters.\nSearch is fast now but matches info is not being shown -"}
{"_id":"doc-en-vscode-cc9887bc971fd30597dae358d7269375eda66c3e952106bcf21bd1cdced458a4","title":"","text":"<!-- 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.79.2 OS Version: Darwin x64 22.5.0 Steps to Reproduce: a webserver at serving a single schema at containing (the precise contents don't really matter) a file , and paste in: the cursor between the quotes just after the trailing slash , and look at the webserver logs, observing no user agent was sent\nThanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.80.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!\nI suggest to verify this in code:"}
{"_id":"doc-en-vscode-d492bf2b1f9b3e2eb9d93bbd24d50ffd453e825c1424dfdfa420c18606ee5486","title":"","text":"<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --vscode- a directory to clone your repo into cloned repo :bug: branch context is not preserved This impacts Continue Working On--branch context is preserved for Clone in Container and Create New Codespace. I propose adding a new optional query parameter to the uri handler here: and passing that to the command as an optional argument here Then after cloning here: and before opening the repo in a new window, we would perform the ref checkout:\nwill you create a test plan item/verification steps for this feature?\nyes I will!"}
{"_id":"doc-en-vscode-305f5095a83611d9bfd9e0fa7e524097007398c8156ffbc3650c93564138c8c5","title":"","text":"Testing Not sure if this lack of functionality blocks anything truly useful, but at least in the treeview, you can multi-select problems and copy them to the clipboard. In the table view you can't.\nThis also has the side effect of losing a multi-select that you may have had in the treeview.\nwhat was the thinking for enabling multi-select in the problems treeview? Was there a particular scenario or this is what the default behaviour is for a treeview? If there is a real scenario, than we should enable multi-select in the table as well.\nYou can copy multiple problems is the primary use case.\nthat makes sense. Thanks!"}
{"_id":"doc-en-vscode-914b0dbe8d0680b438a1958ce2c6c50d08a64c650ac849dc17149eca67be74b0","title":"","text":"accessible view go to symbol picker are closed sometimes (when there's more than one item) cc"}
{"_id":"doc-en-vscode-64463bcbce30f355aa542b88de5aaa27f049b140d0915f54f0655bd0012dbd94","title":"","text":"Testing Version: 1.90.0-insider Commit: Date: 2024-05-29T05:51:07.154Z Electron: 29.4.0 ElectronBuildId: Chromium: 122.0.6261.156 20.9.0 V8: 12.2.281.27-electron.0 OS: Linux x64 5.15.0-107-generic open a file in an editor run . This opens a file selection dialog initialized to the home folder\nSame problem with open folder dialog\nVS Code is awesome, but the open file dialog on Linux has been ridiculously buggy for years. More than two years to fix the problem of the dialog opening in the background. The fix, in the latest version, involves using a dialog inside a portal with no type-ahead support that opens in $HOME or recent files. The open/save file dialog is a crucial control in any application. There should be a way to use the native OS dialog. I'm going to downgrade to the previous version (1.89.1) and keep it as long as it takes.\ncc\nWe hadn't patched the portal code to support most of the file dialogs options, it is being addressed via\nThis is now addressed in the runtime via , fix will be available once we adopt\nReopening since we have reverted the updated due to other regressions , will be revisited in August.\nThis issue is not resolved for me, here is for comparison how the file dialog opens in an older version of VS Code vs. now: Good behaviour: ! Bad behaviour: !\nFiled\nI'm on xfce on xubuntu 22.04. Version 1.89.1-1715060508_amd64 does not have the issue. Later versions do have it. The problem is that instead of forcing the \"Open File\" path, to that of the current file being edited, vscode delegates the path selection to the operating system, which resolves the \"Recent Files\" path. Since recent files is truly not useful in vscode, I can at least pilot the path to be that of the home folder with $gsettings set startup-mode 'cwd' from the previous value. Clearly this is very inconvenient. Is there any update about it?\nThe issue is not resolved for me either."}
{"_id":"doc-en-vscode-32d65a22e45ba376d61baeeedf9547c33927d237da6e1a48581f24b47cf0d5b0","title":"","text":"The file-open and directory-open dialogs still do not appear even though built on Electron 30.1.2. This is reproducible 100% of the time in openSUSE Tumbleweed and in Leap.\nThe file-open/directory-open or save dialog not being shown remains unresolved on Linux in release 1.93.1 built with electron 30.4.0."}
{"_id":"doc-en-vscode-3b87a4f2d976654cb06aa0292a97c9c1d805225c305f036e660348ce1acc64e6","title":"","text":"a notebook and run a cell that will continuously update over time to drag the scrollbar while output is still being written :bug: scrollbar is not held and returns to the bottom\nStreaming output items are all compressed into a single item in (?), so we would need to stop doing that unless needed (for editing previous lines) Also, the current method only allows passing a single output item, but the output renderer will need to be able to render the entire output as it currently does, or just append the new data. Current: Proposed method that would only be used for streaming outputs and if the chosen renderer contains the method: Another alternative would be adding info to the OutputItem itself, containing only the appended string if appending should happen."}
{"_id":"doc-en-vscode-3278f0d795548f65c1767f02b19a4d4e7d0f179746a23892328e32b5b64346cd","title":"","text":"Apologies, this is a bit hard to replicate, so I'll do my best. Open a python jupyter notebook and do some work. Cut some code in the middle of a line in a cell. Go to a different cell and paste. The pasted code will be duplicated. I was able to replicate after restarting VS Code multiple times. Downgrading to 1.46 fixed the issue for me.\n/duplicate of"}
{"_id":"doc-en-vscode-4ee33aa314169dd72b2cfccf1ec83669d12010aea66ec4e0a01bcb80d7beb872","title":"","text":"Issue Type: <bBug</bThis seems to be a regression on VS Code Insiders. It does not repro on stable. If I call , it will only execute that specific task, not the task it dependsOn as well. Here's an example Example code to execute the task: VS Code version: Code - Insiders 1.47.0-insider (, 2020-07-07T07:46:45.605Z) OS version: Darwin x64 19.5.0 <details<summarySystem Info</summary </details<details<summaryExtensions (17)</summaryExtensionVersion ------ vscode-pull-request-github0.17.0 vscode-azureappservice0.17.1-alpha vscode-azureresourcegroups0.2.0 vscode-azurestorage0.9.0 vscode-cosmosdb0.13.0 csharp1.22.1 python2020.6. remote-containers0.127.0 remote-ssh0.51.0 remote-ssh-edit0.51.0 azure-account0.8.11 powershell2020.6.0 vscode-typescript-tslint-plugin1.2.3 java0.64.0 vscode-didact0.1.15 sort-lines1.9.0 vscode-java-debug0.26.0 </details<!-- generated by issue reporter --\nCaused by Because the task execution is first gotten, then passed to the extension host, the depends on is lost when passing to the extension host.\nWorks for me on the latest insiders, thanks!\nThank you for verifying!"}
{"_id":"doc-en-vscode-bdb93f7640ed0a5dc8cd00f330635e1cc8386ac8c62ba4b87365472687eecd18","title":"","text":"I recently noticed an animation to indicate toolbar actions can be changed: ! This seems to be inspired by Safari toolbar when you edit it: ! I am seeing a few issues with our approach: we allow to change visibility of actions in a lot of places (activity bar, status bar) where currently there is no such animation in Safari to get into this mode, the user explicitly picks an action \"Customize Toolbar\" while for us it starts on right click already in Safari you can actually grab an action and move it, I even think they only animate the action to make that more obvious (not so much the fact that you can hide the action) I would vote for not having the animation until we can support what Safari does including to drag and reorder actions. I think the menu makes it already clear what the right click gesture allows you to do: <img width=\"299\" alt=\"image\" src=\"https://user-\"\nYes, thanks, this feels very strange to me. I don't think animating the whole menubar make sense when you are only operating on a single item.\nHow about beginning a right-click menu with an inactive entry that acts as a header? Something like \"Button Visibility\". It would also act as a protection against accidental hiding, since I can imagine some folk inadvertently pressing right button down, moving the mouse a few pixels right, releasing the button and seeing vanish the button they intended to actuate. Especially on Linux where there's a longstanding issue about this happening on context menus at certain Zoom levels and certain places on the screen.\nrelated/motivation\nWell, strictly speaking you operate on the whole menu because you also have toggle actions for all its entries. I like that direction. We already do something similar to right click the overflow item. You cannot hide that but you get a disabled \"Hide\" entry for consistency. On the flip side it is bogus use of menu items as \"headers\" <img width=\"340\" alt=\"Screenshot 2022-09-29 at 08 23 30\" src=\"https://user-\"Overall the motivation for same kind of animation is mostly the . Left and right click show a context menu which do very different things but look very similar\nAny scope for changing the button icon when in this edit mode? Maybe to pencil or gearwheel.\nNote that animations like this look pretty terrible on standard DPI monitors due to the blurriness."}
{"_id":"doc-en-vscode-676209a3eaddf0bdfb7d66f9bad43527048b6e15d68d4b0ee01bcddd876e15cc","title":"","text":"It also removes sub-pixel anti-aliasing which makes it look even more different to non-animating. ! Regular: ! Animating: !\nis that specific to this animation or something you notice with animations in general? Like the sync-spinner or the language status wiggle?\nI also think the spinner looks pretty bad, though it's less noticeable than this I don't think I've noticed this, but any animation like these should have this problem. You can notice it when websites use animations as well, the shift from animated to non-animated is often jarring.\nOr even spinning gearwheel\nCan you please file a dedicated issue? There is a bunch of places that use CSS animations and if there is a flaw with that we should look at it holistically Created to disable the animation for now. Let's take time in October to revisit this. Lets discuss (1) if this is really needed and (2) if we should align other hide-able items (consistency is key)\ncreated with a lot of details"}
{"_id":"doc-en-vscode-b35ceacb553472d21854b18296ff072aa7dc512449d0f7006f1b0e32d803d110","title":"","text":"VSCode Version: 1.0.0 OS Version: OSX 10.11.3 I noticed that we can set to a keybinding. Which creates a nice input field in the sidebar to create the directory at the current selected position. ! But there is no possibility to do this for a file. Yes you can bind but it does not do the same thing. It just creates a new and when pressing <kbdcmd</kbd+ <kbds</kbdyou have to choose the destination in a picker. So, is it possible to add something for a new file as well? It would really improve my speed because I don't have to touch my mouse anymore to create a new named file in a specific directory.\nsounds like a good example for a PR?\nYes I looked into it but to be honest, I have to clue where to start :). So if you can point me in the right direction, I would be very happy to do one :).\nI would start by fulltext search for the action id () and that brings you here: From there you can get a feeling how this global action works and maybe add the new one. You will also see the one on top for creating an untitled file (which is not what you want). When you find the references of that action you will see where it is being registered to the system:\nAlright, awesome. Thank you very much Will see what I can do :)."}
{"_id":"doc-en-vscode-5b6942ca8bfad0f953871d93fc000003bba666a378d0c2d62f49dcd829e021ea","title":"","text":"VSCode Version: Code 1.18.0 (, 2017-11-08T21:19:36.079Z) OS Version: Windows_NT ia32 6.1.7601 Lists shift the indentation by the level of depth in the list hierarchy. This is just a very minor thing, but the is no longer syntax highlighted when a quote is part of a list item and thus indented. ! Steps to Reproduce: markdown file. a list. a quote to one of the items by indenting the quote. Reproduces without extensions: Yes"}
{"_id":"doc-en-vscode-6e2faa36b3d12e5301180e8a9c6a7b97d5df50453fc2f3f2559882edd96b9bc0","title":"","text":"Type: <bBug</bIn the new shell integration options for Bash and Zsh, VS Code wraps the PS1 prompt variable to support new functionality. However, when it does this, it prefixes the PREFIX environment variable to the existing PS1 when creating the new PS1 prompt. See the picture below for an example. ! For Bash, the problem is at: For Zsh, see: Steps to reproduce: either Bash or Zsh, enable the integrated terminal a value to a variable named PREFIX in the integrated terminal that the value you assigned to PREFIX is prepended to the prompt The PREFIX environment variable is commonly used across a variety of projects in the Linux world for configuring and building applications (grepping for 'PREFIX during the build process and it makes the terminal hard to use. This issue is the cause of . I can submit a pull request for this if you'd like. VS Code version: Code 1.71.0 (, 2022-09-01T07:36:10.600Z) OS version: Windows_NT x64 10.0. Modes: Sandboxed: No Remote OS version: Linux x64 5.10.102.1-microsoft-standard-WSL2 <!-- generated by issue reporter --\nthanks for the investigation and yes would appreciate a PR for this\nI can't remember why PREFIX is there, we should blame history before doing the fix\nLooks like PREFIX was only used in the initial commit to accomplish what is currently done with _vscpromptstart(), and it was safe to do so as PREFIX was declared as a local variable. Here are the original commits of the relevant files: Zsh: Bash: The second commit to modify these files () modified the updateprompt() function and removed the local PREFIX variable, but did not remove the variable from the PS1 assignment.\nFor Zsh specifically, in , extra references to PREFIX were to fix a separate issue.\nNice, looks like it's safe to switch to in bash. I'm guessing it's safe in zsh too, do you agree?\n<!-- 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!\n/verified"}
{"_id":"doc-en-vscode-6d17b5dbad126744b4e5f046cbe0da06c2fa6b702a33da611219b0f978d21d67","title":"","text":"Issue Type: <bBug</bSteps to Reproduce: a notebook. In my case, I have a Jupyter notebook (.ipynb). any of the \"\" or \"\" or \"\" or \"\". happens! These navigation commands work just fine in all other views/panels that I regularly use. VS Code version: Code 1.66.2 (Universal) (, 2022-04-11T07:49:20.994Z) OS version: Darwin arm64 21.4.0 Restricted Mode: No <details<summarySystem Info</summary </detailsExtensions disabled <!-- generated by issue reporter --\nthis sounds like a real bug to me, the issue is that notebooks do not seem to be rooted below the editor part in the DOM: ! That asks for trouble because we have lots of checks in code to figure out if the editor area has DOM focus or not, e.g.: What is the rationale? I checked with custom editors, and they manage to put the into the DOM hierarchy of the editor part. //cc\nWe render the notebook out of the grid view as it contains a webview, which can not be re-parented when users drag editors between groups. I basically followed what Custom Editor does did we change this recently? I wonder if it's already safe to do so.\nCan confirm that I am also experiencing this. In the meantime, I've found that this kind of works for moving left and right: But there is no or , and this fails when attempting to move to panels. Looking forward to a fix, or if anyone has a workaround.\nfyi we no longer use but only , so maybe that changed.\n<img width=\"1918\" alt=\"image\" src=\"https://user-\"I found that we are not putting custom editor webviews in the editor grid either.\noh ok, turns out we seem to have logic to still make that work via a special code, looks like notebooks should adopt it as well: And the relevant method using it:\nYes to my knowledge iframes still cannot be reparented. All webviews are rendered as top level elements with absolute positioning to work around this Let me know if you have any questions about using . It should help fix this issue as I believe I've already fixed a similar issue for webviews\nThis feels like a useful workaround."}
{"_id":"doc-en-vscode-b2f3466e7beb3e81d8b14ceb373ae613634c40b285d46aaff3c5b7bcd6fa3450","title":"","text":"Concerning moving up and down, you can use the and actions ().\nworks great, it would be great if you can help review\nThis seems to be working for me now in insiders but feel free to speak up if it's not doing what you expect\nYep, this seems to be fixed in the insiders build. Looking forward to seeing it merged into stable! Thanks everyone!"}
{"_id":"doc-en-vscode-551999e323f73f6be439f51c907ede80a54be126df81aade9bbb7425056e29e2","title":"","text":"Type: <bBug</ba file for which a DocumentSymbolProvider will return some items, for example on the filename in the breadcrumb, then type Ctrl/Cmd+F. The list filter widget looks OK, though it hides the first filename in the list ( ought to help with this once merged). the same but one item to the right in the breadcrumb. The filter widget is transparent. ! VS Code version: Code - Insiders 1.71.0-insider (, 2022-08-22T05:16:19.478Z) OS version: Windows_NT x64 10.0. Modes: Sandboxed: Yes <!-- generated by issue reporter --\n/assign\nEasier steps: <kbdCtrl F</kbdon an outline breadcrumb\nI still see this. It looks like the background of the find widget gets removed, but the contents still scroll up out of the breadcrumbs widget\nDid you test this in dev? Because we still didn't get an Insiders build with the fix."}
{"_id":"doc-en-vscode-e0fb6b82863bd618426b11582bafc4acbcc0cf919e589e5edd78469e08efcc7c","title":"","text":"Originally posted by in\nThis also happens if step 5 is omitted and Search mode is used. The problem seems to be that to put the 'No elements found.' warning message under the find-in-list's input widget a ContextView is created immediately below it. But when find is occurring in a breadcrumb list, that list is itself in a ContextView which gets hidden and cleared immediately before the one for the warning message is shown. The warning message appears in the top left of the VS Code window in a very narrow column. See below, where I open , click on the filename in the breadcrumb to get a list of sibling filenames, then type \"z\" which isn't present in any of the filenames. !"}
{"_id":"doc-en-vscode-d99eb20d51d2616cc73bde2dc227cc556c2049c78059fdc715755f77807121c0","title":"","text":"<!-- 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.88.0-insider in Safari OS Version: macOS Steps to Reproduce: Safari open a file with: to the right of any the cursor goes to the beginning of the line not the end This does not repro in stable\nI didn't do any changes the last couple of milestones that could (easily) explain this. Can you reproduce this in the monaco editor? If so, can you do a bisect?\nI bisected it to this commit: (the commit before it) does not repro the issue. This wasn't in Monaco editor, I just used run code web:\nThis commit is just a rename refactoring. It is very unlikely it causes this... This does not reproduce in chrome, right?\nThe bug does not reproduce in Edge on macOS, but it repros in Safari.\nUnfortunately, I don't have access to Safari. Can you double check that this is caused by that commit? Can you locally rename the class back to the original name and see if it still happens? It does not make any sense that this commit would cause this behavior only on Safari.\nOk and I paired a bit on this and are really stumped. Bad news: That commit I called out seems to be a red herring. Good news: we can repro in the Monaco Editor Playground."}
{"_id":"doc-en-vscode-952064d2589a444a831246e9434b0e109e26dc28081730702c1d54ca0f74413a","title":"","text":"Here's a side by side of two versions of the dev build: <img width=\"1680\" alt=\"image\" src=\"\"You can see when I click to the right of a line, the older (working) build has the correct position here, while the newer broken build has column 1. Here are the links to these versions: Working: Broken: I believe this is out of both of our depths at this point so I'm passing to you This is a regression so I think it should be fixed before we release (assuming I'm not the only one to repro)\nDid a bisect using and it points to\nIn that case, it is most likely ."}
{"_id":"doc-en-vscode-690b5f793cb158ebd4860c099dc54fe404e7ef922cc6e3f92c53439f469e5382","title":"","text":"The fix for at only replaces the first instance of in the string, not all of them. I suspect the regex needs on the end. <img width=\"1028\" alt=\"Screenshot 2022-03-17 at 14 46 58\" src=\"https://user-\" FYI :)\nheh, I found that and was going to change it, but GitHub fell over. I can easily add the , but it's not clear to me where/how to write a test against this class (which is actually the part that I get stuck on any time I want to contribute something). I can't find any similar tests in this area to use as a template.\n/verified"}
{"_id":"doc-en-vscode-68b72a80e588737a170afa1c830dd2fb3d2dfe2955849b89478ff09aac0a12c8","title":"","text":"Issue Type: <bFeature Request</bI want the message could display under the variables it refers to. Because the message box blocks the code over the current line. Thank you. VS Code version: Code 1.36.1 (, 2019-07-08T22:59:35.033Z) OS version: Windows_NT x64 10.0. <!-- generated by issue reporter --\nCan we just change the default to or does this require a setting?\nKind of feel like this is out of scope, but I don't think this should be assigned to me since it's regarding monaco.\nActually I was wrong - it is determined by : I verified if I swap the order then the hovers appear below instead of above (where there's space). I'll make a PR.\nDone! Before: <img width=\"734\" alt=\"Screenshot 2021-06-30 at 08 45 06\" src=\"https://user-\"Change the setting: <img width=\"921\" alt=\"Screenshot 2021-06-30 at 08 45 14\" src=\"https://user-\"After: <img width=\"777\" alt=\"Screenshot 2021-06-30 at 08 45 22\" src=\"https://user-\"\nLet's continue tracking in"}
{"_id":"doc-en-vscode-bd946e2b870e654783a16f7a06ab8b9296d714c4c8141bef16787c0b882257fc","title":"","text":"<!-- 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: 1.67.0 OS Version: Windows 10, using as a default shell Steps to Reproduce: When debugging python(I think debuggers of other languages also got effected too), I'm using following to redirect stdin to my custom input file. This method of implementing redirection when debugging using the < character is also introduced in the . According to the document, This approach requires that the \"<\" syntax is passed through the debugger extension and ends up unmodified in the Integrated Terminal. and it worked like charm before updating to . From , I've noticed that there was a fix related to automatically add escape character() before special symbols such as or (See Terminal on Windows uses cmd /C, this corrupts passed arguments) When I started debugging session, vscode is now really add before . Since character is escaped, I cannot used redirection with the method mentioned in the document anymore. Is this the intended result? If so, how to use redirection 'correctly' after this build? I know a lot of people redirect stdin to and redirect stdout to when debugging, which is actually very convenient. I think that implementing redirection by passing special characters(, , ) as arguments of the debugger is not a very graceful solution, but that method itself should not be eliminated.\nHaving the same issue with new version in WSL. It seem some characters are prefix with . My is . But in console, the command is , due to prefix , my code is stuck. It was working fine yesterday, So, I think this issue is with new release."}
{"_id":"doc-en-vscode-34e16ddbd8a8a0675379e56f89741f033599c86ac696b1c00bcd04dbc3db2f60","title":"","text":"VS Code Version: 1.67.0 OS Version: Windows 10, WSL Ubuntu20.04\nJudjung from of , I'm sure this issue is related to today's release too.\nYeah this is Thanks for pointing out the docs, I didn't know this was recommended. It's suspicious to me that we would want to put shell-specific syntax in the args here. That isn't what \"args\" means to me. I wonder whether we could add launch config parameters like \"stdinFromFile\" and \"stdoutToFile\" (and add those to the runInTerminal request) so that vscode can come up with the right syntax for the shell. I may want to revert the change until we have a better solution. Thoughts Maybe candidate\nI'm not a fan of allowing this. We already try to escape things from those arguments, so people doing this today have only a half-working shell syntax in their arguments. It also only works if you run it in the , and is of course shell-dependent too, which feels weird.\nThis is super messed up. I 100% require being able to redirect the output. This needs to be fixed. ages: [\"\",\"\"] was 100% working on windows before this update! My work flow is screwed rn\nArgs mean arguments as if I was writing it after typing it in console including SHELL commands. I want to redirect output Why in the world it would add ^is crazy to me. This has to be be bug.\nAdditional sometimes you need to chain aliases that take redirect or pass a redirect back in < These are shell scripts that having the debugger \"args\" accept <,,| is really important to have. It was an amazing and highly convenient way to debug. I seriously doubt this is a feature that few people would want deprecated. I seriously don't and it's killing me it broke after this update.\nYeah I agree that passing redirection symbols through args is somewhat weird, and I understand the need for escaping shell-specific characters. That's why I've said it's not a graceful solution. However, many people uses the redirection feature through that way now(even if the docs have been mislead the users). It's good improvement to escape that characters in arguments since it is literally \"argument\", but I think there should be official solution to redirect I/O."}
{"_id":"doc-en-vscode-3391f52be2b59b849b4a57dd7745800a7abc10b196232a8b282017342e8df941","title":"","text":"As mentioned above, add parameters such as \"stdinFromFile\" and \"stdoutToFile\" to might be best solution. BTW, what kind of additional information do I have to add here? I think I mentioned all the details of the sitution but I see the \"needs more info\" label.\nI've spent 3 hours trying to come up with a work around. This is insane. So much of my workflow relied on the ability the redirect stdin and stdout using <,. It's insane that this was deprecated. I don't even get why. It doesn't have to do any crazy checking should just copying what you type in and the shell takes over. This is a serious issue for me. !\nIf it's about \"escaping shell-specific characters\" then I could live with this. And if it's about anything else shell then give me something like this:\nSorry for the trouble. Like I said, I didn't realize that people were depending on this behavior, and I agree that it should be supported somehow, since this is a reasonable and useful workflow. To me, \"args\" means arguments that get passed to the program you are starting. I see a couple solutions Restore the behavior of and require users to shell-escape args in their own config, which is not good, or add which would be shell-escaped Keep the behavior of and add or , or the more specific Any of this will require changes to DAP. I wonder whether anyone is trying to use any shell syntax besides /<, in other words, is there a scenario that adding wouldn't cover?\nIn my opinion, the second way Keep the behavior of and add or , or the more specific is better workaround since we can prevent use of different way from its real meaning.\njust a few comments from vacation... VS Code knows nothing about properties. Some debug extensions introduce in their schema contribution but VS Code cannot provide any direct help with redirecting input/output. VS Code supports/implements the DAP request which some debug extensions use to implement their (private) support. does not allow direct access to shell features (e.g. input/output redirection) because no assumptions can be made about the underlying shell or whether a shell is used at all. So escaping/quoting all shell meta-characters is correct. But we might want to add additional features to the DAP request so that debug adapters can implement / property support themselves."}
{"_id":"doc-en-vscode-db6333f8f17c45a8aa4da75da411b8b7ff47afe79422519baad196013b5cb0fa","title":"","text":"a debug extension can introduce an alternative property that supports shell features, e.g. a property . In order to support this we would have to add support to the DAP request to pass a full command line unchanged to the underlying shell.\nis there a scenario that adding stdinFromFile/ stdoutToFile wouldn't cover? Yes. I for one will use aliases that are shell scrips to redirect their input and output to chain together programs.\nYes, this is basically my thinking. But I think I should revert the change as a candidate until we figure out a better solution. could you give me an example so I understand how that wouldn't be covered by this proposal?\n\"stdinFromFile/stdoutToFile\" makes the most sense to me. I would not be in favor of a option in the request since, similar to the initial problem, the DA has no knowledge of the underlying shell.\nI wonder whether we could make everyone happy in the meantime by leaving the current fix but special-casing and and not escaping these? You could have the and filename in a single arg but I don't see anyone doing that. And it would make the behavior almost the same as the intended escaping behavior.\nIf would work with \"\" instead of \"\", \"\" I could live with that. Or what ever you mean by special-casing. I just want it to work again or have some means to do to it again.\nI mean the opposite (the in would not be escaped, and in would be escaped)\nthat seems like an acceptable interim fix to me. As a C++ debug extension author (vGDB), this has also broken my extension on the most recent VSCode build and I've had to suggest users defer on upgrading for now to not break existing workflows.\nThanks. I am going with this solution for the .2 build that will go out next week. Not a perfect fix - as a single argument would have previously redirected output too - but people are using or in all the examples I have seen so far. It will also be in Insiders tomorrow. I noticed another issue with the escaping, , which will also get fixed in Insiders\nthanks for the quick fix!"}
{"_id":"doc-en-vscode-8e4a34eecebce92add579dd4e3e7b606aa42faa98b16aef77950ce9262110844","title":"","text":"We should not translate the PHP parser error messages, but we should localize the strings that appear in the Code UI. !"}
{"_id":"doc-en-vscode-69217b77a085bdc403333d85aa73b68e9ac7b6ea87e7af985ac48b4f520654fe","title":"","text":"Type: <bBug</bI got the following error randomly while changing workspace settings. I used the extension bisect feature to see if it was an extension, but nothing was identified on the very first pass. The issue continued to persist, until Visual Studio Code was reloaded. Here's the message that appeared in the problem pane: Problems loading reference 'vscode://schemas/settings/workspace': Unable to load schema from 'vscode://schemas/settings/workspace': cannot open vscode://schemas/settings/workspace. Detail: Unable to resolve text model content for resource vscode://schemas/settings/workspace. I found a similar issue regarding multi-root workspaces on github: My workspace has multiple folders. I only edited the workspace settings and I never touched the folder settings for the workspace. I did made some recent adjustments by installing/uninstalling extensions, switching profiles, and editing workspace settings. VS Code version: Code - Insiders 1.77.0-insider (, 2023-03-14T05:23:49.668Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<details<summaryExtensions (11)</summaryExtensionVersion ------ Ionide-fsharp7.5.1 csharp1.25.4 dotnet-interactive-vscode1.0. vscode-dotnet-pack1.0.12 python2023.4.1 vscode-pylance2023.3.20 jupyter2023.3. jupyter-keymap1.1.0 jupyter-renderers1.0.15 vscode-jupyter-cell-tags0.1.6 vscode-jupyter-slideshow0.1.5 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nThis is probably caused by of the schema (and others) It would be better to register the schema immediately but empty, and to set it later again with content.\nCan this be at least workarounded somehow? It's very irritating - I cant edit any workspace settings\nI'm sure a hotfix will release the fix to all of us soon, but here's a workaround for now: I found that poking any settings key in restores proper autocomplete/hover in VSCode's until next VSCode restart. But a key must be poked after every restart."}
{"_id":"doc-en-vscode-b5dd9450d851b5fdaabc960ba8767b37bce97897d5828b50479a8ae40b83d431","title":"","text":"For example, put at the top of your and save the file. You will have to toggle and save this key every time you start VSCode. A detailed set of steps for doing this can be inspected at the end of this comment. If you use the VSCode extension , you can set up a hotfix keybind (like in this case), and press the keybind twice every time you restart VSCode. Or, just never restart VSCode until the patch drops! <details<summarydetails</summary<pI can confirm that setting allows hover hints and completion to function again, e.g. in VSCode's own modification. However, this workaround throws out all JSON linting and reporting in the \"Problems\" pane, so it's sort of the nuclear option. This issue just cropped up for me in the past few days, so it may be a regression associated with the latest release? After further investigation, I find that poking any settings key in restores proper autocomplete/hover in VSCode's until next VSCode restart. But a key must be poked after every restart. Here's a rundown: all tree of settings keys are initially at their defaults, e.g. none of these keys are explicitly specified in any of your (maybe unnecessary, but this is my starting state). VSCode (e.g. with ). Navigate to your user . The following warning presents in the Problems pane: a trivial setting modification in the tree of settings keys, even if that modification is a no-op, like explicitly specifying a default as its default value. For example, put at the top of your and save the file. (You could've also poked to be either or I think, maybe?) whether autocomplete/hover works properly in , completing settings names and such. It should work now. can even remove the edit you made in step (4), save again, and autocomplete/hover still works. VSCode. autocomplete/hover is broken again in , until some modification to the tree of settings keys is made again, like in step 4. For example, commenting out if it's there, and saving, restores autocomplete/hover."}
{"_id":"doc-en-vscode-e16ddd94146ef9905dc9f6cd4d32e317309cc1af1821a1e7659550271c3fe8e7","title":"","text":"So this issue may have to do with unstable startup behavior of JSON schema handling, perhaps isolated to VSCode's own or perhaps all JSON schemas more broadly, and this unstable state can be temporarily fixed by poking a settings key, but the unstable behavior returns on the next program start. At least in my case. </p</details\nI have encountered a similar error: So nothing I do in my file has any effect. Not only that, but when I type \"\" into the Settings search bar, the only thing that comes up is a reference to a file under .\nIn my case I think I found the culprit: The property above gives a \"Value is not accepted\" error even though it's a valid value that works when the is enabled (it's currently disabled). As soon as I delete this property, the \"Unable to load schema\" error goes away. Weird. Update: I spoke too soon -- after reloading VS Code, the \"Unable to load schema\" error is back\nA few days/restarts later, and the error is gone. Looks like a Heisenbug.\nFor me the problem message appears in a typescript node project when I have open. Close this file and the problem message goes away. (The file contains no known issues). While others report either user or workspace settings reference loading problems, for me it is configurationDefaults:\nis there any update on it? it's very frustrating and I don't see a reliable workaround\n<!-- 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!\nI still see this <img width=\"1619\" alt=\"image\" src=\"\"Repro: a syntax error in , which will result in some setting's value being \"changed\" that forces restart of vscode dialog to restart vscode shows up, click on \"Restart\" restarted vscode will likely have this error\nI cannot reproduce this, are you seeing this consistently?"}
{"_id":"doc-en-vscode-ea65ac47bdebaee298f06c4dfa0c6d946a4ca914e70574fa49e2e3e6ceb9dee5","title":"","text":"I can't repro deterministically, but I feel like it has to do with loading/reloading the window\nCan others subscribed to this issue, please try our latest insiders and let us know if you still see the issue?\n/verified\nI confirm this is fixed in (tested under Ubuntu 22), and without the need for .\nI just upgraded to the regular version and it also seems to be fixed there as expected ^^.\nCan U confirm it is now fixed in version 1.80.0 and close the issue ?\nThe message is still there for me in 1.80.0.\nThanks for confirmation. I will close this as fixed and verified. Please reopen a new issue if you are still seeing it (may be new) with steps to repro.\nFor me the message showed up in 1.80.0\nFor me too\nCurrently experiencing this issue. I can overcome it temporarily following a suggestion elsewhere where I add or remove \"\": true to my file. I keep adjusting the file to see if there is something in there ausing the issue. Even old, known settings are causing the error to kick in regularly. I put a single setting in there and the error comes up unless it's empty Version: 1.80.0 (user setup) Commit: Date: 2023-07-04T15:06:02.407Z (1 wk ago) Electron: 22.3.14 ElectronBuildId: Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.\nCurrently experiencing the issue on my linux machine. On my Windows machine (with the same configuration file, since it's synchronized) it works fine on stable, but not on insiders. Can confirm that toggling as a workaround works until restart."}
{"_id":"doc-en-vscode-0cbb56d04b2c369f36b7bed1f85a8f0c3835a5b058e2097440ad9a0dc4cb6d51","title":"","text":"Linux version: Version: 1.80.0 Commit: Date: 2023-07-04T13:39:48.236Z (1 wk ago) Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.80.0 Chrome/108.0.5359.215 Electron/22.3.14 Safari/537.36 Windows version (stable): Version: 1.80.0 Commit: Date: 2023-07-04T15:06:02.407Z (1 wk ago) Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.80.0 Chrome/108.0.5359.215 Electron/22.3.14 Safari/537.36 Windows version (insiders): Version: 1.81.0-insider Commit: Date: 2023-07-13T05:33:32.822Z (2 hrs ago) Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code-Insiders/1.81.0-insider Chrome/108.0.5359.215 Electron/22.3.14 Safari/537.36\nReopening this because it can be still reproduced.\nI am getting this error and I can't figure out how to fix it.\nPlease try our and see if you are still seeing it\nCurrently seeing this while in a file on GitHub Codespaces, in the following form:\nCan you please try insiders and see if you are still seeing this?\nI still saw this issue when opening on: Version: 1.80.1 (user setup) Commit: Date: 2023-07-12T17:22:07.651Z Electron: 22.3.14 ElectronBuildId: Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.\nAs I mentioned, this was in GitHub Codespaces. I can't change the version of VS Code they serve to the browser."}
{"_id":"doc-en-vscode-4678cdfc95032f886d6296aa966707f9d395b94c72c95cd3f709e5d4358b8a09","title":"","text":"There should be an action Switch to Insiders... in the settings gear icon in the bottom left corner, do you have that?\nuninstalled installed all extensions, including- C# v2.0.328, autopep8 -for python, ctrl+shift+p - selected -format this document with - seleceted C#- All things worked again."}
{"_id":"doc-en-vscode-0a1d03df981986debdbc681c23289ef8fb72b396102c2520bd690b5ac0a35867","title":"","text":"Type: <bBug</bVSCode, create a folder named, for instance, \"XXXX\". that folder create another called .vscode .vscode create a file named with this content: VSCode sure the setting \"task.allowAutomaticTasks\" is not set or is set to its defautl value \"auto\". \"XXXX\" with VSCode. VSCode will run \"echo Hello\" without asking you whether you want to run tasks configured with \"runOn\": \"folderOpen\" or not. VS Code version: Code 1.70.2 (, 2022-08-16T05:35:13.448Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nThis happens because you have presumably opened a trusted workspace - which is now when we allow these to be run if the setting is \"auto\" for allow automatic task\nThe 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 . Happy Coding!\n! If I understood it correctly, the popup that supposedly asks you whether you want to run these tasks is not actually meant to appear ever because if the workspace is trusted it will be executed without asking you and if it is not trusted then it will just not exeute them instead of asking you. Doesn't it look kinda pointless to have in the description of the option of the configuration \"Prompt for permission for each folder\"? You are never prompted anyways.\nI this configuration and I am still not prompted anyways:\nNo I did not. Please next time ask the user if he did X before assuming it and closing the issue. I tried reproducing the problem with and without a trusted workspace and the problem persists anyways.\ni'll investigate this that shouldn't happen\nTasks will only run in trusted workspaces, so I will update the setting description to indicate that. Also need to fix the prompt not happening per folder."}
{"_id":"doc-en-vscode-a4363304286d62a6b4378ee16f64573e02eea8bd1d4971d0f49b29ef467cb179","title":"","text":"Type: <bBug</bSince the upgrade to 1.91.1, the tooltips/popups (that show function documentation on mouseover, for example) have become a hinder, because they seem to get sticky, being in the way when I want to select/click something on the lines that the tooltip/popup is overlaying. I'm not 100% sure how to explain this, or what exactly changed, but I know this wasn't a problem in the version before. Something definitely changed in version 1.91.1. I'm not sure if it's because they're appearing faster, or taking longer to disappear, or... Thank you! VS Code version: Code 1.91.1 (, 2024-07-09T22:06:49.809Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (13)</summaryExtensionVersion ------ better-comments3.0.2 vscode-intelephense-client1.10.4 path-intellisense2.9.0 vscode-eslint3.0.10 gitlens15.2.0 prettier-vscode10.4.0 duplicate1.0.2 vscode-github-actions0.26.3 php-cs-fixer0.3.13 vscode-phpunit3.2.2 vscodeintellicode1.3.1 php-sniffer1.3.0 php-debug1.34.0 </details<!-- generated by issue reporter --\nHi the editor hover has not been fundamentally changed last iteration. Last iteration I have refactored the editor hover code so this could be the source of the new issue you are seeing. For me to understand better the situation, next time you see the issue you described, could you post a screen recording here and an example of the code where you are seeing the issue?\nThank you. I cannot show much of the code, but here's a short video which I hope helps. (I tried to \"exaggerate/force\" a bit, but it should show what I mean) These editor hovers have been annoying me all day, since the update. They just keep being in the way. In previous versions, wasn't the hover disappearing when the mouse leaves the tooltip? Or when the user is selecting text? Thanks."}
{"_id":"doc-en-vscode-29b5589886d8a8705229c9caf370aec932f5416664f6e01c792d0669a032c41e","title":"","text":"[video removed, for privacy]\nWhat version were you previously on?\nHi the hover should still disappear if you keep your mouse outside of the hover for long enough. Perhaps you could change the value of the setting . This setting controls how quickly the hover disappears. The default is 300 ms, meaning that after 300 ms outside of the hover it disappears. Similarly you could tweak the setting - this setting controls how quickly the hover shows, ie how long the cursor needs to be on a word before the hover is shown.\nI believe I was on 1.91.0, but maybe I didn't use it enough between upgrading to that one, and 1.91.1, to find this issue. Before that, I was on last month's iteration, which definitely didn't have this problem. Thank you. I was going to change that option, and then I saw a hint about having to be enabled. So, what I did is I actually disabled that one. Seems to have improved a bit. It seems to be still remaining sticky if I do put the mouse over it, so I'm not sure what exactly that option does (its description says the hover will remain visible when mouse is moved over it), but somehow, disabling this option makes the hover disappear if I move the mouse outside the code that triggered the hover, which is similar to the behavior I had before, I think. And if I click on the hover, it remains sticky, which is good/expected. Great. I changed from 300 to 600, so it doesn't appear so quickly. Thank you for the tips. I think there's still one question left -- what about when I'm selecting text (like shown in the video above) ? Wasn't the hover supposed to disappear, once I'm selecting text, and therefore the user is not interested in having a hover in the way of the selection? :) Many thanks, again!\nHi thank you for the comment. I believe the way the editor hover works is that when you click outside of the hover, the hover disappears. Meaning when you start a selection it disappears. However as you move the cursor to expand the selection and hover on a word the hover can appear again. Perhaps we could make the hover never appear when a selection is under way, I will open an issue about it and let the community put votes on it."}
{"_id":"doc-en-vscode-79b0d9e5f04377df4c0bd6eb9beb193e2d3459106696bcbbf47798a21e025729","title":"","text":"I am having an issue with this as well since updating versions. I attached some images. attempting to drag selected text into the object ! once selected tooltip stays in place permanently blocking destination ! I think once you hold down left click on a selection to start moving, the tooltip should always disappear. At least that is the behavior that you would expect in most applications.\n+1 to this, also experiencing the same issue after updating versions\nAlso having this issue. The Hover Hide Delay is using the Hover Delay instead, so if you have a long delay before the tooltip appears, you will have a long delay before it disappears. If you set the Hover Delay to 0 and the Hover Hide Delay to 1000, should see the tooltip appear and disappear instantly\nI have noticed and issue when using VS Code, in which the clicking outside of a tooltip will no longer dismiss hover tooltips. This occurs after leaving VS Code open for a while, including after a sleep/hibernate cycle. When this happens I have to restart VS Code, otherwise, clicking anywhere, including to initiate text selection does not dismiss any existing tooltip and the tool tip then interferes with the selection process. Perhaps there is a bug that is causing the described tooltip/click behavior to break after leaving VS Code open for some time. It might be related to this issue of tooltips being more sticky than intended. Version: 1.92.1 (user setup) Commit: Date: 2024-08-07T20:16:39.455Z Electron: 30.1.2 ElectronBuildId: Chromium: 124.0.6367.243 20.14.0 V8: 12.4.254.20-electron.0 OS: Windows_NT x64 10.0.\nLooked through the code a bit, and I think this is the issue this.hoverSettings = { enabled: hoverOpts.enabled, sticky: , hidingDelay: }; should be this.hoverSettings = { enabled: hoverOpts.enabled, sticky: , hidingDelay: hoverOpts.hidingDelay }; in and\nsupports your theory.\nHi thanks a lot for finding this error in the code. If you would like you can make a PR containing this finding, so we can merge your fix and you can participate as a community member in the project. If not I will make the fix that you mention :). Thanks for the catch."}
{"_id":"doc-en-vscode-01071f01cbb2b2bb8f2cf201825bc922f73b4cc8e954d5b726e3f25b826d5b26","title":"","text":"If you could make the fix, that'd be great, I'm not very familiar with git\nSounds good thanks again\nHi the PR that fixes this issue is here When this is merged, you should see the correct behavior in tomorrow's insiders release or next month's stable release. Please let me know if this is not the case and you continue seeing this issue."}
{"_id":"doc-en-vscode-7b22d46d73f47178751e664b0dc58b347e55a5fb4f6c0ed88473129856426fe7","title":"","text":"Type: <bBug</bIn the latest release syntax highlighting in html files with included JavaScript is so far off it's unusable. I have a comment (which should be green) Syntax highlighting has the the correct color. is dark blue. is green again. is a different color blue. The color choices and what parts of words are highlighted seems random. VS Code version: Code 1.71.2 (, 2022-09-14T21:07:15.900Z) OS version: Darwin arm64 21.6.0 Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (105)</summaryExtensionVersion ------ html-snippets0.2.1 vscode-languagetool3.8.0 vscode-languagetool-en3.8.0 vscode-icalendar1.0.1 vscode-color0.4.5 code-gnu-global0.2.2 simple-react-snippets1.2.7 vscode-reveal-hugo0.2.5 doxdocgen1.4.0 vscode-postgresql-client25.7.11 vscode-mac-color-picker1.1.0 vscode-eslint2.2.6 vscode-instant-markdown1.4.7 vscode-springboot-snippets1.2.0 xml2.5.1 rust-syntax0.6.1 vscode-html-css1.13.1 EditorConfig0.16.4 vscode-npm-script0.3.28 esp-idf-extension1.5.0 vscode-diff1.4.2 markdown-table-formatter2.2.4 change-case0.0.6 vs-code-http-server-and-html-preview2.2.2 copilot1.47.6882 go0.35.2 CppSnippets0.0.15 rest-client0.25.1 flux1.0.4 mediawiki0.0.4 tablegenerator1.0.4 better-cpp-syntax1.15.19 react-component1.1.0 vscode-hacker-typer0.1.1 diff-tool0.0.1 hugo-shortcode-syntax1.0.0 vscode-github0.30.7 cortex-debug1.6.5 vscode-language-babel0.0.36 vscode-clang0.2.4 vscode-http-client0.34.0 prettify-json0.0."}
{"_id":"doc-en-vscode-d644454c8bd63e87bd54a5516e5d58b130805ea9d9b15c0cc180bc1f9ae6ee04","title":"","text":"3 mongodb-vscode0.9.3 mongoose-os-ide0.6.0 vscode-docker1.22.1 csharp1.25.0 data-workspace-vscode0.3.0 mssql1.16.0 sql-bindings-vscode0.3.0 sql-database-projects-vscode0.19.0 python2022.14.0 vscode-pylance2022.9.40 jupyter2022.8. jupyter-keymap1.0.0 jupyter-renderers1.0.9 remote-containers0.251.0 remote-ssh0.84.0 remote-ssh-edit0.82.0 remote-wsl0.66.3 vscode-remote-extensionpack0.21.0 cmake-tools1.12.27 cpptools1.12.4 cpptools-extension-pack1.3.0 live-server0.4.1 vsliveshare-pack0.4.0 vscode-react-native1.9.3 sqltools0.25.1 sqltools-driver-pg0.3.0 vetur0.36.0 particle-vscode-core1.15.4 particle-vscode-pack1.15.4 particle-vscode-snippets1.15.4 vscode-boot-dev-pack0.1.0 vscode-concourse1.39.0 vscode-manifest-yaml1.39.0 vscode-spring-boot1.39.0 platformio-ide2.5.4 r-debugger0.4.7 java1.10.0 r2.5.3 wordcount0.1.33 bash-debug0.3.9 rust-analyzer0.3.1221 sockscode-vscode1.0.1 stackery1.1.4 spellchecker1.4.0 markdowntable0.10.2 html-preview-vscode0.2.5 cmake0.0.17 vscode-arduino0.4.12 vscode-java-debug0.44.0 vscode-java-dependency0.21.0 vscode-java-pack0.25.2 vscode-java-test0.37.1 vscode-maven0.39.0 vscode-spring-boot-dashboard0.7.1 vscode-spring-initializr0.11.0 codetour0.0.58 gistfs0.4.1 vscode-wakatime19.3.0 full-react-snippets1.4.2 vscode-java-saber0."}
{"_id":"doc-en-vscode-9ab1b7c87f9839fe6856227230ad26cfb464d6d24811b1e2b674c829b89085dd","title":"","text":"1.2 markdown-all-in-one3.4.3 vscode-aspell0.1.4 propertylist0.0.2 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\n<img width=\"940\" alt=\"Screen Shot 2022-09-28 at 6 56 06 PM\" src=\"https://user-\"<img width=\"879\" alt=\"Screen Shot 2022-09-28 at 6 15 54 AM\" src=\"https://user-\"\nDoes this reproduce in the with all ?\nIt sure does. <img width=\"517\" alt=\"Screen Shot 2022-09-28 at 7 12 08 PM\" src=\"https://user-\"<img width=\"705\" alt=\"Screen Shot 2022-09-28 at 7 13 25 PM\" src=\"https://user-\"\nPlease share the text of file that causes this\nIt ain't pretty ...\nIt's a template file for Hugo. Specifically a file called\nsame as semantic highlighting is broken for some reason\nReproduced with The special thing that there's a new line right after"}
{"_id":"doc-en-vscode-2da2309605aaba2b2d309b04838d9f0f5f5edfbb1062d50c2267aa0fe8437da4","title":"","text":"Version: 1.78.0-insider (user setup) Commit: Date: 2023-04-04T09:32:52.453Z Electron: 22.4.3 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0. Sandboxed: Yes run from a Windows command prompt The tunnel starts and prints open VS Code, and open the output Note that the output is stuck at Missing are the message and the info that the tunnel is attached The UI thinks the tunnel is still connecting. Sometimes this also works, but when I try it, most of the time it is stuck\nCan you please enable trace logging and share the output?\nNothing extra messages shown when the Desktop tunnel attaches:\nThis issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!\nStill a problem in Version: 1.78.0-insider (user setup) Commit: Date: 2023-04-12T05:19:38.288Z Reproduces every time I try it\nThis issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!\n<!-- 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!\nI'm still not seeing info in the log in VS Code that the tunnel is attached after from the command line and seeing the \"Open this link in your browser\". <img width=\"945\" alt=\"image\" src=\"\"\nthe tunnel will not start unless you \"Turn on Remote Tunnel Access\"\n<img width=\"730\" alt=\"image\" src=\"\"Looks good to me after enabling tunnels in VS Code\nThanks. Enabling Tunnels in VS Code fixed it."}
{"_id":"doc-en-vscode-f94d7040de035bfeef3e8838b26e38bab8899640ef0807100c27f24ab8a11f8d","title":"","text":"I got into screen reader optimized mode on Windows by using NVDA, but after closing NVDA, I don't know how to leave that mode. I tried clicking on the indicator in the taskbar, and also tried searching \"accessibility\" in the command palette for a command that would toggle it off. !\nclicking on the indicator in the taskbar should work we should also have a toggle command in the command palette so that clicking isn't required and can reference that command in this help menu !\nfyi for any input\nAgree with the above. Also on vscode restart you should no longer be in screen reader mode if that is happening, it is a bug. take into account that the accessibility help dialog shown in the screenshot has not been polished since we introduced it. We could make sure the text is more concise and user friendly. Visually it should not be polished since this is targeted for screen reader users.\nTry to set a custom keybinding for this command - I find it very handy\nHow do I get that status bar entry to show? I tried the following: Turn on NVDA when Manually set `\"editor.accessibilitySupport\": \"on\"\nThis command should work !\nThat still doesn't cause the status bar entry to show for me. I've checked the status bar show/hide menu and it's not in there either.\nany interesting settings? https://user-\nI was about to say I have the same issue, but then noticed that I had to go to a text editor to test out the feature. I was running the toggle command in the Settings editor.\nNot being in a text editor was the problem! I was either in the settings editor or the endgame notebook."}
{"_id":"doc-en-vscode-16c5838b6363a2d329d995eede075963d41f0db9e266fd9b6ecc146ad0744d5d","title":"","text":"<!-- 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.43.0 OS Version: n/a I have the set to in my settings: Given a Does not produce any warnings as expected. However in : The linter says\nThis has the same root cause as : script are owned by the html extension instead of by the JavaScript extension. Fixing that is difficult However we could have a small fix that just makes html understand the setting. Marking this as help-wanted\nHello I'd like to try my hands on fixing this issue. Can you give some pointers as to which files are good places to start?\nThis change will need to be made in the HTML extension Here's where we configure TypeScript for the html extension: You should: Pass the value for in with the initial configuration Make sure that the language service updates its value for when the VS Code setting changes\nIs there another way to get the setting value other than vscode.workspace.getConfiguration()? The 'vscode' module cannot be found when I try to import it into javascriptMode. I think 'vscode' would have to be as a dependency in in order to import 'vscode'.\nRight now I'm passing in a default 'false' for experimentalDecorators in the initial configuration and passing the settings into getJavascriptMode.doValidation to update compilerOptions and calling ts.createLanguageService(host) every time doValidation is invoked. It has the expected behavior, but is there a better way to update the compiler options without creating the service every time it runs validation?\nIs called when the file is changed? If it is, try updating the object that it returns\nI am reproducing this error now with the following code: I realize this is known, but I will add the mention with respect to . Here is the relevant docs page, if a person wanted to make a unit test using If anyone finds this in the future, if is set in , it should suppress this error. Additionally, both and files, in the root of the project, take precedence over that setting."}
{"_id":"doc-en-vscode-27adc194a623d16ca191f853a71f17283194096678c751615df5eac581177705","title":"","text":"Quick pick and events are disposables: is a listeners are : , , , , , A few instances of pickers or events not being disposed or registered as disposable: [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] //cc\nThanks for catching these just taught me that there's a better way to use the quick pick API - with and that will avoid this\nInteresting, curious to see how that change looks like, I have a lot more places:"}
{"_id":"doc-en-vscode-42826047b7ae7b80323556308179af06e5b830577349da0957d5316b73aeb417","title":"","text":"! I see this sometimes, but it often gets fixed if I try again, or close and reopen the editor, etc. Right now it keeps happening and it's just impossible to click the hover. I don't know how this API works but I assume this is on vscode's side. Happy to set breakpoints and debug\nI couldn't reproduce this so I'm not sure what's the root problem. However, I'm saving here a patch which simulates a hover very similar to the one in the gif: <img width=\"1141\" alt=\"image\" src=\"https://user-\"diffn- editor.focusNotebookCell(newCell, newFocusMode, { focusEditorLine: 1 });n+ await editor.focusNotebookCell(newCell, newFocusMode, { focusEditorLine: 1 });n\nI tried for quite a while but couldn't repro. I think there might be some settings that cause the issue reproduce. Does this reproduce when you comment out all your user settings?\nYeah, it reproes with all settings commented out\nThanks to via we could find a repro. Reproduces consistently when hovering at the end of the line: It turns out it has to do with the range the hover provider returns. If the hover provider returns a range that spans one line above the hover request, the hover will render one line above. If the hover provider returns a range that spans two lines above the hover request, the hover will render two lines above, etc. Here's a simplified patch: https://user-\nTo verify, use gitlens and hover over the end of the line at\nWorks great but raises the question, why does gitlens return a hover with a multiline range? And I get a highlight in this region, but it blinks and disappears on line 919, and on other lines, no highlight. !\nPR to improve the highlight range at\nI'm still seeing the original issue at"}
{"_id":"doc-en-vscode-855ddc10478dfb1a1d9efd0548494edbdea117446cd534245eeadfdd0fe05283","title":"","text":"a deprecated extension, for example Bracket Pair Colorizer extensions viewlet -notice how it is not very visible that the extension is deprecated. If the user wants to migrate they have to click on \"configure these settings\" and uninstall the extension 's solve both of these things by rendering a \"Migrate\" button for deprecated extensions that have alternatives The migrate button would be similar to the Update button in looks, but it would either: Install the alternative extension, uninstall the deprecated one Uninstall the deprecated extension, open settings view with the desired settings shown\nI do not like Migrate button for an extension like Bracket Pair Colorizer that needs settings to configured. It felt little weird to me enabling Migrate button for this extension and opening settings editor but not applying any settings to migrate. Hence I enabled this button only for those extensions with alternate extensions <img width=\"1120\" alt=\"image (2)\" src=\"https://user-\"\nthat makes great sense, thanks! I plan to try this out as soon as there is a new insiders out. Feel free to close this issue then :)\nI just tried the latest insiders which should have your changes. However I do not see the Migrate button in the Extensions details view. Also it would be cool if the button was also in the extensions viewlet. Similar to the button. !\nIts because alternate extension is already installed and migrating is just uninstalling the the deprecated extension. I thought it might be too aggressive to show in Extensions Viewlet. What if users do not want to migrate and they always see it in extensions viewlet?\nyou are right. When I uninstall eslint all is good and the button gets rendered in the extension details - cool! Extensions viewlet - as for users not wanting to migrate and still seeing it - I think that is fine. It is the same if you do not want to update and you always see \"reload required\". It is an update, it is just an update to a different extension. I do not find this too aggressive, especially since we want to push users off deprecated extensions.\nMakes sense. Showing Migrate action in extensions view (without extension name) <img width=\"293\" alt=\"image\" src=\"https://user-\"\nAwesome, thanks! Let's see what the users says about the full flow and how it goes during endgame :)"}
{"_id":"doc-en-vscode-29de378203675c3ef5e2ed5406895c80582faeae66917ad0d56e01d48b0aafac","title":"","text":"Type: <bBug</bCC In inline Copilot chat, \"Regenerate\" button is not readable by some screen readers, such as JAWS. This is because the button is labeled with title attribute. Please add aria-label so that JAWS can recognize the label. For better communication, I have recorded a gif: ! VS Code version: Code - Insiders 1.86.0-insider (, 2023-12-20T05:36:57.756Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (116)</summaryExtensionVersion ------ vscode-openapi4.19.2 android-dev-ext1.3.2 aiprm-lang0.0.2 Bookmarks13.4.2 openscad1.2.2 spellright3.0.118 zoterolatex0.4.1 mermaid-markdown-syntax-highlighting1.6.0 doxdocgen1.4.0 vscode-markdownlint0.53.0 vscode-eslint2.4.2 vscode-quick-select0.2.9 vscode-deno3.30.0 gitlens14.6.1 EditorConfig0.16.4 prettier-vscode10.1.0 vscode-firefox-debug2.9.10 shell-format7.2.5 vscode-google-translate1.4.13 codespaces1.16.5 copilot1.143.601 copilot-chat0.12. remotehub0.62.0 vscode-github-actions0.26.2 vscode-pull-request-github0.79."}
{"_id":"doc-en-vscode-699207499bdafb919d23058d3f2c4c8598c40d7f3ace686cb27e7b538c76cda6","title":"","text":"cloudcode2.2.1 overleaf-workshop0.6.1 cslpreview0.2.2 easy-snippet0.7.5 path-autocomplete1.25.0 latex-workshop9.16.1 lilypond-syntax0.1.1 scheme0.2.0 better-cpp-syntax1.17.2 language-julia1.65.2 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.11 git-graph1.30.0 azure-dev0.8.0 vscode-azureappservice0.25.1 vscode-azurecontainerapps0.6.1 vscode-azurefunctions1.13.1 vscode-azureresourcegroups0.8.3 vscode-azurestaticwebapps0.12.2 vscode-azurestorage0.15.3 vscode-azurevirtualmachines0.6.5 vscode-cosmosdb0.20.0 vscode-docker1.28.0 vscode-edge-devtools2.1.3 black-formatter2023.7. flake82023.10.0 isort2023.11. python2023.23. vscode-pylance2023.12.101 jupyter2024.1. jupyter-keymap1.1.2 jupyter-renderers1.0.17 vscode-jupyter-cell-tags0.1.8 vscode-jupyter-slideshow0.1.5 remote-containers0.329.0 remote-ssh0.108. remote-ssh-edit0.86.0 remote-wsl0.81.8 vscode-remote-extensionpack0.25.0 azure-account0.11.6 azure-repos0.38.0 cmake-tools1.16.32 cpptools1.19.1 cpptools-extension-pack1.3.0 js-debug-nightly2023.12.1817 powershell2023.11.1 remote-explorer0.5. remote-repositories0.40.0 remote-server1.6."}
{"_id":"doc-en-vscode-4dde3473589e6675bddb475c089dcd0146797062fd1843ce7f575d40ea4976e2","title":"","text":"vscode-github-issue-notebooks0.0.130 vscode-node-azure-pack1.2.0 vscode-selfhost-test-provider0.3.22 vscode-serial-monitor0.11.0 vscode-speech0.3. vsliveshare1.0.5900 windows-ai-studio0.2.1 autodocstring0.6.1 pandocciter0.10.3 shiny-python0.1.5 shinyuieditor0.5.0 quarto1.109.0 r-debugger0.5.4 java1.25.1 vscode-xml0.26.1 vscode-yaml1.14.0 r2.8.2 multi-command1.6.0 AudioQ0.0.2 vscode-deepl1.0.10 abc-music0.4.0 lua3.7.3 latex-utilities0.4.10 cmake0.0.17 vscode-terminal-here0.2.4 windows-terminal0.7.0 errorlens3.16.0 intellicode-api-usage-examples0.2.8 vscodeintellicode1.2.30 vscode-arduino0.6. vscode-java-debug0.55.0 vscode-java-dependency0.23.3 vscode-java-pack0.25.15 vscode-java-test0.40.1 vscode-maven0.43.0 markdown-all-in-one3.5.1 grammarly0.25.0 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nThank you for the issue JooYoung. I cannot access the gif because it seems to be a private link."}
{"_id":"doc-en-vscode-ca25ee4f446199330b44d2170f47a1508cfadc3289185505396fa069dcfcf9e0","title":"","text":"I think a class like this could be helpful: Usage: Originally posted by in\nplease let me know if you like this!\nThis class is primarily owned by Hence assigning to him.\nYes, feel free, I can review a PR, thanks."}
{"_id":"doc-en-vscode-28ea3b55176adb1fbd98d8b602298806560ecd6a353d7bb12f7750f2df4a5d2e","title":"","text":"Type: <bBug</bThis issue is related to the Julia extension. I filed an issue , but I also filing it here (as suggested by As per the initial post of the above link, all extension work perfectly fine when the Julia extension is disabled. here are dmp files as per VS Code version: Code 1.79.2 (, 2023-06-14T08:57:04.379Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (50)</summaryExtensionVersion ------ rainbow-brackets0.0.6 vscode-django1.10.0 python-environment-manager1.0.4 python-extension-pack1.7.0 code-runner0.12.0 copilot1.94.220 vscode-github-actions0.25.8 vscode-pull-request-github0.66.2 nbpreviewer1.2.2 language-julia1.47.2 vsc-python-indent1.18.0 vscode-github0.30.7 vscode-opn1.1.2 MagicPython1.1.0 vscode-azureappservice0.24.9 vscode-azureresourcegroups0.7.5 vscode-docker1.25.2 csharp1.26.0 isort2022.8.0 python2023.10.1 vscode-pylance2023.6.40 jupyter2023.5."}
{"_id":"doc-en-vscode-5a7d1e05ea0e548a12d81d61d52ac7d192f2efd522ad5d66a0ee526e76ba3d23","title":"","text":"jupyter-keymap1.1.2 jupyter-renderers1.0.15 vscode-jupyter-cell-tags0.1.8 vscode-jupyter-slideshow0.1.5 remote-containers0.295.0 remote-ssh0.102.0 remote-ssh-edit0.86.0 remote-wsl0.79.5 vscode-remote-extensionpack0.24.0 azure-account0.11.5 cmake-tools1.14.34 cpptools1.16.3 cpptools-extension-pack1.3.0 powershell2023.6.0 remote-explorer0.4.0 remote-server1.2.1 autodocstring0.6.1 r-debugger0.5.4 r2.8.1 vscode-open0.1.0 spellchecker1.4.0 python0.2.3 rmarkdown0.0.14 cmake0.0.17 vscode-counter3.2.1 intellicode-api-usage-examples0.2.7 vscodeintellicode1.2.30 jinja0.0.8 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nAs mentioned in the linked issue, it happens for me as well. I can reproduce it with Insiders version too and the same happens with a few older julia-vscode extensions I tested. <details<summaryVS Code version</summary</details\nThere seems to be an issue with spawning a process. The symbolicated logs seem to have the same form.\nI'd expect that this happens when we try to spawn the Julia process that powers the LS. Any chance we can debug this further? I assume we can't handle libuv failing to spawn a process anywhere in the extension code, right?\nAs asked in the I want to add that I can reproduce this as well. From the linked thread:\nSorry for the delayed response, can you please provide the output of the following steps to understand the error 1) In a terminal set the following env variable 2) Launch VSCode from the same terminal session with arguments that redirect stdout and stderr to a file as seen below, replace the file paths where appropriate Additionally, once the extension host crashes open command palette in VSCode and run and attach the output from the tab of the developer tools that got opened."}
{"_id":"doc-en-vscode-00ed95b979ce3643fe5bb3972f7193a24873a5ca31f6a6a498df3826b677f092","title":"","text":"unfortunately this is a fatal error that cannot be handled in the application layer. But we should be able to see the output of from the above logs.\nI have done this, see attached.\nSame here\nThanks for the logs, in both cases the launching of child process triggers a fatal error from at due to . I would like to understand if this can repro with outside VSCode since we haven't done any modification to the spawn API. I have simplified the Julia language server process spawn call from your logs into the following script, can you run it with node v18.15.0 which can be downloaded from , the steps would be 1) Save the following script to 2) Install v18.15.0 3) From terminal, run and attach the generated output\nApparrently Julia expects 8 arguments. Not sure why though.... if length(Base.ARGS) != 8 error(\"Invalid number of arguments passed to julia language server.\") end\ncan you help with above error, I would like to create a minimal repro outside VSCode since this is an issue with\nIt seems we need additional arguments in in the .js file see or here\nI two empty arguments in the file However, I have no idea if these arguments are relevant. Then things seem to work Are we expecting the server to shut down at the end? EDIT: the process only shuts down if I hit enter. If I don't press any key it keeps running and the last message is 'Received new data from Julia Symbol Server...\" output is:\nThanks for fixing the test case No, I was expecting the error to show up\nCan you run our bisect tool in the terminal . In each step install the Julia extension (if not present) and if the extension host terminates with the above error, mark it as bad commit. This would help us narrow down if a change from our side introduced the regression.\nLooking at the above, the argument right after is In the test case, I set this argument to empty though\nI think it is fine to skip the pipe name, looking at the code it is only responsible for monitory crashes from the language server."}
{"_id":"doc-en-vscode-604929d75effac1cee9b36252a9c3364269e94514929f7b7906bbf0cad14ceae","title":"","text":"Only on the first run I had to open my project () install the julia extension trust the authors of the folder open a .jl file in my project\nI will add that, when I run the above code the extension server fails every time except for the first time. The first time I get the ERROR below, but the Language Server seems to restart. Also it actually takes ages (maybe 2 or 3 minutes) for the LanguageServer to start. <img width=\"1194\" alt=\"image\" src=\"\"\nThanks for the bisect results, can you confirm if the extension host terminates with julia extension in . Download links available at\nyes. it terminates\nSorry I should have provided link to , can you try it again with this version. I am trying to confirm if Electron 22 update was the trigger.\nI don't have time for this right now. Interestingly I get another error now (I am using the most recent VS Code version now 1.81.1) Not sure if this is connected though....\ncan you also confirm , thanks!\nI can reproduce the extension host termination with VSCode 1.77.3 and julia-vscode v1.47.2.\nThanks for confirming, that eliminates the allocator changes we adopted for Electron 22 update. Refs\nThis issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!\nThanks for looking into this, Do you need any more info about the extension?\nMight be fixed by\nOnce the libuve PR us merged, do I need to wait for the next minor julia release?\nThanks for sharing the fix , I will backport the fix into Electron as next step.\nSteps for verification: 1) Open extension in latest stable, add the following changes 2) Debug extension, run command 3) Stop the debug session 4) Start debug extension again, run command 5) It should crash the extension host Perform steps 1-4 again in latest insiders with the fix and it should not crash.\nSeems to be specific to windows, I cannot repro the crash on a Mac.\nYeah, the seems to be in the Windows kernel.\nYes बुध, 25 अक्तू॰ 2023, 11:15 pm को Sebastian Pfitzner < लिखा:"}
{"_id":"doc-en-vscode-37c14446abcbab97f9972899ea5d7b73898b7f24e6863f703a941d483bbd7dd4","title":"","text":"Testing a new notebook and make an edit profiles to restart the EH the file when prompted and provide a file name: The untitled-n.ipynb tab remains open, rather than opening , :bug: The file is no longer marked dirty, even with futher edits and can be closed without prompting to save\ncan you maybe check from the notebook side?\nLuna paint behaves similarly with one extra step: a new image and make an edit profiles to restart the EH the file when prompted and provide a file name: The untitled-n.ipynb tab remains open, rather than opening , (different) and the switch profile operation is blocked switch profiles again The file is no longer marked dirty, even with futher edits and can be closed without prompting to save\nSomehow today I cannot reproduce an issue with insiders: ! Please give me more detailed steps and see if you still find this.\nstill seeing it. Did you try making edits after switching? that's when the dirty indicator doesn't show up anymore. ! I saved as a different filename in the gif, but keeping the untitled filename still doesn't show a dirty indicator, nor does it auto-save.\nThis seems to me like something notebooks need to handle better: if you enter an extension host that does not have the notebook extension and you make edits, the editor should probably not allow that. I.e. the editor should maybe turn readonly once the extension is disabled or not present.\n- the notebook extension is built-in so it's still available in an empty profile. The repro steps can even start with an empty profile -and make an edit to the first cell profile to default and save as 1.ipynb when prompted an edit in the notebook :bug: file is not dirty\noh nice, sounds like an issue related to EH restart then, will update the title With your working copy knowledge you might be even able to figure this out ;)\nIt looks like the issue in the notebook scenario is that it's calling save directly on the workingCopy in the : In the untitled case, that will delegate to saveAs, which will dispose the untitled workingcopy without opening a new editor with the resulting . The editor is left open with its underlying WorkingCopy disposed. For non-built-in custom editors though, it seems like we should just close them if we don't know if they will be supported in the new profile."}
{"_id":"doc-en-vscode-2a151221418fdca671faf02f8c4c25579be85a82e35b64b93e7af925dd4d6a96","title":"","text":"I don't see how we can expect a custom editor to support a scenario where its source extension isn't installed - is that even possible? I went over the issue with and concluded that we can defer to next release since the previous stable version also didn't handle this scenario well.\nfyi I just created which is a similar issue for custom editors. Here for notebooks I suggest the following: if the EH restarts and still has the notebook extension for the opened notebooks, reconnect to the EH and allow to further make edits on the editor (I actually thought this was already implemented based on the work did) if the EH restarts and there is no more extension for the notebook editor, turn the notebook readonly and inform the user somehow Does that make sense?\nThe previous change just doesn't account for untitled notebooks, but I think I can fix that. That makes sense, although I'm surprised that we would require all custom editors to handle this (asked about it in the other issue)"}
{"_id":"doc-en-vscode-07174a51c2da62f32a06b3fa2168e0caabe3df89d81edb5a72a2688ed0b1f3a6","title":"","text":"Testing My first reaction for how to stop dictation in the editor was to click the flashing microphone. It would be cool if something happened when the flashing microphone is clicked.\nI will turn this into a real with action and hover."}
{"_id":"doc-en-vscode-c22d84383d6a8259c47c44307076aeebc4034368896e3118bd86ac7a129be5dc","title":"","text":"Type: <bFeature Request</bCC Please consider auto-activiating accessible view in terminal when user hit enter key. In most cases, screen reader users want to open accessible view after executing command in terminal. Thus, pressing Enter key can do: the current command to terminal. Accessible View immediately. Rather than having this as the default mode, we could consider adding this as a custom user setting. VS Code version: Code - Insiders 1.85.0-insider (, 2023-11-02T09:02:24.464Z) OS version: Windows_NT x64 10.0. Modes: <!-- generated by issue reporter --\nThis makes sense. let us know if you have any thoughts.\nI imagine this mode can boost user productivity because VSCode now sends user typing in Accessible View directly to the active terminal. If this mode is , users will experience more seamless round trip between terminal input and accessible view without having to press Alt+F2 and ESC.\nTo verify, enable . Run a command in the terminal. The accessible view should open."}
{"_id":"doc-en-vscode-b770bc26ce0ec0d3f98b8063540c205532df08cf60e3d1f3272a845554c736e3","title":"","text":"Terminal: <img width=\"328\" alt=\"image\" src=\"\"Editor: <img width=\"436\" alt=\"image\" src=\"\""}
{"_id":"doc-en-vscode-25def4b51855289428ac597ab7d9f4ea91d4d6d2a8681bc3bfb59c38c46fc148","title":"","text":"Currently the list sets the role of each item to be This should only be done for the Tree, not for the list. List should use . More details Tree that actually uses the list should probably pass the role as the getRole to the list it extends from. if you are busy let me know and I can look into this.\nWe should also verify this nicely works with NVDA, since it is part of aria 1.1 spec.\nSure, PR would be great.\nSure. Assigning to this milestone and if I do not find time might get pushed out.\nTo verify , turn on NVDA suggest box -make sure that the suggestions do not have \"Level 1\" read ath the end explorer -make sure the items have appropriate Level read at the end"}
{"_id":"doc-en-vscode-036a444922f003c04c5053ce39395d1af6b1ad29130a7cf0df8493968b3c63bd","title":"","text":"Issue Type: <bBug</bSet the variable to something like this: You should see something similar to the following: I'm assuming it's associated with . If I'm reading correctly, it checks for semicolons but not things like , , , etc. I understand this is probably an edge case. I was able to workaround by: creating a new function to wrap the others set to the new function VS Code version: Code 1.69.0 (, 2022-07-07T05:28:46.408Z) OS version: Darwin arm64 21.5.0 Restricted Mode: No <!-- generated by issue reporter --\nThanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.69.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!\nI can confirm this bug still exists in 1.69.1, and is probably less of an edge case than you might think , as I found this issue when the terminal wouldn't start because I had powerline installed.\nO\nMy bash (GNU bash, version 5.1.16(1)-release (x86_64-apple-darwin21.1.0)) didn't want to work with empty functions, this reproduces the problem though:"}
{"_id":"doc-en-vscode-f211d0bdc21141d093e3b73b4cf6063add58d7cbdeb57eec7739914d024796da","title":"","text":"Issue Type: <bBug</bwhen i enable shell integration, i get an error: my contains: VS Code version: Code - Insiders 1.66.0-insider (, 2022-03-28T07:49:37.594Z) OS version: WindowsNT x64 10.0. Restricted Mode: No Remote OS version: Linux x64 5.10.60.1-microsoft-standard-WSL2 <details<summarySystem Info</summary </details<details<summaryExtensions (11)</summaryExtensionVersion ------ better-cpp-syntax1.15.13 remote-containers0.230.0 remote-ssh0.77. remote-ssh-edit0.77. remote-wsl0.66.0 doxdocgen1.4.0 better-cpp-syntax1.15.13 cmake-tools1.10.5 cpptools1.9.7 cpptools-extension-pack1.1.0 cmake0.0.17 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nlooks like you set somewhere which re-writes your . Right now if we detect possible problems with unsupported formats we bail out and disable shell integration by design. To workaround this you could point your at a function and run inside the function instead, for example\nAssigning to April to see if we can improve our handling here.\nno. i'm not setting . ugh. testing this is a nightmare. vscode seems to keep some persistent state on the server affecting shell startup. anyway, i'd recommend testing with my exact client/server OS combo. is set by the OS to the value above, but weirdly that's not actually what's used to echo my prompt. my prompt, as set in my file is .\nIt might be set in your or ? VS Code sources a shell environment on startup and that gets used as the base environment for terminals. For WSL you'd need the vscode server to shutdown fully.\nno, this also happens when connecting (via ssh) to a fresh CentOS7 install."}
{"_id":"doc-en-vscode-fa01d44fd01c920dba5938a9a29193a1131c9b0a6e47d76d30edbeac7d5804be","title":"","text":"<img width=\"965\" alt=\"image\" src=\"https://user-\"\n<img width=\"888\" alt=\"Screen Shot 2022-03-31 at 17 04 04\" src=\"https://user-\"\nIt seems that works right on Manjaro X86_64 <img width=\"822\" alt=\"image\" src=\"https://user-\"\nSame here, with Arch and default As workaround I blanked the $PROMPT_COMMAND on my\nThanks for finding the , should make it easy to test against\nthe shell integration feature also breaks long line-wrapping in bash (happens on Ubuntu, too). the terminal wraps the line before reaching the right edge of the terminal window, and it wraps to the same line overwriting the existing ontents of that line. scrolling through line commands in the bash command history is completely broken.\nTentatively assigning to July as this gets hit with Arch's default"}
{"_id":"doc-en-vscode-2350bfa98ae8efe2becaeeb357eb365537914949fac827438bd93af07544c49d","title":"","text":"See I have had to revert our commit via\nIssue could reoccur if shared process start up is delayed.\nWhat was the problem with ? As far as I can see from the code, every client to the shared process should wait for it to be running. . If this assumption holds, change was correct. Do you have any suggestion as to until when to delay the spawn?\nYeah it would be great if the workbench could signal back some event when editors are restoring, but we currently do not have that. Who is waiting for the shared process to be ready, is it just telemetry and extensions management? We have to be careful to not introduce another deadlock area...\nHmm it ain't the services themselves who wait but the container of them. AFAIK, both the and the wait for the shared process to start.\nthe workbench does not really wait right, it just runs that code in parallel to the rest of the workbench loading.\nThe workbench will show. But every call to a shared process service will wait until the shared process has started serving the socket. For example, extensions won't show up in the viewlet until the shared process appears.\nIt was a guess from analysis and also from testing/verification that removing the delay fixed the dialog issue. I do not think we have a concrete reason why is it depending on the delay.\nOK. So it seems we can easily delay it. Can you find a signal in the main process at which point we should spawn it?\nsomewhere in  possibly with some delay? Alternatively the call to opening a window () returns the opened windows and there is a  promise you could join on. That one is literally resolved when all editors have restored in VS Code.\nBut the shared process already starts only . Should we just put a timeout then? That would make this change exactly what did last month. I'm not saying it's wrong, just stating the fact. Edit: Actually... his change looks very weird to me now. It seems to delay the connection to the process, not the actual spawning.\nyes I think what should get delayed is the creation and opening of the shared process window.\nJust note that I have removed the uninstall dialog last milestone. So this might not be an issue any more."}
{"_id":"doc-en-vscode-d07bf54acd45cb8731962f289811795dc8a65ab27f9b2b6864bd3d454fd5ae14","title":"","text":"Issue Type: <bBug</bWith at least one folder loaded in Code: to Code Preferences Settings on either \"User Settings\" or \"Workspace Settings\" Notice tab spacing is jumpy when changing active selection. It should NOT be as jumpy. I believe it's caused by the text being bolded on active selection. <iDesired</i! <iActual</i! VS Code version: Code 1.28.2 (, 2018-10-17T00:18:43.347Z) OS version: Darwin x64 18.0.0 <details<summarySystem Info</summary </details<!-- generated by issue reporter --\nHere's the\nI'm not sure about this change, I think the bold is necessary to make the selected tab noticeable. Some themes hide the underline on the selected item, and in some themes, the color difference is not really noticeable. So I would worry that this would make it impossible to tell which tab is selected. I also don't really have an issue with the slight shifting, I've never noticed it before now.\nWe should try to remove this shift as it's not really smooth. In our other tabs (panels, settings json) we don't use alternate font-weights for active/inactive, so I think we should keep them consistent and the same. Alternatively, if we really want to make the states look different we could adjust the opacity (just like the other tabs) as long as they pass the color contrast ratio: !\nI agree that it's not smooth. It's also not consistent with the other tabs in the product. There is a hack that can remove the shifting (discussed with this ), however I think that might be overdoing it to achieve this effect. I would add the opacity change as well to help reinforce the two states.\nShould I just borrow the inactive color from the panel tabs, at least for the builtin themes? Or if I should use opacity, can you tell me what color/opacity to use? Looking through some popular ones, I don't think this change would be a problem for that many other themes really... Also for folder settings, the folder name and string \"Folder Settings\" are currently distinguished by size and color, so we might still need 3 colors.\nActually the current panel tab colors in Monokai don't meet the contrast requirement: ! !"}
{"_id":"doc-en-vscode-ea890d041ce6245e0de73fccce03f7d068138cfdc686be6149a745b5cd0a4cfc","title":"","text":"We only need to meet the color contrast on the themes we own, which is light/dark/hc. Here's the contrast on the inactive text: Here's the colors and opacity for the active/inactive panels: For the folder settings, you can change the opacity to (which passes) and will end up looking like this: !\nNot using the panel foreground color because the background is not always the same, but I think it looks good as is after the PR."}
{"_id":"doc-en-vscode-4f03d6215c953cdc240adb37b46de9724dec7220c2cafde870340ce4262ca84c","title":"","text":"A Visual Studio Code workspace file is currently recognised in Linux as a normal plain text file. This is because there isn't a MIME type for this file. Applications can provide additional MIME types as described here: Not having a MIME type has a couple of issues, for example the files are shown as plain text files in the GUI, which makes it hard to distinguish source code files from the workspace file. This slows down navigating to a workspace and opening it. Find the workspace in the following screenshot ! It's currently impossible to theme such a file because it's not seen as a different MIME type:\n(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.461 --<!-- potentialduplicatescomment --\nThis also means that you can't make double clicking the workspace from a file browser open it in vscode, unless you're OK with all text files opening in vscode, which is probably not what most folks want.\nThis bug has been fixed in to the latest release of ! you can help us out by confirming things are working as expected in the latest Insiders release. If things look good, please leave a comment with the text to let us know. If not, please ensure you're on version of Insiders (today's or later - you can use in the command pallete to check), and leave a comment letting us know what isn't working as expected. Happy Coding!\nHi can you verify this issue? Check out the previous comment.\nI tried to verify this but am not sure how to do this myself. I've not used desktop linux extensively; I tried reinstalling Insiders from the on Lubuntu to see if it associated files with VS Code, but that didn't happen.\nVerified by installing insiders from on Ubuntu and was able to see mimetype and set a custom icon ! upon uninstalling it was removed."}
{"_id":"doc-en-vscode-7f030cd24b5ab75c5cb04da5054d6dc5a00e406ee5e3058d2612d5246686f328","title":"","text":"Repro: terminal with sticky scroll enabled command that \"overflows screen\" (ie, it scroll terminal beyond what's visible) it once again to again overflow screen (not sure if it needs to be run again, but that's how I repro'ed) screen (ctrl+l) once again & see sticky scroll shown even though not required (also reported with vid and logs in DM to ) Version: 1.85.0-insider Commit: Date: 2023-11-29T02:45:05.413Z Electron: 25.9.6 ElectronBuildId: Chromium: 114.0.5735.289 18.15.0 V8: 11.4.183.29-electron.0 OS: Darwin arm64 23.1.0"}
{"_id":"doc-en-vscode-9e15b3f6b88f9efeb26f51cf7838743c4517c214c4c83bf381fc1b4e3fe363aa","title":"","text":"! !\nI think this was the result of moving the progress bar below the input. Since the progress bar use to provide the padding.\nlet's just call it an exploration of compact mode :) /s\nThis is partially as designed, but it still needs improvement. The latest changes make it so we have a nice cutoff when the quick pick list is scrolling: <img width=\"653\" alt=\"CleanShot 2022-12-16 at 09 23 10 src=\"https://user-\"However it should probably still use padding at the bottom of the list, rather than the container, to ensure this doesn't happen when the entire list is visible/not scrollable.\nI dont want to be the annoying guy at the party here, but an empty quick pick now looks like this: <img width=\"647\" alt=\"image\" src=\"https://user-\"vs before <img width=\"633\" alt=\"image\" src=\"https://user-\"\nHaha, whoops. I'll have another go at this then.\nverified the original issue here, but we'll continue the next issue in:"}
{"_id":"doc-en-vscode-447381b4720f615da682bba9296649dfdc936bb855dc930286a6df92dd89e53a","title":"","text":"The select box in the panel header should have a white background: ! This is similar to the recent breakage with the simple editor widget background color in SCM and extensions views.\nTo Verify: to an obvious color. that terminal and output select boxes are using these when they are in their default locations in panel."}
{"_id":"doc-en-vscode-a7b8e207d5031b1670f2dd4cb8f6e1f344a5dfe43861c2e4732dceb02c02d544","title":"","text":"<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --As mentioned in the thread by there is a need for a tool that would help developers engaged in the VSCode project identify the Trusted Types violations. This can be achieved by adding as a devDependency and an appropriate yarn script.\nI have also a task-definition so that tsec errors show in the editor itself. F1 Run Task tsec <img width=\"1472\" alt=\"Screenshot 2020-09-01 at 13 07 22\" src=\"https://user-\""}
{"_id":"doc-en-vscode-9620021b9ccf591acd74fdc95f7b5b953d89435f458f03865f0559e017ef9dbf","title":"","text":"<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --I'd like to have a theme setting that would allow me to change the foreground of the text in red next to the shortcuts. I've reached out to the dev tools and wasn't able to track the setting. I searched Google, SO, ChatGPT and I've tested a bunch of foregrounds and nothing works. <img width=\"1012\" alt=\"Screenshot 2024-01-10 at 16 21 18\" src=\"\"\nI a new color . It is derived from the"}
{"_id":"doc-en-vscode-61a8d22f99103044f3c3cf76ba00ee7939a0047be075c8026051c789d83c3e12","title":"","text":"Currently, we have to add this copyright header manually to every new file: /\nCopyright (c) Microsoft Corporation. All rights reserved. Licensed under the MIT License. See in the project root for license information. *\n-------------/ An ES Lint rule that has an auto fix would be really nice. What are your thoughts ! (using )\nI like. The closest that we have today is this snippet\nLet's do it!"}
{"_id":"doc-en-vscode-0c3468851b840d9011507a2315a0ed727cf93c6e27b47aa39d9c4d152a2ce8f1","title":"","text":"<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --when you import a profile file, vscode will create a new profile but not overwrite current one or merge it to current one Actually I don't need so many profiles, the default profile is enough for me. sometimes I just want to import a keybinding settings from some one, and keep my other settings after I import it, WHAT HAPPEND!!!, all my other settings and extension are gone!!! This is unreasonable! what vscode should do is merging(or overwriting) new keybinding to my old one!! <!-- Describe the feature you'd like. --\nCan I have a try on this? I'm new to contributing to this repo but want to try out stuff and get along with starting out at the same time..\nEdit: Ignore this, I misread this with other issue\nJust wondering is not this same as Can you please distinguish your ask from the other?\npartially like But I request more flexibility: Suppose current profile is profile X (X can be default or user profile) when I import A profile, that will be: A.keybinding, A.UI, A.extensions ..... and I choose A.keybindings only to import what I expect: there are 2 options for user when importing: option 1 - merge to current profile, (so X profile's keybindings overwritten but other part of settings kept) option 2 - or create a new profile partially basing on what imported (this is what VSCode currently does )\n<!-- -96bd-47a8-a0e8- --This feature request is now a candidate for our backlog. The community has 60 days to the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our . Happy Coding!\n<!-- -c9e0-7adb-d31b- --:slightlysmilingface: 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 . Happy Coding!\n?"}
{"_id":"doc-en-vscode-93aa13d8e568229fb1193b976ecdf281af350a8ec7c2df5e0885ca5352b1991e","title":"","text":"I would think this is not a good one to start at and recommend to look for issues labelled with or\nI really want to try out.. just to experience and I think I would be able to do it. Even if it's not a good first issue I have contributed to other open source repos. Can I?\nSure, here is the starting point\nThanks a lot for this I was checking your PR with the user-profile feature implementation.. For now I'm just figuring out stuff that is already present. Just a single doubt that I had was about the merging of profiles.. would the editor be like a merge editor that opens whenever we get a merge conflict on git..? Or something else with checkboxes on which settings to get imported from each of the sides(current and imported one)? I'll try my best\nFor the sake of simplicity, during conflicts, I would simply override with the new one.\nAlso\nNote to self: see for manual workaround.\nYou can now import and replace any existing profile (including Default profile) from new Profiles Editor UI\nTo verify: Create a profile A and configure with some settings and extensions Export the profile A to the disk Change some settings and extensions in the profile Import the profile A You should be able to import the profile with name A replacing the existing profile\nWhen I export the profile, install some new extensions, then import the profile with the same name, I would expect the installed extensions to disappear from my extensions list, but that doesn't seem to be the case\nIt is working for me, ie., I only see the extension from the imported profile. After importing, extensions are getting replaced. Can you please share the exact steps to repro?\nUsing vscode 1.92.2, I can't figure out how to get to that UI. Where do I find it?\nsearch settings for \"profiles experimental\"\nThank you!"}
{"_id":"doc-en-vscode-c14140fb4c39db2744d4b9aab16bac1f4eba9257c730e8c405a10bf8062e4f68","title":"","text":"<!-- 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 VS Code Version: main branch () OS Version: any Sorting of suggestions is broken if the CompletionItem uses label details. When is a string, suggestions are sorted by label with ties broken by the completion item kind. But if is a then it is not sorted correctly. Here's the bug: This doesn't work as intended on objects. when and are both objects, these two comparisons BOTH return false and things end up being sorted only by kind. if one label is a string and the other is a , then the string ends up sorted after the no matter what the 's label is. Steps to Reproduce: a that returns something like this: end up sorted d, c, b, a, z but should be a, b, c, d, z\nThanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.68.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!\nfix is to use I think\nThanks This is a nice bug and good find. You did a great investigation, planning to fix this in this milestone but since you already did the lead work I'll happily review a PR from you\n<!-- 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!"}
{"_id":"doc-en-vscode-5b3e6aa093bee289b961b50fa528c6abdfd41e5785d6c94381dc5f507d5b48e5","title":"","text":"Open in two different tabs Make sure settings sync is OFF Change the theme in one tab Theme is not updated in other tab"}
{"_id":"doc-en-vscode-df4fc757c1179ef7f76458e88f4e644b031017c4b561154defbe154ad6682862","title":"","text":"New enum/select box detailed descriptions should be read by reader. Add describedby attribute handling for details provider within selectbox.\nEither describedby or just\nYep, I've thought about live/alert also. By my research this does not really match the expected taxonomy for the accessibility tree, an extended description is pretty much exactly what describedby is for. That said, describedby probably will not be happy changing which will mean I will need the static set of descriptions in the Dom. Not a big deal, just another example of where nothing is straightforward. But, that's why we get paid the big bucks ... well at least you :-o ! What I really want to solve is getting rid of the multiple 'clickable' readings. I think I may have a way to avoid that which will be very important for these descriptions given the number of links.\nGood point, I have no idea if pointing all of the selectbox items at the same details box will work, or if there's something we can do to order events to make it work better. Or maybe changing the 'id' of the details element for each item. I'm very curious what's causing that! Very weird.\ndescribedby can have a list of IDs associated with it. like labeled by and most other ARIA aspects it does not like things changing underneath it, that of course is what aria-live is for but, but everything I read says use this judiciously. I think having a separate set of descriptions (modified for reader output/minimal clickable) will not be a big deal. Just as the options are static, so are the descriptions so hiding them in the select for use will not be an issue. I haven't done the definitive experiment yet but, I believe the multiple clickable issue has to do with something like this: I think the reader can find these as all clickable elements when they are descendents of a managed accessibility tree. my research has yet to determine if this is considered a bug or as designed"}
{"_id":"doc-en-vscode-7fa68d19221ff045af1c5aa9d8b3db74a6d4dd1c12c70528d018407967ec821b","title":"","text":"Issue Type: <bBug</bI do not see the error or success icons for the gutter icon on my shell integration enabled terminals; instead it is always the empty circle. The integration appears to otherwise be working (the Go to Recent Directory and Run Recent Command commands are working as expected). I presume that somehow, the integration is not picking up the result of the operation being run. For reference, I am using but otherwise don't believe I have anything special in my Bash configuration that would affect this."}
{"_id":"doc-en-vscode-f4be82aa3b923ed28ed162a9b19ea2bbbea232634711e81e411a8478bf8cf92b","title":"","text":"VS Code version: Code 1.68.0 (Universal) (, 2022-06-08T11:44:00.250Z) OS version: Darwin x64 21.5.0 Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (76)</summaryExtensionVersion ------ Bookmarks13.3.0 project-manager12.6.0 vscode-sqlite0.14.1 atlascode2.10.12 github-markdown-preview0.3.0 jsdoc-markdown-highlighting0.0.1 markdown-checkbox0.3.2 markdown-emoji0.2.1 markdown-footnotes0.0.7 markdown-mermaid1.14.0 markdown-preview-github-styles1.0.1 markdown-yaml-preamble0.1.0 gitignore0.7.0 vscode-markdownlint0.47.0 vscode-eslint2.2.2 xml2.5.1 gitlens12.0.7 EditorConfig0.16.4 graphviz-preview1.5.0 flow-for-vscode2.1.0 vscode-mysql0.4.1 copilot1.28.6134 remotehub0.34.0 vscode-pull-request-github0.44.0 go0.33.1 todo-tree0.0.215 triggertaskonsave0.2.17 vscode-guid1.4.20 path-autocomplete1.19.1 tablegenerator1.0.4 plantuml2.17.2 svg1.4.18 docthis0.7.1 vscode-position1.1.2 yarn-lock-syntax0.1.3 Kotlin1.7.1 vscode-language-babel0.0.36 pull-request-quantifier0.1.2 extension-manifest-editor0.1.5 csharp1.25.0 dotnet-interactive-vscode1.0. network-edge-devtools1.0.0 data-workspace-vscode0.2.0 mssql1.14.2 sql-bindings-vscode0.1.0 sql-database-projects-vscode0.16.2 vscode-postgresql0.3.0 python2022.8.0 vscode-pylance2022.6.10 jupyter2022.5."}
{"_id":"doc-en-vscode-721bbb78324da1a9c4f12dee80e18aa64788c88b98ff9c40faa683962c3d9c8c","title":"","text":"jupyter-keymap1.0.0 jupyter-renderers1.0.8 hexeditor1.9.6 powershell2022.5.1 remote-repositories0.12.0 vscode-js-profile-flame1.0.2 vsliveshare1.0.5615 vsliveshare-pack0.4.0 resourcemonitor1.0.7 vscode-commons0.0.6 vscode-yaml1.8.0 sass-indented1.5.1 gitconfig2.0.1 mdx0.1.0 codevalet-vscode1.5.0 vcl0.1.2 msbuild-project-tools0.4.3 jest-snapshot-language-support1.1.1 intellicode-api-usage-examples0.1.1 vscodeintellicode1.2.21 vscode-icons11.12.0 quokka-vscode1.0.478 wallaby-vscode1.0.338 jinja0.0.8 ReactSnippets2.4.0 vscode-proto30.5.5 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nIt's working fine for me (I have the icon customized): <img width=\"447\" alt=\"Screen Shot 2022-06-10 at 11 29 56 am\" src=\"https://user-\"This is with a fresh install of stable bash-git-prompt Version: 1.69.0-insider Commit: Date: 2022-06-10T05:16:48.648Z Electron: 17.4.7 Chromium: 98.0.4758.141 16.13.0 V8: 9.8.177.13-electron.0 OS: Darwin x64 21.5.0 Could you see if it happens on the ?\nI am installing the Insiders build now. I will let you know.\nHmmm, doesn't seem to work. <img width=\"232\" alt=\"image\" src=\"https://user-\"\nHow does it detect the exit code? Perhaps I have something installed that is interfering, either in my bash config or elsewhere?\nYeah it's meant to change depending on the exit code of the program."}
{"_id":"doc-en-vscode-c8650865172e3091c5245f2d7148b80318807899e60c08bb5b08c3de8882817c","title":"","text":"Some info that would help us investigate: Set log level to debug via the command palette, then in Help Developer Tools console it will show some shell integration related logs when you run a command Do you set PROMPT_COMMAND anywhere? Do you use bash-preexec?\nI'll get this going and let you know. Ah yes, besides using , I have this in my bash config: I'll try disabling that and see what happens. It would be a shame to lose it but perhaps there's a better way of implementing that so that it's compatible, if that turns out to be the issue. Not that I am aware of, no.\nOK, so I disabled my PROMPT_COMMAND change and tried a few things in a new terminal that weren't working before. Now, when I use it is still an empty circle, but when I do , I get the green success lozenge!! So I'm guessing that was the main issue; though I do wonder if I should be seeing that green circle for and such too (that said, this is the non-Insiders build - I'll try Insiders in a second). I'll add the log level and see what I get.\nI can confirm that the Insiders build works as advertised now, so it was my history manipulation code that was getting in the way. Thank you for helping out. I'll close this issue as it appears to be an issue on my side, not yours. Thank you for helping troubleshoot.\nLet's keep this open to track the issue so we handle it better.\nwould you like me to gather the logging info as requested, since this is staying open?\nI think we understand the problem enough to reproduce it, it's just a case we need to detect and handle better.\nThis is happening because we actually depend on to differentiate regular commands that succeeded or failed vs ones exited via or running an empty line. Specifically this call: I'll disable shell integration if includes as that specifically is the reason it was failing.\n<!-- 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!"}
{"_id":"doc-en-vscode-c4863aa0b0f08c84d920342eddf78e82cd6a73fafa6fbc06f5c11f19ad00f0b6","title":"","text":"To verify: In set Enable the shell integration Open a terminal, it should not have shell integration enabled\n/verified I see that the integration is not enabled as the lozenges are missing."}
{"_id":"doc-en-vscode-5bf3acb9e94cb7fd11020fc1bf247774fb1a38fd79c7a8035ce2d9faccc83e88","title":"","text":"<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --The comments API doesn't have the concept of resolved/unresolved threads, although most code review tools distinguish them. The current API allows us to surface this to the users, see However, this seems pretty limited. I find it difficult to identify all my unresolved comments. It's very easy to miss some of them. If the API had a boolean for unresolved comments, we could surface them in multiple ways: In the Comments panel, surface the number of unresolved comments, similar to what is done with Problems: ! In the Comments panel, highlight the unresolved comments (or put them in bold), so that it's obvious to the user what comments they still have to go through. In the Comments panel, have a way to hide/filter the resolved comments. In the Editor, consider consider using a different background color for unresolved comments. I currently use a different label for unresolved comments, but this is very subtle. In the gutter, use a different symbol for unresolved comments (e.g. or a diamond of another color). In the Editor, provide a way to go to the next unresolved comment (an alternative to ).\nLet's discuss the API change. IMO, the information should be part of a . On many levels, Comments seem similar to s. A diagnostic is a comment provided by a tool such as a compiler. A comment is typically provided by a human. Diagnostics have a severity field, which indicates how important is the problem. We need an equivalent for Comments, something that tells the user if an action is expected (e.g. they need to resolve it) or not. Once the user addresses the comment, the importance is reduced. simplistic solution is to add a boolean, e.g. . to , we can go for a two-state enum instead: to be more general: . We might consider having more fields here. In a code review, multiple users interact with the comments. The current VSCode user is not necessarily the person who needs to do something. For example, the user has just updated the comment and they wait for a response."}
{"_id":"doc-en-vscode-ba281bfc6ad77598605e9d3947a685450f104ce7a7bb4f5783e821caa7680b8b","title":"","text":"So the third value could be used to mean \"it's not my turn\" or \"acknowledged, I'll come back later\". The benefit is that the user can use the list of \"unresolved\" issues as a TODO-list and publish the comments once it's empty.\nThank you very much for your proposal. and me have quickly discussed this and we believe this proposal makes good sense. We plan to start looking into it next milestone. Though no promises yet when this will land, we will know more in December when we start our investigation.\nAll of the proposals in have merit. In a perfect world I would choose one of options 2 or 4; however, we have users of the comments API who's comments don't have a resolved/unresolved state. Option 3 circumvents that, but then we have the issue of what to show in the UI: a GitHub PR comment isn't high or low priority. Another proposal, similar to how comment reactions work:\nI see than left comments on the commit (). I like the approach of having an object for the state (instead of the proposed boolean/enum), it gives more flexibility and lets user create their own states. In my proposal, the information was attached to a thread, not to a single comment. Do we have use-cases where we want this information per comment? We might also want to control the gutter icon:\nGitHub comments are resolved per-thread, so no, no cases were we want it per comment. I'll move it to the thread.\nAfter much discussion, we have decided to proceed with the following: The main reasoning behind this is that resolved vs. unresolved comments should look the same to the user across a GitHub PR extension, an Azure Dev Ops PR extensions, and any other PR extension. There original concern around using \"resolved\" and \"unresolved\" is that maybe not all comment provider have those states (maybe they have \"viewed\" and \"unviewed\" states for example). To alleviate this, we'll see if we can avoid using \"resolved\"/\"unresolved\" language in the UI. If additional states are needed later, we can always add more to the API.\nI have a basic implementation of this working, with and themable colors. Before I finish up the pull request to send it out, I was wondering what the best practice is for providing defaults for these colors?"}
{"_id":"doc-en-vscode-6a19f2593ef14e62ee675967386abd5dff47693300eb0317f8dd7b1a30ebe72b","title":"","text":"In the mocks from we use a yellow for unresolved comments that is inspired by visuals of our internal tool. I am not sure if they match an established VS Code palette.\nawesome, looking forward to reviewing it! Generally, we try to avoid introducing a new color entirely for something like this. The best practice would be to look through the existing color values where we use yellow then use the same yellow, just like is done here where uses the same color as : We'll also do a UX review of this, so the color may end up changing anyway.\nI went for new colors as the comments are conceptually something different than e.g. editor warnings. Currently the comments in the editor use (default blue), so a theme, an extension, or the users themselves would not be able to style comments independently of peek views. I think it makes sense to base the default on another color like as in your example, so that themes which omit the new colors receive a reasonable default, but it seems like we would give up a lot of flexibility and also clarity if comment widget colors directly used something like internally?\nYes, basing the color on another is what I meant! I agree that we don't want to directly use another theme color.\nIf anyone is eager for this API to be finalized then please comment and let me know how it's working for you. Otherwise, I will plan to finalize later in 2022.\nThis would be very nice to have. We are using Github and especially larger PRs are hard to manage, if there are many comments (in Github as well as in VSCode)\nSo is there currently a way to filter resolved/unresolved comments in the sidebar? If not what can I modify currently to provide a visual distinction between resolved/unresolved?\nthere's a color difference on the icon, but that's currently it. This is the feature request you're looking for"}
{"_id":"doc-en-vscode-e9246eac3587555dbd876ce8bd09a868f83fb7338c8d642293c42a06df7eba9d","title":"","text":"<!-- 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.33.1 OS Version: Windows_NT x64 10.0. Steps to Reproduce: a new user snippet file for the project. The one I encounter the issue with is: the snippet and attempt to press TAB after writing the first variable cursor does not move to the next stop, instead a tab character is The desired behavior would be for the cursor to move to the next tab stop. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes\nSeems to work just fine for me... Any special keybinding or setting? !\nThe action you took is not the problem I encounter and does indeed work the same way for me. Could you try to edit \"SystemName\", the first tab stop, then press TAB to go to \"Required Components\"? vsCode just inserts a tab character after whatever I wrote instead of going to the next tab stop.\nOk, thanks for clarifying. For some reason snippet mode stops when making that edit... Not sure why\nI have encountered similar issue, however, I could add a single blank space in the snippet which \"fixed\" the tab navigation. Also, my example is far simpler. See\nThis is a regression from I will revert that change and re-open the corresponding issue (which is much more rare than these issues)\nThank you for fixing this, looking forward to the next release."}
{"_id":"doc-en-vscode-a5709a82ab6ae7f22917a48052b76ff14904e9b0a3c2be8a67b1c4722b2fce53","title":"","text":"Version: 1.68.0-insider Commit: Date: 2022-06-02T05:17:01.962Z open the Settings JSON editor add some unnecessary commas no problems reported in the problems view. open the JSON Language Server log. Observe that there are no diagnostic requests. Other requests are sent and completed, so the language server is running.\nMaybe unrelated: I was expecting \"trailing comma\" warnings in (we recently changed the schema to not accept them), but they only started showing after I flushed the schema cache (using the UI command) and reloaded the window (I can't completely rule out that a window reload alone would have helped).\nI checked that with the fix the trailing commas are reported"}
{"_id":"doc-en-vscode-e719d7af96ec0d5310dd9fb7e82bd7c8f45aaf1e4fc5f4c542a75178c1728473","title":"","text":"Maybe you've already thought about this but it would be useful to be able to create a new folder in the simplified file dialog. This could be a button in the title bar or a confirmation step when a folder that doesn't exist was typed. Creating a folder and opening it, and creating a folder and saving a file in it, are common workflows so it would be useful to be able to do those in one step.\nFor the meantime:\nHey thanks for the mention! This was a feature I personally needed for quite some time - we all basically do those steps mentioned by on a daily basis so I decided to code an extension for it. Even though the extension already works great, I am actually working on it right now and adding a new feature which will allow it to create new folders using the Simple file dialogs - regardless of user setting, see . If anyone's interested, I think I'll manage to finish it by tomorrow.\nI've been busy with work and other projects but after a long wait, I worked really hard and managed to finish my npm module for Visual Studio Code that implements the aforementioned behavior and shows a custom QuickPick that allows browsing and creating folders from the Command Palette, even nested/recursive folders. The extension that implements this package is available at repo. Not perfect (yet) but it works.\nAlso create new file in Open File dialog would be useful.\nSaving is good. Opening hasn't been implemented -- should there be a new issue for that?"}
{"_id":"doc-en-vscode-c8001d4e038529068b27f5340405908be2010b37134b9cda546fa2310eb6a53f","title":"","text":"Testing settings UI for \" fontsize\" \"Show matching extensions\" blue button no it - no effect fyi !\nIt shouldn't show up when the filter is present, I guess"}
{"_id":"doc-en-vscode-9757ce4f0eafa1f3195b7e159960759be88311e44ed8cea74cb159b0b77bfdc2","title":"","text":"Testing an editor and write something in it. tab until you reach the terminal. Type something in the terminal. . Realize that tab is correctly not moving focus in the terminal. command \"Toggle Tab Key Moves Focus\" out of the terminal and keep tabbing until you get back to your editor. something in the editor. again until you reach the terminal. something in the terminal. to tab out of the terminal. It looks like tab moves focus as toggled itself off. Tab moves focus seems to be off for both terminal and editor at this point until reload.\nI can also cause similar behavior if I flip the settings.\nwhat is supposed to happen now? What I think I expect to happen (and isn't happening): If I run \"Toggle tab key moves focus\" while in a place where it doesn't move focus via setting, then it now globally moves focus. If I run \"Toggle tab key moves focus\" while in a place where it does move focus, then it now globally does not move focus. However, I'm not a \"tab moves focus\" user, so maybe my expectations are bogus.\nThank you for testing. Those expectations are correct, except that the toggling does not apply globally - it is per area. So, if I have in settings: terminal tab focus mode: on editor tab focus mode: off where: = status bar indicator = no status bar indicator focus the terminal focus the editor focus the terminal and toggle it off focus the editor and toggle it on focus the terminal focus the editor reload the window and focus the terminal focus the editor I see that this is not working atm because I'm not reacting to configuration changes\nfyi for easier testing since the command palette can cause the terminal to no longer be focused, I'd suggest using the keybinding to toggle tab focus mode"}
{"_id":"doc-en-vscode-d62a04551126810c7598750d024aceabedba11a6d3f3ea5c577752d6cd6f5882","title":"","text":"<!-- 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: 1.85.1 OS Version: Alpine 3.19 Steps to Reproduce: More info and fix in new version :"}
{"_id":"doc-en-vscode-1c40a0cf3bdc81282a1dcb9225acbbb5a49c262a89a85cc00736106739af6ed2","title":"","text":"<!-- 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.66.0 OS: MacOS Monterey 12.3, Darwin x64 21.4.0 Steps to Reproduce: new new markdown cell, name it for instance or will only show and have deleted the 1) or 1. written manually\ncc -- It looks like this is being sanitized out of md strings. A markdown cell containing will be sanitized to render as . If the cell contains it will render as expected, only removing the html tags. It seems to be happening at the following:"}
{"_id":"doc-en-vscode-829f1c987705c157c70eca0dfea30f232f6197c5800781b71e1bb8459a43983a","title":"","text":"As a result of the discussion in , we should format each command, description, and keybinding more consistently and limit redundancy.\n/closedWith though still need to do the same for the chat help dialogs"}
{"_id":"doc-en-vscode-5945adc82ea46a6840d24853134269e9a962daf2e57efa6253b924f294f1b397","title":"","text":"<!-- 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.51.1 / 1.52.0-insider OS Version: Ubuntu 20.04 / Windows 10 Steps to Reproduce: 4x spaces at the beginning of a line multiple cursors on that line enter Expected: Insert newline at each of the positions where cursor is present Actual Behavior: Inserts newline only at the first (NOT the left most) cursor position (Let me know the relevant settings values required) Addiditional info: I use tabs (width of 4 spaces) for indentation for formatting ! <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes\nI think this might be caused by one of your installed extensions. Here it is on my machine: ! To validate this, could you please : Run the command Developer: Toggle Keyboard Shortcuts Troubleshooting This will activate logging of dispatched keyboard shortcuts and will open an output panel with the corresponding log file. You can then press <kbdEnter</kbdand check what command is invoked. If you are having trouble understanding the output, please feel free to paste here and I can help decipher it for you.\nHere is the renderer keyboard troubleshoot log: Also, the I have disabled all the extensions. And, now, I can reproduce this with the latest stable too and in Ubuntu.\nIt is also not exclusive to the multi cursors created using keybinding. I can reproduce this by placing mulitple cursors created using the too.\nFrom the keyboard log, I can confirm that nobody is \"stealing\" Enter via keybindings. But there is another way that extensions can intercept that, via our command. That is the way in which intercepts Enter. Does this reproduce when disabling all extensions? Press and then choose !\nHey , In all of my previuos posts I have made sure that I have disabled all the extensions (by running the command that you have mentioned) and also, at the end of each of my posts I have explicitly stated that I had disabled the extensions. Can it have anything to do with my settings related to tabs?"}
{"_id":"doc-en-vscode-8e1d371e33668045a5c17ca5af854e518420eec385328f32d87d270ac5d271c8","title":"","text":"May be, inspect my settings here: (which has ) and, try to reproduce the issue by applying the exact same settings (copy paste my ).\nAlso, , Please carefully go through each of the above posts. It seems like you are not reading all the comments. It will save me from repeating the same thing again and again. Thanks.\nThank you for your patience, with your settings, I could finally reproduce. I missed the fact that the editor is configured to use tabs and I believed you might be using vim due to the block cursor in the GIF. You can workaround by using ."}
{"_id":"doc-en-vscode-5f7b980b13fbb6b3091dec63fb47cc5e48c4f099091ec48a8648508598944031","title":"","text":"Feature Request The command takes an extension argument so that extensions can open an issue reporter for that extension. I'd like to use this for the built-in JS/TS extension as well but cannot at the moment: It'd be nice if for VS Code builtin extensions, we automatically changed the field to\n<!-- -96bd-47a8-a0e8- --This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our . Happy Coding!"}
{"_id":"doc-en-vscode-927ec1e81507f8bfca9715bcdf396e91ff236eebc87d8e4e15d948b1a8ccccec","title":"","text":"I was trying to understand the usage of and the lifecycle of actions created while creating it. I think this originated with the terminal, so looked at the terminal code, but it seems like the problem isn't solved here either. instantiates some Actions which extend Disposable, but they are never tracked or disposed. The ActionViewItems returned from are apparently owned by whatever calls that and get disposed, but not these extra actions that we have to create. So, one solution would be for them to be owned and disposed by although that feels unexpected. But otherwise, there isn't a technically correct way for the code in to know when they should be disposed. Wondering whether I'm missing something or if you have any thoughts.\nI spent some time investigating this and the issue is that we use in some places and in others. Only the latter is disposable. This would be a bit involved to rework"}
{"_id":"doc-en-vscode-0c39d6703afbe94293f8cd25a0ee21e7a17bbae5cab85a68f1241cf3979c3a8b","title":"","text":"VSCode Version: 1.1.1 OS Version: Windows 7 x64 It would be great if holding the key + spinning the mouse wheel would increase / decrease the VS Code zoom value.\nI am not sure we want to zoom the entire UI when you use the mousewhell, I would expect only the editor font to increase. Thereby moving to\nyes you are correct.\nDidn't this feature used to work, or am I just failing to remember correctly? I was just going to report this as a bug, but maybe it never actually worked. I jump between different computer setups fairly regularly, so maybe I am just not remembering. Anyway, I found this dupe, and didn't want to submit a new issue. Thanks for your efforts By the way, I think I would expect this feature to work the same way that and work. VSCode's UI deviates from many other UIs in that it scales well, so I think I'd expect this to scale the entire UI consistently with the keyboard commands.\nIf this zooms only the editor, shouldn't it be seperate from ?\nI would expect and to zoom only the editor. That behaviour would be consistent with most (all?) other editors and apps. Scaling the entire interface is an accessibility feature IMO, so maybe it doesn't need to use such a commonly used shortcut by default? Beyond Ctrl+Wheel, pinch to zoom should also zoom the editor.\nCan this be disabled? I'm constantly accidentally zooming my text to a tiny size when I ctrl-click and accidentally brush my fingers over the trackpad.\nThis is disabled by default, so you must have enabled it in the past --\nThanks - I came here to vote for this feature, and it turns out I just had to turn it on! Shouldn't this issue be closed?\n:+1: Closing since this is implemented. The feature is disabled by default due to numerous issues reported by users using touchpads where we begin to unexpectedly zoom in/zoom out when e.g. using ballistic scrolling and pressing the ctrl/cmd modifier. The root problem is that we cannot differentiate events coming in from a real mouse with a wheel from those coming in from touchpads / trackpads."}
{"_id":"doc-en-vscode-3827f05d231ae0d4132032e8528b92eefcc8109004cc4f4882d761ae97dce73e","title":"","text":"<!-- 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.90.1 x64 OS Version: Ubuntu 24.04 (Updates 14 Jun 2024) I get the error on a fresh installation of Ubuntu 24.04 and VSCode 1.90.1 Everything works fine with VSCode version . Steps to Reproduce: latest version of Ubuntu 24.04. command. command.\nIn my case the issue occurred when doing , also on Ubuntu (20.04) and also on vscode 1.90.1 Here is a temp workaround to revert to vscode 1.89.1, if that's useful to anyone:\nHi Having same issue on remote VM Ubuntu 20.04 Install errors with Solved by using the flag"}
{"_id":"doc-en-vscode-c570bae3509eccf5e35209355526fe5d2cf34df8130f0cae65aa7851cd0ac83f","title":"","text":"This is a continuation of to implement a proper fix in the runtime or application as necessary. Known data points: SIGTRAP when gpu tried to access resource bundle to load a label for assigning display name when computing vsync interval using the internal implementation rather than the gl extension. Also name from resource bundle is only requested for builtin-displays and not virtual ;l=449-456 Using gpu codepath from main process serves as a workaround. Debian package on the same system didn't trigger the crash codepath, very likely a different gl backend was used. Next steps: 1) Compare gl initialization trace between snap 1.89 and 1.90, using the following categories 2) Compare gl initialization trace between debian 1.90 and snap 1.90 3) Confirm if resource bundle access from gpu process is necessary moving forward.\nThis turned out to be a regression from https://chromium- which causes the gpu process when using the software display compositor to reach into the resource bundle. Before the CL, gpu process will not call into only the main process did.\nis there something to verify here?\nThis is related to the candidate issue and I was just using it to track fixes. Nothing particular to verify for this particular issue, maybe confirm the checksums for both branches are same vs"}
{"_id":"doc-en-vscode-03b1fe8bcc7a333143d99c26fbc0c53daf9478b0f032523dd82915db005133c3","title":"","text":"Ideas to experiment with: Don't shrink a cell while it is executing -less jumpy as output is replaced change the anchor heuristic from \"if the resizing cell is partially visible\" to \"if the cell's output will shrink out of view\" Anchor to a focused cell if the focus is in the cell's editor cc\nFor the new heuristics we are adding (growing upwards or downwards), they should probably be interrupted the moment users start to scroll, for example, if I scroll manually to a specific position, I would expect the scroll top not to change.\nI disagree - That could mean if you have a cell focused and anchored, and you scroll to get it higher in the view, it would then start getting pushed down as the previous cell grows.\nIf I scroll to get it lower in the view, as I want to read the cells above, and since it's still in the view and focused/anchored, the cells I was reading will then pushed upwards, right? This feels unnatural compared to how browser handles scrolling or Terminal. Terminal scenario might be closer to this, as it usually sticks to the bottom when the shell is streaming outputs, but the very moment we scroll upwards, it stops sticking to the bottom."}
{"_id":"doc-en-vscode-ee4509bc45987ce1b50b7b4e26dce42aa20015441e41a6672f878065dcb175ab","title":"","text":"Select a portion of a variable name Press F2 Previously, the rename widget would open with the same substring highlighted. It's helpful to quickly rename one subword in a variable name, for example. Now, the full contents of the input in the rename widget are highlighted initially. I don't know who owns this but it looks like you touched it recently\n<!-- 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!"}
{"_id":"doc-en-vscode-606eed8ee8b9e65a645014c78f91e6a3ff9288fe43fdda2392d5ef177310ce71","title":"","text":"Issue Type: <bBug</bLike what the heading says, inserting a code snippet anywhere in the code file causes an autoscroll. This is a slight inconvenience, as while inserting snippets, viewing code above it is desirable, causing us to rescroll into view. So adding an option to revert to the functionality in the stable release would be preferred VS Code version: Code - Insiders 1.46.0-insider (, 2020-05-07T16:36:39.681Z) OS version: Linux x64 5.4.38-1-MANJARO <details<summarySystem Info</summary </details<details<summaryExtensions (4)</summaryExtensionVersion ------ cpptools0.27.1 Go0.14.1 material-icon-theme4.1.0 material-theme3.5.0 (1 theme extensions excluded) </details<!-- generated by issue reporter --\nYeah - that's a regression from a recent change to keep the position stable when additional edits are inserted...\nis the item that caused this regression.\nfixed via\nYep, it works fine now. Thanks a lot!\nThis bug has been fixed in to 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 pallette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!\n/verified"}
{"_id":"doc-en-vscode-d7b354ec7fa8570ede0c28ed32626293898215fc66c30a1628fd1843dfed3226","title":"","text":"This is somewhat the opposite of and the acknowledgement that computing additional text edits for all items upfront is too demanding. This issue is only about and the goal is a pragmatic solution, similar to the one that we have for . Idea accept an unresolved completion proceed with insertion as usual set up a content change listener resolve the items once resolved check if additional edits overlap with \"concurrent\" changes. when they overlap, do nothing otherwise proceed\nThe first version for this is now merged to master, it's a pragmatic approach that's better then not resolving but worst than (costly) upfront resolving. Items to followup on [ ] telemetry and follow up issues [ ] - TS issue for having incomplete items [ ] [ ] java for returning very few (resolved) completions, e.g doing the right thing\n/cc - My understanding is that Java resolves all items upfront, e.g compute additional text edits during \"provide\", and that it is quite expensive and therefore Java only returns a small amount of items. Is that correct? Could Java return results faster when additional text edits are computed during resolve (and therefore only for selected items)?\nYes. I think so! is the dev who was working on Java completion. I believe he can provide more insights toward this topic. // cc\nthis is exactly the behavior that used to have, ie compute all the completion items first (fast), then the text edits were computed during resolveCompletion. We were asked to not do that as and changed to return a small subset of completion items (with incomplete=true), with full text edits computed upfront. The user experience is definitely not as good as with our initial implementation.\nTo be clear, computing any Java textedit upfront is costly when returning 100+ items (and we can return several thousands items). We'd prefer if the async insertion of textedits covered all textedits, not just the additional ones.\nThe requirements discussed in are still true and there are no plans to change that. There is (which might be derived from ) and . The former () is inserted at the cursor and must be inserted synchronous to accepting a completion (we cannot block typing while waiting for that). The latter () is meant for things like import-statements and we now want to relax that, e.g it can come late and we try to apply those edits despite the user having typed more."}
{"_id":"doc-en-vscode-0c857242b34ed52dce7088938c65190f31b9116d903528ce4038c3ec897d183f","title":"","text":"When exactly does run, is it only when an item gets highlighted in the menu? Can't tell from the docs. I only need to generate for the completion item the user ends up applying -- doing it for other items is unnecessary work that's bogging down the extension host, and I will have to implement yielding. I assume no one would need to generate before a completion item is applied? Is there any kind of completion applied event we can hook into to work around this for the time being?\nThat's exactly what is about . Today, there is no guarantee that is ever called because its original design is to provide data for the suggest details widget. However, we see that (amongst other things) are computed during resolve and leads to subtle bugs (because don't always call resolve or always await it) Well, is the problem if you do not generate them upfront. select suggestion synchronously inserts the string starts for additional text edits continues to type quickly and all over the place -call eventually returns but it is unclear if the edits are still valid because the state changed many types in-between Solutions: Won't work because in JS you cannot wait for another \"thread\" or \"process\", the world always keeps turning Implement a full -solution because this is two entities \"typing\" concurrently in the same document. However, it will feel awkward because the user doesn't expect to be such a scenario. approach that tries to apply additional edits if possible but inserts the \"main edit\" (insertText) always synchronously. () \"if possible\" is currently defined as \"no edit has occurred before the first additional edit\". That works well if you use additional edits for things like imports or prefixes (which is the indented use-case) but won't work if additional text edits change the main edit, like appending a call-operators with arguments etc\nI mean JS can't block but ignoring typing while awaiting is possible -- I was imagining that VSCode would keep the completions menu open and ignore any typing until is resolved and all text edits applied for the accepted item. Obviously this would be bad if resolving takes a long time, but the API has cancelation tokens already, so the UI would just need to show a spinner/cancel icon, and also cancel if the user presses ESC or navigates to a different editor, for a decent UX."}
{"_id":"doc-en-vscode-2115e438de866f42a904232f44db2cb525c2f89c929b8454bab42979e5b6c771","title":"","text":"I think this would be less confusing for users too; it's the only way it would be clear when VSCode is completely done applying the completion. I think many users would be confused if imports usually get but not when they resume typing too soon. FWIW I can syncronously generate the additional text edits I need, so I'd be happy if there were an API to synchronously generate them when the completion item is accepted. I know not everyone would be able to generate them sync though.\nAlso I know my questions may have seemed redundant, but I hadn't seen anyone on this thread point out that it would be ideal to avoid ever computing additional text edits (or even the primary insert text) for unselected completions. Since can get called before any item is accepted (I assume, since it seems to be for showing additional details in the menu), I'd think any solution via could still result in unnecessarily generating additional edits that are ultimately discarded.\nThe golden rule is that \"you can always type inside the editor\". Ignoring typing is not a good solution and will bug users. Just think of quick suggest and auto accept characters - you don't want the editor to stop typing just because an extension is taking a little longer (+50ms). To be precise you should have written \"typing at or before the offset at which additional edits are going to happen\" I honestly think the majority can generate them synchronously but this happens in the extension host process or the language server process, and all of that might happen on a different machine and there is no way to synchronously transport that into the UI.\nre with the current changes you should be able to have a \"simple insert text\", say , and compute an additional text edit, like , that goes in front of it so that you eventually have . Right? Or am I missing something?\nthat might actually be a good idea ;-) In practice though, we might need to revisit the way the principal TextEdit is computed (i.e rewrite a bunch of stuff from upstream JDT)\nI get the desire to be able to always be able to type inside the editor and agree that's an important principle. The only reason I think this case is an exception is that: The user would probably want to wait for all edits to get applied anyway."}
{"_id":"doc-en-vscode-9132fa71eb633d21971640f1bb980a8874af30dfb4158c01fa6bf6c11edd4ff5","title":"","text":"Seems unlikely that people would want to get the main edit without the additional edits By making the operation cancelable, you can still go back to typing immediately if you so desire. I certainly wouldn't want to block the user from typing without recourse (as you know, I feel frustrated that happens currently when using Vim extensions) On the other hand, I guess it's unlikely that the additional text edits would overlap whatever the user continues typing...\nI hadn't thought about auto accept characters though, that's a good point. That's something I don't have experience with. Also considering that VSCode could pop up a warning if it has to bail on inserting additional edits, it's not a big deal if it ever happens\nI remember that we have some new data points regarding the time consumption in different stages of code completion in Can you share that data and see how we can tune it with this change?\nFor Java language server, below is a sample of call tree when triggering completion. (time value is larger than expected because of extra overhead from JProfiler) ! Total time of completion stage mainly consists of three parts: competion candidates in JDT to CompletionItems (calc textEdits, additionalTextEdits, etc.) --- calc an incomplete list of only 50 items by default (the full list can contain thousands) --- here calculating import statements costs a lot of time server-side code snippets (not much related to this topic) I did a simple experiment on java language server, with vscode-insider built on 2020-5-15. I was using spring-petclinic, which is not a big one, but with some dependencies. Type a initial letter, e.g. \"O\", and observe perf of completion and resolve. Do multiple times for statistics. Calculating additionalTextEdits async in resolve stage does decrease the time cost a lot. textEdits and additionalTextEdits are calculated during completion stage. completion: ~150 ms resolve(avg of top 10 items): ~10 ms Now I simply move a bunch of textedit calculation from \"completion\" stage into \"resolve\" stage. completion: ~100 ms resolve(avg of top 10 items): ~17 ms !\nI just realized that can return a thenable, but I assume that would delay the appearance of the entire menu?\nClosing as we haven't seen issues with the new pragmatic approach and the plan is to stick with it."}
{"_id":"doc-en-vscode-21ea23a5ea1f6e51db21a54f4e89f11ae1eea99cf83c8c7baa4d9b8cad491b1b","title":"","text":"so how do servers know that clients support lazy-loading of additional textedits? Surely this should be a client capability advertised by vscode (that needs to be specced in the LSP)\nis the right person for that and you should probably create a follow up issue in the LSP land\ncorresponding LSP feature request created here please add more details if I miss anything.\nThanks\nTo verify: use TypeScript have a suggestion that will import a symbol make sure that suggestion isn't first or focused in the UI use the mouse(!) to select the suggestion make sure the import is there make sure undo, redo works as expected"}
{"_id":"doc-en-vscode-59e4ba98548ad395ffe499e1b73c7b92fe1d12051c0abe95a4a282e47cc81736","title":"","text":"Type: <bBug</bDelete a notebook file in a git repo Open it from the SCM view It's editable ;( VS Code version: Code - Insiders 1.94.0-insider (Universal) (, 2024-09-11T05:04:03.124Z) OS version: Darwin arm64 23.6.0 Modes: <!-- generated by issue reporter --\nFixed by"}
{"_id":"doc-en-vscode-3c9c77bd94452d2756eabf856a0467e8375b8054f2a5b186326ef05028068560","title":"","text":"I've had an SSH window open in the background and noticed that it keeps going through reconnection. Looking at the logs, it looks like vscode is often triggering reconnection, even though nothing strange is going on with my network, as far as I know. Noticed this at home and also the office network. This is the log from vscode. The SSH log doesn't show anything unusual before the resolver is invoked again. Has anything changed here lately?\nSorry this issue fell through the cracks. Are you still running into this?\nYes\nDo you perhaps have a log with tracing enabled? The reason in the original log appears to be timeout. That is triggered here -- So the conditions are: a message was written to the socket 20 seconds ago and the server side didn't acknowledge it (and) no data was received from the server within the past 20 seconds (and) no previous timeout event was fired within the past 20 seconds (this just avoid sending many timeout events) (and) the renderer process appears responsive (Just speculating) I think we have fixed something in the terminal land and we now no longer send any data in an idle window. Could it be that your window becomes idle and the connection is dropped by SSH? (I believe due to some terminal heartbeat mechanism there was always data being written every 5 seconds, but now that is no longer happening).\nWell, now I can't repro it.\nI've more logging via . Please keep an eye out. In case you hit this again, the logging will have more data.\nThis issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!\nFinally got it\nIt seems like the log message you touch didn't show up there. But, it does show up in an earlier reconnection in this window (before I enabled trace logging). So I'll just share the full logs This shows a window that was mostly idle with 2 reconnections, the second one had logging at the trace level enabled\nHere's my interpretation: the management connection timed out at due to our own timeout logic. We wrote one message and that message didn't get acknowledged within 20s by the server. As an observation, the connection didn't receive any bytes from the server within 320s (5 minutes)."}
{"_id":"doc-en-vscode-10055c408e7ac3d25e8587c718a04c9bae2bdb97241e19f9ef42b6f49d9b245b","title":"","text":"this resulted in the core invoking on the SSH extension and the SSH extension replied with a new port i.e. instead of the previous . the extension host connection immediately closed at with code , indicating that perhaps the previous tunnel at was killed as part of invoking . Precisely 20 minutes later, at , both management and extension host connections receive a event from Chromium. I can't quite explain the first timeout, why would the server not acknowledge a message within 20 seconds? But the timing of the second disconnection seems to indicate to me that after 20 min of idleness, the underlying connection is closed. Anyone could be closing it: either on the client side by Chromium or the OS, either on the server side by nodejs or the OS, either by the SSH tunnel timing out. For the second disconnection I think we might need to do something to tackle . For a long time the terminal was doing a heartbeat mechanism which resulted in data being sent over the wire (and that would not make the connection idle), but that was fixed via Right now, if you are really idle in a window, the underlying connection will be idle too and I think the OS or someone closes it as idle after 20 minutes.\nMy best guess is some other weird optimization where network requests don't even get delivered when an app is in the background. I've noticed this in windows that are not focused\nThis issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!"}
{"_id":"doc-en-vscode-2644b9d156959c9ddecca9656eb5f1d3eadd7846b1640a21d8242e97d2495e54","title":"","text":"<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --We already have this feature in Core: where you can return where . Truth be told, this already works in API today though it's not officially a part of the API today (so it could change at any moment). For example, I can do: <img width=\"738\" alt=\"image\" src=\"https://user-\"with it goes from: to it goes from: to\nref\nCreated a TPI so moving this to April for Finalization."}
{"_id":"doc-en-vscode-63f72f6f8e2918e6b94eaa223c02ed860a95b19d86c4220f6ad5054288061d6c","title":"","text":"Currently, the editor does not support customizing file labels in a way that would allow filenames to be prefixed with the name of the application or folder from the start of the path. This limitation affects projects structured in a monorepo setup, particularly when files are deeply nested within application-specific directories. Supporting negative indices for could solve this problem. This would enable accessing folder names starting from the beginning of the path. Implementing negative indices would cater to the needs of projects with files at various nesting levels within their structure.\nIs the reasoning not the other way round or am I misunderstanding how it currently works? E.g. I'd like to access last 2 parts of the path, but the description of the settings suggests that only the single final and the starting folders can be accessed.\nFor the following path you will get the following values: Path: : : : : With negative indices: : : :\nHere is an example of the mono repo: It has a root and multiple projects in the folder. It is common to make changes in multiple \"packages\" at once, and it would be convenient if we could identify files by the . Example: -\nVerification steps: a custom editor label. The template should include , for which is a negative number. For example, add in , item: value: a file which matches the pattern specified in step 1. For the example specified in step 1: every file matches the pattern editor tab should have set the correct folder name for . Here an explanation on how negative indices work: For the example specified in step 1: the name of the editor in the tab should start with the top level folder the file is located in. In the vscode repo the file would have the custom name\nI have followed the steps for the verification and the settings file is renamed to . The TS files are renamed correctly to . Is this expected?"}
{"_id":"doc-en-vscode-8b4efaf11aeebf34b8089b02e11c35d044aa38b53bca3976566eea8a7ca6b82b","title":"","text":"On Safari/Codespace Open a notebook Open settings Switch to notebook Press enter https://user-"}
{"_id":"doc-en-vscode-b65acd42f1a30362bf251165c7735bc08e6d321059eabf6b00274cfd84a629e6","title":"","text":"a JS file: to definition on Bug I see this scary notification: <img width=\"671\" alt=\"Screen Shot 2022-07-26 at 2 31 10 PM\" src=\"https://user-\"In this case, the user was likely just trying to view the file Would it be possible to either: show this notification when saving? open these file as ?\nThis came in via from and I think is not good. This also reminds me that when debugging you may end up in a file from the installation dir. I think we should probably revert the change for now and think about a better solution unless there are objections.\nI agree. Maybe pursue your earlier suggestion of opening all installation directory files in readonly mode. Perhaps combine with a scary warning if you save a new file in there."}
{"_id":"doc-en-vscode-4c9ff479c62adbd9ab836e62209b1c6784c0dabbb48a7c055b56d80c4cc856f7","title":"","text":"We very likely do not need to ship all of this in the web bits: This was already once done before in , and when dependencies got renamed this was once again forgotten about."}
{"_id":"doc-en-vscode-f90f776042f4d21ac199c4bcf231e859b273ffa5ca7f5c0c37d08c204c3e4984","title":"","text":"Issue Type: <bBug</bdeveloper tools themes Everything appears to work as normal, but the console gets flooded with errors. VS Code version: Code - Insiders 1.36.0-insider (, 2019-06-14T10:36:51.530Z) OS version: Darwin x64 18.6.0 <details<summarySystem Info</summary </details<details<summaryExtensions (13)</summaryExtensionVersion ------ vscode-eslint1.9.0 gitlens9.8.2 vsc-material-theme2.9.0 remote-containers0.61.0 remote-ssh-edit-nightly2019.6. remote-ssh-explorer-nightly2019.6. remote-ssh-nightly2019.6. vscode-typescript-tslint-plugin1.1.0 debugger-for-chrome4.11.3 vscode-docker0.6.2 material-icon-theme3.8.0 polacode0.3.2 vscode-sort-json1.13.0 </details<!-- generated by issue reporter --\nI can't repo this. Which developer tools and theme are you talking about specifically?\nI tried repoing this again and it appears that this error is related to installing a new theme. Here are some better repo steps: developer tools themes (no errors) a theme themes (errors even if it is one of the themes shipped with VS code) The errors go away after a reload, but installing a theme does not tell me a reload is required.\nOk, with the extensions view open, I sometimes see Does not cause seem to cause any actual problems\nI get that as well sometimes, but do you not get the webview must be attached to the DOM error as well?\nI can reproduce it. Steps: on any extension to load it's Readme in an editor that editor theme (this triggers the webview error) step 1 (this triggers the guestInstanceId error)"}
{"_id":"doc-en-vscode-dc6f11946a72c1ad191104d72658607f62d2fead0e2b3ee4b7457568823792ab","title":"","text":"Issue Type: <bBug</bkeyboard shortcuts for \"npm.packageManager\" ! VS Code version: Code - Insiders 1.62.0-insider (, 2021-10-11T05:16:36.885Z) OS version: WindowsNT x64 10.0. Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (26)</summaryExtensionVersion ------ vscode-javascript-repl0.7.2 Bookmarks13.2.2 gitlens11.6.1 copilot-nightly1.5.3048 remotehub0.15.0 rest-client0.24.5 monkey-patch0.1.15 search-node-modules1.3.0 vscode-docker1.17.0 vscode-edge-devtools1.3.1 remote-containers0.202.1 remote-ssh-edit-nightly2021.10.5220 remote-ssh-nightly2021.10.5220 remote-wsl0.58.2 hexeditor1.8.2 js-debug-nightly2021.10.817 vscode-typescript-next4.5. debugger-for-edge1.0.15 vetur0.34.1 explorer-exclude-vscode-extension1.2.0 reveal1.2.7 luna-paint0.10.0 vscode-icons11.6.0 cloudmusic9.2.4 markdown-all-in-one3.4.0 material-theme3.13.2 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --"}
{"_id":"doc-en-vscode-f88af50c1e8f723b0a06895f76c481de98fcd6e41ee09bbcaf0450589605cad6","title":"","text":"We have the ability to select which branch to push to in the source control, could we please have a pull from option? To target specific branches. Unless it exists already? I have only recently started using VS Code and i love it!\nThis is an easy contribution, care to submit a PR? PS: You currently have the ability to select which remote to push to, not which branch.\nI'll take on this. Is it correct that branch names are not stored anywhere? I've checked in and cannot find anywhere they could be stored. If there is nothing, I'll just take a user input using showInputBox.\nI created a pull request for this: Please take a look when you have the chance.\nmerge conflict is fixed.\nMerging with"}
{"_id":"doc-en-vscode-de13733ea68fa91bddf27830fd5bdb3f418c008d6b746dfb6aced09f067a0504","title":"","text":"VS Code 1.46 start VS Code Stable use this launch config: close \"\" editor run it Observe: (everything is good) <img width=\"749\" alt=\"2020-06-1609-34-37\" src=\"https://user-\"- shutdown VS Code open same project with VS Code Insiders (or any other editor) modify \"\" and include argument \"1234\" between \"hello\" and \"world\" shutdown VS Code Insiders launch VS Code Stable again go to debug view and run \"echo args\" launch config open Observe: <img width=\"1080\" alt=\"2020-06-1609-39-11\" src=\"https://user-\"VS Code runs old launch config which lacks the \"1234\". Workaround: an edit change of is needed before VS Code will run the correct launch config.\nWe no longer store the configuration in storage. The only downside is that now when you select a dynamic configuration, reload, we do not preserve the dynamic configuratoin and you have to select it again. For that we would have to store the \"origin\" as you suggested, but that I will tackle as a seperate issue, thus reopening\nI've verified that no stale launch configs are run."}
{"_id":"doc-en-vscode-0a684b4e4d880d4d5f4a1511affe0ce4e748d0525514e9c2a1d1318120d0c249","title":"","text":"is used in the inline chat widget to accept a suggestion is used in the accessible view to accept an inline completion suggestion There is no keybinding to insert the current chat code block suggestion at the current cursor location is used to submit a comment from within a comment widget suggested aligning these. what do you think of adding a default keybinding of for inserting the current chat code block at the current cursor location? I will change the inline completion suggestion acceptance in the accessible view to .\n-- Did you mean ? I think can be used for submission. There is no issue with this key. Submitting pull request, for example, is also . However, when Accepting something, we may want to use for the consistency.\nI was suggesting we align all of these to use rather than .\nI don't think people will be in favor of to accept in the inline chat widget as that would break muscle memory.\n-- FYI, the following keybinding is also :\nI've refined the original content of this issue to reflect the ask. We shall see what people say.\nHere is my summary: for submitting actions. Evidence: GitHub Pull Request uses this keybinding. Also, \"Report Issue\" under Help menu also adopts as its default keybinding for submitting issue content. for accepting or inserting suggestions. Evidence: already uses this keybinding. Also, Accessible View adapted this for accepting the current inline suggestion.\nI think that's not a good keybinding and that Ctrl+Enter is way better because it's easier to reach, e.g on a DE/CH keyboard you need to press Shift+7 to get /\nI am then not against unifying all the listed keybindings in favor of .\nTo verify: Focus an editor Enable screen reader mode Focus a chat code block Use and verify that the code is inserted in the editor at the current cursor position"}
{"_id":"doc-en-vscode-77a03d3a5b1d1cf3cfa64ddc6224b6d7c8b7c3c0302ae63925b2a066129033e7","title":"","text":"<!-- 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: up a keybinding to launch quick text search a diff editor some text quick text search Nothing in input: ! Expected: !\nHi , I guess the PR has fixed this already. I tried reproducing it locally with the changes of my current PR, and it seems to be working fine. Attaching the screen recording for your reference.\nYou need to open a diff editor. For example: open a folder that is a git repo Make a change in any file Go to the source control viewlet and click on the changed file: <img width=\"1679\" alt=\"Screenshot 2023-10-08 at 2 57 57 PM\" src=\"\"Select text in the right editor The bug appears.\nGot it, will try to correct it\nHi , I understand that you must be busy. Can you take a look any time you are available? I need some help in figuring out where exactly the diff editor is interacting with search bindings. For example, I am not able to understand how hitting cmd+f calls the search function from the diff, or where it is getting called from. Similarly for the quickTextSearch, can you point me in the right direction?\nI was looking for code pointers and ended up finding the bug anyways:"}
{"_id":"doc-en-vscode-dda74c37533ada43042df8302e3249fa659295e4ce7625b66af7efdd86c8709b","title":"","text":"Version: 1.94.0-insider Commit: Date: 2024-09-23T05:12:01.964Z Electron: 30.5.0 ElectronBuildId: Chromium: 124.0.6367.243 20.16.0 V8: 12.4.254.20-electron.0 OS: Darwin arm64 22.6.0 Steps to Reproduce: a very long line. Google IME for Japanese. at the last of the long line. position of the IME widget is not optimal. ! With , it is worse. !\nHi yes thanks a lot for opening this valuable issue. This is happening because we use the model ranges instead of the view ranges in the control bounds, selection bounds and character bounds positioning. The following PR fixes this:\nI try the OSS version from the repository. The issue with is fixed. However, I still see the issue with Version: 1.94.0 Commit: Date: Unknown Electron: 30.5.1 ElectronBuildId: undefined Chromium: 124.0.6367.243 20.16.0 V8: 12.4.254.20-electron.0 OS: Darwin arm64 22.6.0 a very long line. Google IME for Japanese. at the last of the long line. position of the IME widget is not optimal. !\nOh I see thanks for letting me know that is curious. I will reopen the issue and have a look.\nAfter investigating the issue, I believe this happens because I didn't remove the editor scroll left position from the bounds set for the selection and character bounds. The following PR should fix this."}
{"_id":"doc-en-vscode-8404759e1ee656aabe1521fde11f0dde83c16e2853a3f19c37954d313040e76e","title":"","text":"<!-- 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. --I'm currently implementing hit conditions in vscode-php-debug. Xdebug has very limited conditions it supports and we need to signal the user if they typed something unsupported. If a breakpoint has such a condition we try to return that in the field in the setBreakpointResponse/body/breakpoints. There is the implementation line: I noticed that the message is only visible when hovering with the mouse over the unverified breakpoint and only when the DAP isn't in a running state. If the adapter is in a breakpoint, there is no indication why this breakpoint isn't valid. Steps to Reproduce: and build vscode-php-debug from branch . a PHP debug Optionally add under setting. a breakpoint with hit condition \"blabla\". breakpoint should be unverified, hovering over it should show the message. Messages exchanged until now: launchResponse initializedEvent setBreakpointsRequest (see full message below) setBreakpointsResponse setFunctionBreakpointsRequest setFunctionBreakpointsResponse setExceptionBreakpointsRequest setExceptionBreakpointsResponse configurationDoneRequest configurationDoneResponse threadsRequest threadsResponse () a PHP process that will cause the debug adapter to move into running state. Following messages will be exchanged: ThreadEvent () StoppedEvent () threadsRequest threadsResponse () stackTraceRequest stackTraceResponse threadsRequest threadsResponse () scopesRequest scopesResponse variablesRequest variablesResponse this point hovering over the unverified breakpoint will not show the message."}
{"_id":"doc-en-vscode-24b09d5016e336a720eabbd4b0ef58e4836b748c1c7dbf743fe7434e55a13585","title":"","text":"Full breakpoint messages Version: 1.59.0 (user setup) Commit: Date: 2021-08-04T23:13:12.822Z Electron: 13.1.7 Chrome: 91.0.4472.124 14.16.0 V8: 9.1.269.36-electron.0 OS: Windows_NT x64 10.0. Full log of message exchange (DAP and Xdebug)\nMaybe a good issue to get introduced to the breakpoint message computation. Thus assigning to Code pointer where we compute breakpoint messages There is probably some check wrong depending on the debug state.\nAny luck looking into this? I just want to check if there is something I did wrong before releasing. Btw: Is there any way to enable DAP logging of node/typescript adapter so I can compare messages?\nwe just did not have a chance to look into this yet. will probably look into it soon, if he is busy I can also help. Yes, it is possible to enable DAP logging for js-debug. Add to your and start debugging. The location of the log file on your disk will be written to the Debug Console. That log file should have the communication.\nI totally lost this one, and it's fairly straightforward. This is due to us disabling editor hover in favor of the custom debug hover.\n<!-- 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!"}
{"_id":"doc-en-vscode-b1d143f38f5b392a6931ed685b51b034e2a9026227e850c8a5c1460223b61404","title":"","text":"Steps to Reproduce: recently opened (\"Clear Editor History\") quick open and search for a file (such as a TS file) to see symbols (notice how the file opens in the background) to a symbol = when you open quick open again, the file is not part of the recently opened section //cc this is a regression from the transient work we did"}
{"_id":"doc-en-vscode-736e5dacce23e50e1645834292698b90ac492d0487cce5f095aee4c19a0dc8c2","title":"","text":"Type: <bBug</b<!-- Please fill in all XXX markers --Python Debug Console shows \"Shell integration failed to activate\" ! a Python file command over terminal with mouse <!-- After creating the issue on GitHub, you can add screenshots and GIFs of what is happening. Consider tools like , or for GIF creation. --<!-- NOTE: Everything below except Python output panel is auto-generated; no editing required. Please do provide Python output panel. --- Python version (& distribution if applicable, e.g. Anaconda): 3.10.5 Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Poetry Value of the setting: Default <details<summaryOutput for <codePython</codein the <codeOutput</codepanel (<codeView</code→<codeOutput</code, change the drop-down the upper-right of the <codeOutput</codepanel to <codePython</code) </summary<p</p</details<details<summaryUser Settings</summary<p</p</detailsExtension version: 2022.12.0 VS Code version: Code 1.70.1 (, 2022-08-10T06:08:33.642Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nSame problem here\nSame.\nVS Code creates this terminal as a part of the request that gets sent over DAP. It seems like it is failing when VS code tries to create the terminal, moving this there for further investigation.\nwhat needs to be done here for correct activation?\nThis issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!\nCan you elaborate why this ticket was closed? The issue is still there.\nwhat needs to be done in order to prevent the \"Shell integration\" from failing? \nIf run in terminal replaces the shell args then this warning shouldn't be showing (as shell integration should be disabled). It does works in the JS debug terminal which is a terminal profile that sets an environment. If the terminal is launched without args this would be an issue on the terminal. how do I create a python debug console?"}
{"_id":"doc-en-vscode-fc614aff5704f53fa1bf44a3c73448d15b21e3b35eb624b45b1052368327b5fa","title":"","text":"in a Python file the \"Debug Python File\" action from the editor drop down opens a python debug console\nAnd Python debugger creates the \"Python Debug Console\" here: It is unrelated to the \"JS debug terminal\". It is just an integrated terminal where the debugger or runtime is launched.\nLooks like the path and args should be supported because they're the defaults: Unless they were configured specially. We'll need to look into this.\nI noticed I have the same problem\nsame here with using powershell core ! but i can't reproduce it with fresh system and latest vs code and latest powershel core using windows sandbox !\nGetting the same error for the past couple weeks, on ssh terminal. !\nwhat's the terminal profile you're using there? Is it a custom ssh one defined in your settings?\ni'm new to vs and having this issue as well.. anyone please help~ thanks~!!\nCan you share your file and also do a trace log while creating a terminal? /label info-needed terminal\ni've uploaded 3 images at 1) terminal 2) renderer log 3) file let me know if you need anything else.. thanks~!\nthanks for that info. I see the when I create a terminal like you do does using pwsh instead as your default profile fix it?\nI am using default bash terminal over ssh. I did not define any specific terminal profiles. Here's the installation printout when it says starting ssh terminal. I can do but I don't know what to grep to share.\nthanks for helping but i've just tried.. and it doesn't work.. same error still there.. what else can i do??\nthis is working for me - anyone seeing this should closely inspect their default profile - that's the primary reason shell integration would not get activated !\nSame issue, but my debugger is cppdbg. Really annoying, I hope someone fixes it soon\nSame issue with npm + devcontainer\nI was having the same problem, but removing and using instead in seem to work for me\n, very interesting, I tried what you have described (I just used \"terminal.integrated.defaultProfile\", but not \"terminal.integrated.automationProfile\", since I couldn't find it in settings), and it partly worked on one computer (the debugger showed up in the terminal and worked as intended, however when pointing at the terminal it still said \"shell integration failed to activate\")."}
{"_id":"doc-en-vscode-067fcc9fe49875656c729fe3f0c8c21df3a62922b8e3e928737a2f913cb9f72c","title":"","text":"THE INTERESTING PART IS THIS: I tried the same , , , on a different computer and the debugger didn't work at all, with the same error. The only difference might be that on the first pc I used mingw from MSYS gcc , and on the second pc I use normal MinGW gcc. I will check later to see if that is the cause\nIf this issue is related to what we expect, then you should see a warning of the form can one of you pls check if you see this?\ni can't see this warning, all i get is \"Shell integration failed to activate\" and nothing more.\nthe warning would show up in devtools' console I think. For this issue I'm going to fix the shell integration failed to activate message in the hover when we didn't even try to inject. For example: !\nis there any solution to this issue?\nYes you should no longer see that message. Can you please verify that's true in insider's?\n<!-- 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!\nthe issue was fixed, thank you for your responsiveness,\nWhen will this be resolved for regular users (not Insiders)? I am using 1.72.2\nin abt a week"}
{"_id":"doc-en-vscode-1fc79999526489e7458b2c1524b4a7638689e35ad6cdfa12fcd2403fd2b669ce","title":"","text":"Type: <bBug</bwhen I do a ctrl-f and run search replace. When I put in a & to search for and a & with a new line it crashes visual studio code and once and a while my whole os VS Code version: Code 1.74.0 (, 2022-12-05T16:47:18.476Z) OS version: Linux x64 6.0.6--generic Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (41)</summaryExtensionVersion ------ language-x86-64-assembly3.0.0 vscode-intelephense-client1.8.2 compare-view0.10.0 vscode-eslint2.2.6 prettier-vscode9.10.3 theme-editor1.9.0 vscode-docker1.23.2 isort2022.8.0 python2022.20.1 vscode-pylance2022.12.20 jupyter2022.11."}
{"_id":"doc-en-vscode-2c43238a7fe2218e638ca0cd843eaf15407f5e25b5e3d84803b41a8a10a70e50","title":"","text":"jupyter-keymap1.0.0 jupyter-renderers1.0.12 vscode-jupyter-cell-tags0.1.6 vscode-jupyter-slideshow0.1.5 remote-containers0.266.1 remote-ssh0.94.0 remote-ssh-edit0.84.0 remote-wsl0.72.0 vscode-remote-extensionpack0.23.0 cmake-tools1.12.27 cpptools1.13.8 cpptools-extension-pack1.3.0 makefile-tools0.6.0 powershell2022.12.1 remote-explorer0.0.3 vsliveshare1.0.5788 vsliveshare-audio0.1.91 vsliveshare-pack0.4.0 gremlins0.26.0 format-html-in-php1.7.0 nunjucks0.3.1 markdown-preview-enhanced0.6.5 code-spell-checker2.12.0 best-light-themes-pack1.0.2 cmake0.0.17 theme-generator0.0.8 php-debug1.29.1 php-pack1.0.3 linkerscript1.0.2 php-intellisense1.0.13 (11 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nThanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.74.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!\nUpdated to the latest version still same issue\nWhich find widget is it? Is it the find within a file or globally across the workspace?\nThanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our . Please take the time to review these and update the issue. Happy Coding!\nIt's within a file\nare you searching against a large file? Can you please share the document you search if possible to help troubleshoot?\nThanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our . Please take the time to review these and update the issue. Happy Coding!\nI used this text in a new file and when I did the above steps it crashed my system."}
{"_id":"doc-en-vscode-05b063e4719765c669182e01cfc968d276aea40bd52192191d4e95374e5d3d90","title":"","text":"It's pure javascript code but not sure how this can crash the system. Assigning to our Electron experts.\nHi, could you attach a ?\nIt is not creating a dump file. Any suggestions to getting crash data from linux (Pop!_OS)\nCan you please share a screen recording of the steps you have tried to get the crash dumps, thanks!\nI finally got it to dump. Let me know if there is anything else I can do to help\nAre you using a screen reader ? Seems like accessibility tree is enabled in your instance and the crash stacks point to Segmentation fault in the accessibility code path. Crash is addressed in\ncannot repro, but would be good if also verifies this is fixed\nI used the latest insiders and it worked as expected. Thank you very much! I tired it on the current release to make sure it was not fixed by me updating my system. The current release still crashed.\nAlso to note in current release I disabled all plugins and it still crashed and anytime I do it twice it crashes my whole system. So it is definitely fixed in the insider release"}
{"_id":"doc-en-vscode-0f1e8da9a5d61672c218bfb4c705cdb03ac453c48fc91d32152df171da0d8d76","title":"","text":"<!-- 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: 1.74.0 (Universal) OS Version: MacOS Monterrey 12.5.1 (21G83) While using a window manager on Mac (Mosaic), I'm not able to resize / place the vscode window on the designated location on the screen. This is relatively new behavior, can confirm this was not an issue prior to release . I believe this release started this bug. vs code is the only application I know of that has this issue. I included a screen recording showing the problem. https://user- Steps to Reproduce: a window manager (mosaic), drag and drop vscode into any of the resizing blocks.\nrequires a purchase, is there a repro with other open source window managers ? In your demo, you seem to using native titlebar. Does the issue repro when launching with ?\nHi I was unable to reproduce it with a free alternative from the apple store (). Setting was not successful either. Normally I would approach the developer of Mosaic myself but it's only vs code that stands out here, every other app I know of (30+) work just fine. Even vs code used to work like any other app, hence this bug report. Mosaic does have a 7 day free trial if that's of any help:\nI actually went for that but I just get pop-up that trial is expired on starting the application :( I have an idea what might have caused this issue in the runtime, Can you maybe help with confirming the issue by following the steps below which requires running VSCode from source."}
{"_id":"doc-en-vscode-c3b3c021b24d82da6092f45c62692617ec7c7a8013b3d2f8c8de27ddf56cb9be","title":"","text":"If the above steps are difficult to attempt now, I will try to provide a custom build later this week to verify.\nThanks for the update. Will give this a try and get back to you\nHi sorry for the long wait. Happy new year by the way! I followed your steps and I can confirm that running with from source I can resize/reposition windows just fine with Mosaic.\nHappy new year :) and Thanks for confirming. As part of an accessibility experiment we disabled the attribute in the which looks like the Mosaic window manager relies on."}
{"_id":"doc-en-vscode-93a623b65292f2ccaab5838dc12bf66be6746ee256743f8b5f603f4321612162","title":"","text":"From: Crash dump: I tried to use but the result seems weird, maybe you can help me explain how you do it? Attaching the output here:\nwill use symbols from which does not contain symbols for our custom Electron builds, so you will have to manually replace the symbols under with corresponding ones extracted from\nshould address this crash.\nbut then our instructions are not correct right? can we please update them to explain how to do this step by step? thanks!"}
{"_id":"doc-en-vscode-ad1f10c2c20f1f3cb7b2f9f23f517179d7c801a537bc615957cb8b1abc0fff2c","title":"","text":"Just upgraded to macos 12.3, try to ENABLE System Integrity Protection if you have disabled it before: Originally posted by in\n[(42)] opendir /Users/xxx/Library/Application Support/Code/Crashpad/attachments/-107c-4a3e-8990-: No such file or directory (2) objc[2187]: Class WebSwapCGLLayer is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/Frameworks/libANGLE- (0x7ffa4f13a8f0) and /Applications/Visual Studio (0x115684ce0). One of the two will be used. Which one is undefined. [(171)] EXCCRASH should not contain exception 12 [(70)] exception EXCGUARD invalid in EXCCRASH [main 2022-11-01T07:19:07.195Z] CodeWindow: renderer process gone (reason: killed, code: 9)\nLocal OS Version: macOS 13.0 (22A380)\nIf the issue persists with latest stable , can you provide the crash logs following the steps at , thanks!\nmy version is 1.74\nIn your case, is SIP enabled or disabled ? Does it crash when you run with ?\n! The same mistake. Are you running normally on the latest Mac 13 system\nI think is not specifically a vscode problem. Im getting this for every Chromium <108 based electron app like: Logitech G-Hub I replaced the with the latest it working since but please don't do that it requires SIP disabled and this is not a solution not even a workaround. !\nThis \"not even a workaround\" works here as well. Thank you for sharing! SIP was reduced beforehand due to OCLP, so I don't know about it. But definitely not recommended reducing/disabling it! For anyone curios:\nIf you are using OCLP with reduced SIP you just need to add ipccontrolport_options=0 to the nvram boot-args."}
{"_id":"doc-en-vscode-88767a9cd72d8b7051e283bfc9eb4b55cb43066c935b1c59e2cf5375fbbe382e","title":"","text":"Upstream issue\nsudo nvram boot-args=\"-v csenforcementdisable=1 amfigetoutofmyway=1 keepsyms=1 intcoprocunrestricted=1 amfiunrestricttaskforpid=1 amfiallowanysignature=1 csdebug=1 ipccontrolport_options=0\" exec this command,program is ok\nare there steps for this?\nthis requires booting macOS with custom arguments specifically SIP and AMFI disabled, better for authors to verify this issue. can you help verify if this issue is addressed with our latest insiders without having to add to the boot args, thanks!\nAre there any conclusions? I also have this problem\nthis will be fixed in our next stable release\nToday it keeps failing. !\nplease create a new issue with crash dumps based on the steps here , thanks!"}
{"_id":"doc-en-vscode-6cf357967c825fed30321dd28ec013ee9c4c71364a48553bf484f9a3d6286dbd","title":"","text":"VSCode Version: 1.41.1 OS Version: Win10 1909 Steps to Reproduce: In an extension: .executeCommand('', 'telemetry'); settings open, but without a search filter <!-- Launch with to check. --No, as there is nothing to run that code\nWhy do you need this? You can use but I don't really want to provide a ton of commands to control all the different options in the settings UI.\n<!-- -96bd-47a8-a0e8- --This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our . Happy Coding!\nThere is a difference between User settings or Workspace settings, there is different UI and comparable methods in the API to reach them. The openWorkspaceSettings has the same signature as openSettings, but they don’t behave the same way. That’s why I think this needs to be resolved to be consistent. Martin Martin Tirion Microsoft Tel +31 (6) 1250 6153 Blog\nSame issue. I just want to open the workspace settings and filter by my extension name.\nSame here!\n+1\n+1\nThis is exactly what I need to programmatically open the workspace settings for my extension, allowing users to easily make changes. For anyone who needs this feature, execute openSettings with your search, then execute openWorkspaceSettings. It will switch the current settings window over to workspace settings while keeping your search string. Example vscode.commands.executeCommand('', 'telemetry' ); vscode.commands.executeCommand(''); Although this works, I still believe these commands should be consistent. I believe my use case is exactly why we need this, a per project/workspace settings window for extensions at the click of a button rather than multiple quickPicks.\nTried solution by I have the exact same use case for this as a couple of people above, providing a shortcut to my settings from an extension. The solution above didn't work, but reordering the calls worked for me: vscode.commands.executeCommand(''); vscode.commands.executeCommand('', '[search term here]'); Works for now, but I have a feeling this will break on me in the future."}
{"_id":"doc-en-vscode-4aa97c0f02afa45a729a26037250dfecf3fe3680819822e676c1b83a2fb9d9a7","title":"","text":"Since the solution provided by already stopped working as of now (at least on my machine/env). So here's my motivated '+1' on this: I think there's a clear use case for this I also subscribe to the argument provided by -- that adding this would make the API more consistent, since then openSettings and openWorkspaceSettings would work the same way.\nThanks and for documenting this workaround I had this same need btw."}
{"_id":"doc-en-vscode-ccb33cb3359768fc49e523ccd38eae37de7f9c63f94182cda5bdb3c9e5da6da6","title":"","text":"have insiders with settings sync enabled add exploration build to the sync select replace local when prompted so that exploration because just like insiders over time insiders UI state gets ruined, e.g the side bar is populated with views I have carefully hidden and rearranged\nThis is caused due to the dependency between two states and . Values of both states changed together from outside Change event for first state is triggered. Updating to this change can cause view container changes like (registering or deregistering) This triggers internal change events to update pinned viewlets Updating pinned viewlets is updating the stored value for second state Bug is caused at the last step -pinned viewlets state is getting overriden without refreshing its in-memory state.\nHow would this be verified?\n<!-- 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!\nSince it cannot be reproduced easily, I would ask to verify this.\nthe steps are as easy as described in or the description of this issue. use settings sync onboard another machine :bug: view state of the main machine get's broken: views reappear, views are reordered etcpp\nCan you please verify this? I believe this depends on some pre-existing state therefore not everyone can reproduce. This state is not trivial to set up. Since you have this state already, it might be easier for you to verify."}
{"_id":"doc-en-vscode-0e8ad7db5338944fa6fa60b4b2b018f413d30d57b4bd8f3f292b325c4912d59b","title":"","text":"Open a large workspace Start a text search Press esc See busy process still running is never called here:"}
{"_id":"doc-en-vscode-0a41ee0a1f8e10da182e38a6d1983372f960eb6719ee45c77ce56cffc495bfeb","title":"","text":"Steps to Reproduce: in VS Code, build and run as an extension the debugged VS Code version open a text file some text Rename from the context menu Observe: the rename dialog opens, however the method on the rename provider is never called. The return before however since no other rename provider is registered the provider should still be called according to discussions with"}
{"_id":"doc-en-vscode-2c80f279ac2c5b07b978451e056ae3c8ec70b1834e6441b74803acf61717644f","title":"","text":"Issue Type: <bBug</bIf I try to open an image with a name such as 'test-' it says 'An error occurred while loading the image'. In the developer console, the following error is shown: VS Code version: Code 1.44.2 (, 2020-04-16T17:07:18.473Z) OS version: Darwin x64 19.4.0 <details<summarySystem Info</summary </detailsExtensions: none <!-- generated by issue reporter --\nLooks like the problem is on the , line 22 We got , which is a string looks like it is correct. Next, when we do it becomes an object and the paths are not correct here. Going down into the () i found that the string is being processed inside the by the This piece of code takes the string, and tries to decode any part started from %, thats why %41 becomes A\nI don't think the decoding process is faulty, but the encoding part. Every browser will interpret as . ! So the url should escape in the first place. !\nYou're right. The percent (\"%\") character is missed in the encodeTable, and in the encodeURIComponentMinimal() 562 line."}
{"_id":"doc-en-vscode-1e30af62d56215aea92f0682e427cfc8ecc187e934f1b3ed58aa88f22717e429","title":"","text":"Expected ! Actual !\nRegressed in\nThe markdown preview in the chat is also broken for Dark Modern but is fixed by your change: !\nAnd the markdown preview in the settings editor: !\nI looked into this some more and have the following findings block rendering is broken for Dark Modern, Light Modern, Dark HC and Light HC What changed: we a new theme token, , adopted it in and , and updated the values for to look good with a different background color But we didn't adopt token for blocks in Markdown previews, which is why is broken for Markdown preview Some options Adopt for blocks in Markdown preview -- this amounts to a rather drastic styling change for Markdown previews ! Revert Revert the change to and drop the usage of so that Markdown preview, chat, and settings UI are in a reasonable state for all themes, which I attempted in\nAlso affects the Extensions Details page since it is a Markdown preview !\nVerification: for Light/Dark Modern and Light/Dark HC, make sure that blocks are properly rendered in Markdown preview, settings UI and chat"}
{"_id":"doc-en-vscode-e44076a08f638d71a573f99fb12804e46e2ed92842536f54a103d6ec36849032","title":"","text":"Issue Type: <bBug</b(or maybe feature) HI! I have a habit that I constantly do and and we have strict rules on doing feature branches, hence creating (& removing) lots of branches per week. (did I just implicitly mentioned that I'm fast : )))) ) So it comes to me a lot that I do and I see no action, and sometimes I even don't understand that no action happened. So it happens a lot that I do code, I do branches, I do sync, I go home happy, I come back tomorrow and I find out that my commits existed only on my local system the whole time. (and, BTW, I have strict inner rules that my codes should always be synced with remote) So, firstly, what I am asking for, is to receive a toast, a popup, an error, or everything that can notify me when I do and my branch is not published yet, so I can remember to publish my branch every time its new. Secondly, I think it wouldn't be bad if VSCode automatically publishes my branch when I do . I'm not sure if this is correct considering git rules/conventions. But If that's OK with Git & VSCode team/community, well, that's OK with me :) +1 Keep up the good work :) VS Code version: Code - Insiders 1.30.0-insider (, 2018-11-30T06:19:37.226Z) OS version: WindowsNT x64 10.0."}
{"_id":"doc-en-vscode-953e2a7e48797104a4379e9eaec61b5286dfd95042232c2f7ac64e6b0fb8d93a","title":"","text":"<details<summarySystem Info</summary </details<details<summaryExtensions (20)</summaryExtensionVersion ------ swagger-viewer2.1.0 npm-intellisense1.3.0 path-intellisense1.4.2 vscode-markdownlint0.21.0 vscode-eslint1.7.0 githistory0.4.4 gitlens9.0.1 tslint1.0.40 vscode-npm-script0.3.5 prettier-vscode1.7.2 vscode-nginx-conf-hint0.1.0 Angular27.0.1 camelcasenavigation0.3.51 Angular-BeastCode7.0.18 vsliveshare0.3.1005 vscode-icons7.28.0 sass-indented1.4.9 vscode-nginx0.6.0 move-ts1.11.3 html-css-class-completion1.17.1 </details<!-- generated by issue reporter --\n(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.453 --- <!-- score: 0.448 --<!-- potentialduplicatescomment --"}
{"_id":"doc-en-vscode-b307699bc5ef5175914a0860203fba5eb689cb74c71f939c46c5223d54d07d35","title":"","text":"has said that when switching between editors, it's unclear to him when a diff editor has been entered, though this is clear for sighted users. We should something like to fix this. cc\nI think we announce whenever an editor gets focus. Each editor has a title that is announced. So I am not sure what is missing here? I would not like that we just add a new alert. Is the title of the diff editor not descriptive enough? Or is nothing getting announced (which would be a bug)\nGood point, the file name is announced and says (Working Tree). is that sufficient to indicate this?\nClosing for now, but will reopen based on your feedback\nJust discussed with JooYoung and the redundant info is escaped/ignored by screen reader users, so we need to alert with this info\nShould we consider a better announcement on focus of the text editor? how does this interact with the existing announcement?\nVenkatesh observed that the editor title isn't being read at all, only the accessibility help hint, need to investigate that. EDIT: I explored and this works as expected.\nEdit: we use already. This is working as expected. When a new file is opened, the title is read. When a user focuses the document, they hear the hint, if any, along with the \"edit text, ...content\". If that hint is disabled, they hear \"edit text,...content\"\nwhich command do you use to switch between editor tabs? Is it ? I believe this issue is about when using that command, indicating if the focused editor is a diff editor via an .\nWhat should I be looking for when verifying this?\nHave some editor groups open, including ones with diff editors. Run the command . When a diff editor group is focused, you should hear \"diff editor\" announced by a screen reader. Disable that setting, and ensure you don't hear that. You should also hear it when navigating the open editors view. !\nUsing the Open Editors view, I don't see anything read about diff editors when I hit on a diff editor: !\nActually, I do see it when I toggle accessibility mode on"}
{"_id":"doc-en-vscode-aa3c90bff8c8cc31e51a8c056f0f82f7ce01eb0e969bef62587357dcfa682b6c","title":"","text":"<!-- 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: 1.85.0 OS Version: Ubuntu 23.04 a file with contents a file with contents the explorer, right click on file and select the explorer, right click on file and select , opening the diff editor the diff editor that , and event listeners have been but not been removed The issue is not present in VS Code 1.84.2. It seems to be caused by"}
{"_id":"doc-en-vscode-0bd9e62ba9a6b8fb47514c2021bbf8ee8fe31a9a883edbeec87952b31dd29edf","title":"","text":"Testing Disable scrolling output via command Select ! The scrolling setting is enabled, which I didn't expect !\nThe setting is for the initial rendering of all outputs, whereas the command will change a single cell's output. I'll see if I can clarify that in the description"}
{"_id":"doc-en-vscode-8427bc7f60fa9aeb522eeb8310089972b16877fd0de1a77d6f710e24cd4ce48f","title":"","text":"Microsoft/vscode Tested using VoiceOver on MacOS Issues The add reaction button on the right side is currently read out atWhen focusing on a reaction in the context menu, it is read as just the emoji name. Github instead reads each option asThe existing reactions do not have helpful voice text. They should be read as the reaction name and number of reactionsThe add reaction button the right of existing reactions also does not have helpful voice over labels\nThis is now read as \"Toggle Reaction\" Since this uses a context menu, this is intentional. Menus don't have special aria labels. This now reads a more useful \"Toggle reaction, x reactions with y\" message. Same as above since this is a menu.\nThis seems improved but I can't get it to read the menu when I tab from the comment to the react menu button. It doesn't read anything when I use the arrow keys to move focus between menu buttons. If I expand the menu with space, then it reads the menu name. It looks like this, so I guess voiceover is stuck on the full comment context even though focus has moved. Not a voiceover expert though, is that an issue or should I be using other nav keys anyway? <img width=\"610\" alt=\"image\" src=\"https://user-\""}
{"_id":"doc-en-vscode-40f991944b3b3846ee0fcd5709fa80dd178cb9c45de240050b837e0296a2501c","title":"","text":"Seeing an increase in issues (such as ) where a mapped network drive or symbolic link points to a UNC path. If you use methods such as or to resolve these paths to their UNC equivalent and use them for further file operations, our UNC allow list might prevent use of these paths until you add them to the allow list. We should discuss if there are options here to make this easier on the impacted users. The issue often goes unnoticed because we do not prompt the user on startup for these paths to add them to the allow list. Workaround Given an exception like this one: Find the resolved file path (here ) and add the hostname of the path (the value between and the first after that) to the setting (here: ). Then restart VS Code. See also:\nThere are some cases that are a bit difficult to handle: In my company, people always either use the raw path to access files, or map a drive to and then access files using the mapped drive name. However the real path is , which is on a server that most developers have never directly interacted with or even heard of (and there are a number of these file servers depending on the exact path). The TS server and likely many other extensions use this real path in their code, and when it does not have access the server crashes. The only way developers would be able to know the host names causing problems and add them to the allowed host list is by examining the error message of extension host which is extremely user-unfriendly. What is tricky about this is that a user may never know the real hostname until a runtime error occurred. And depending on the extensions a user installs, this may or may not be a problem at all.\nIs there a way to get an older version of vscode ? The current version is unusable as long as this bug persists.\nThis worked for me Note: omit the leading and the at the end.\n/fixedWith\nSteps for verification: create a that points to a localhost UNC folder which has a Typescript project open the mapped network drive verify TypeScript smartness works and shows no errors in the TS server output logs\nFor some reason I wish to go back to 1.78 until there is a release which includes the fix. However I cannot find the Windows zip (needed to make VSC ) on the . Any idea where to find it?\nThe fix for this is in releases."}
{"_id":"doc-en-vscode-a350145044d22c14ebdd5088142207efb2fe7e795e29e410ef1705f91124d7b0","title":"","text":"I am still getting this error while using the extension !\ncan you give more details, did you configure the setting accordingly?\n!\nAre we certain this is related to UNC paths? Whats the extension repository, maybe reach out to them as well?\nI am on this issue thread from , that points me to then to this one. Repo is See that someone pointed a cucumber issue here: It's a bit confusing honestly.\nI see no UNC mentioned in any of these issues, so I consider it unrelated.\n, you have a example from this configuration ??"}
{"_id":"doc-en-vscode-f276ab39104bed3897a907e917d6da5d085bd2744c51ea6a3e26eac87d68b47c","title":"","text":"VSCode Version: 0.10.11 OS Version: OS X 10.10.5 Steps to Reproduce: a long line of text that wraps in the editor the cursor on the first line and press Cmd-Option-Down (on OS X). This creates a second cursor on the next visual line, which means it is somewhere on the same logical line depending on how the text is wrapped. When creating multiple cursors on adjacent lines, often it is to perform the same edit on multiple (logical) lines that are aligned with each other. The current behavior having the second cursor appear instead at some situation-specific place on the same logical line throws a wrench in this workflow. I can't think of a good situation where it makes sense (though I do realize it is consistent with pressing the down arrow without cmd-option) Definitions: a logical line is a line in the file on disk. A visual line is a line in the editor. A logical line may span multiple visual lines when there is wrapping."}
{"_id":"doc-en-vscode-5f0d5c059fb44a354c128c8c8582d68a267f2c99cdf219d4742986bbcdd5cf79","title":"","text":"a cell that updates the same line of output continuously :bug: extra character appended at the end and the last update doesn't seem to occur !"}
{"_id":"doc-en-vscode-0280745e470fe6a734777512067d86e42b09615d1f646ce2e746af70f41180b2","title":"","text":"There is now a better Intellisense plugins for Vscode PHP: and . In it's known issues it says \"There may be duplicate suggestions for functions or variables. This is because VS Code has it's own (very limited) code-completion support for PHP, and there is currently no way to turn this off.\" This indeed is annoying, the vscode suggestions are too broad and are just noise compared to accurate entries by crane.\nIt should be possible to uninstall the VS Code php extension.\nfyi\nI think crane still uses vscode's syntax highlighter for PHP. So if one were to remove VSCode's internal PHP extension, would it also remove the syntax highlighter? P.S. I think simple options would suffice, e.g. \"\", so it could be turned off.\nYes - but we can also think about splitting our extension into one part that does highlighting and bracket config and another that does completions. That would allow for more freedom.\nThis is now annoying the testing of proper language server in here : Quote: P.S. I think the option would be a simplest thing to implement for now.\nRelated\nAny update on this?\nI have been holding back the PHP IntelliSense release with intelligent completion for over a month now because it is useless if VS Code just spams the completion list with countless functions that do not make sense in the context. When will we get the option to disable or uninstall the built-in PHP completion?\nI agree it makes sense to provide a temporary option to disable this. Just submitted a PR here:\nAlso just checking - at this point in time, is there anything else about the built-in support that is interfering with the experience? (hover, signature help, etc.?)\nthanks for looking into this. Signature help is being implemented right now, iirc there is no built-in hover. It would be great if all of them could be disabled (everything except syntax highlighting).\nI pushed the PR and changes the setting name for the code completion to \"\". If disabled, hover and signature help are also disabled.\nI don't think the setting achieves the desired result. Setting to I no longer get completion suggestions even from PHP Intellisense extension. If have to use to trigger the completion suggestions list.\nI don't think this is related, this only removes the built-in completion provider."}
{"_id":"doc-en-vscode-ea49850c83b588e0a9ae1e2ae916fc126e1a886b5b40674e0d81302406350a55","title":"","text":"So something else which controls the display of suggestions list from extensions like php intellisense is broken?\nPart of the January build. Add to your settings to disable all completions from the built-in PHP extension."}
{"_id":"doc-en-vscode-c86c758e3754e1c567e4185c1c8aefdf45e87587c8dd0f0171c5243915d75adf","title":"","text":"!\nwhen we triage issues assigned to ourselves we usually use the milestone, anything that will be fixed in this milestone we put to june. Appart from that adding the bug label is usually good so this issue gets verified in the endgame (since it is june and bug). Assigning issues to other team members we usually leave with no label and milestone so the owner can triage and assign it. Cheers\nthanks, I'll make sure and mark them appropriately next time!"}
{"_id":"doc-en-vscode-0e5316ad06a91058c24bedd641437aa44a4edd40194740913c7954f6aa78820f","title":"","text":"<!-- 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: 1.62.2 OS Version: Windows 8.1 Steps to Reproduce: a markdown file with the following content: Open a Preview to the side Rendering/Parsing of line 5 goes wrong Parsing of line 6 gives the: I have line 3 and 4 to determine what causes the problem, it is the literal text at the end of line 5: Any literal text (single backtick) of the content: generates the error If there is a tag on a line, any literal text (single backtick) after that is not recognized by the syntax highlighting in the editor\nI have just updated the extension that has this piece of Markdown in the README. Github, Marketplace and Extension Bar all render the markdown correct.\nI recommend that you disable the built-in , because it turns the Markdown inside VS Code to a flavor much different from GFM that you apparently don't want. The Markdown Math was introduced in . Besides, if you install some VS Code extensions that offer math support someday, you will need to check their documentation to disable the corresponding features. The rendering did not go wrong, to my knowledge. You just discovered the dark side of Markdown. Markdown is not a single rigorous language, but a collection of various flavors (aka \"dialect\", \"variant\") that disagree with each other. Let's take a glance at its history first, though there should already be more detailed articles on the Internet. created in 2004. It's the origin of Markdown, and unfortunately ambiguous. Soon, flavors bloomed."}
{"_id":"doc-en-vscode-47703209eb811930b291c41fb3644d4f7af27e7d97a65ec2c35bee5e7ed728b2","title":"","text":"Many years later, a group led by began to develop . The new spec has become the basis of many flavors in recent years. Among these derivatives, the current , , is the one that you're familiar with. Interestingly, a number of Markdown implementations adopt GFM and modify its extensions to create new flavors, for example, . I don't know the very flavor that VS Code's Markdown Math tries to follow, but it ( and . Please correct me. Now we can see that lots of Markdown flavors are technically incompatible. Thus, it's a pity that Markdown users have to configure their processors to get desired results. Here, in VS Code, the built-in ships a GFM-like environment. You can to get a more GFM-like experience as long as you're careful.\nMinimal example that demonstrates the issue:\nMarking as a good first issue since this should be a fairly scoped bug Here's the relevant repository where this issue should be fixed: The repo includes tests that you can use to confirm the issue is fixed and also check for regressions\nI am looking to fix this by not allowing a dangling dollar symbol inside a markdown block to open or close. Do you think I'm on the right path?\nI still do not regard the behavior here as a bug. Things just work this way as per the inline parsing strategy of CommonMark. From a CommonMark-compliant parser's view, we can say in a non-normative way that is equivalent to Then, given the enabled rules ( default, CommonMark HTML, pandoc-style math, and something else), it's recognized as This is correct and exactly reflects the philosophy of CommonMark. This issue ought to be marked as flavors are not compatible, . A derivative flavor can inherit the philosophy of its parent, but cannot retain the semantics. In other words, you cannot enable a math plugin and expect GFM-like rendering at the same time. You can only discuss right or wrong within the same flavor. If you want GFM-like rendering, disable the built-in Markdown Math () extension first.\nBut how do I write in Markdown Math a line that shows me Is there a way to Escape the\nAvoid plain HTML-like pieces in Markdown. Use proper syntax whenever possible. In Markdown, HTML-like pieces (leaf block \"HTML block\" and inline structure \"Raw HTML\") are nothing, but just a kind of literal content."}
{"_id":"doc-en-vscode-fd7e946e48e8138355b9fef5fcd20505d9741baf88dc221240bde539166bdeea","title":"","text":"CommonMark requires implementations to skip them: There are roughly 7 + 6 rules for recognizing HTML-like pieces; HTML-like pieces are captured, and then emitted as-is to the output, without further touching parser's machine state. This design is a compromise for compatibility, and causes usability and security issues, like your cases. jgm complained about the terrible fact many years ago. As for escaping, if your use case is presenting a character in textual content, you can try \"backslash escape\" like , and \"entity and character reference\" like and .\nMaybe the wrong example asked, the OP was about some italic (or bold) text inside a code block, it was done with <codefoo<embar</emfoo</codeand when you use a character outside backticks and further down on the line a it goes wrong. I did not know Markdown allowed HTML entities. I have now enabled Markdown Math and replaced all characters inside with and now there is no\nExcuse me? I'm confused now. So, you add these dangerous pieces to your Markdown document for formatting? Unfortunately, CommonMark Markdown is not a superset of WHATWG HTML. They actually have almost no intersection, and apply nearly opposite handling when encountering pieces that look like HTML tags. If you decide to have HTML-like things in a Markdown document, you have to be careful, and know how to lead the parser to your desired result. I thought I've made these basic facts clear. But seems no. No one understands my comments above. Before I come up with another way to explain, we can demonstrate something by this sample: If it's treated as HTML, there is one element with a comment and a text node \"\" inside. However, if you feed it to a CommonMark-compliant renderer, you'll get somewhat illegal HTML output:\nIf they are so dangerous why do they allow HTML tags in CommonMark Markdown? As soon as you use single or triple backtick all inside is treated as literal, there is AFAIK no way to make something inside italic (or bold) using Markdown syntax. I use HTML tags to get the required rendered output.\nGood to know. Then, you only need to be careful when configuring Markdown renderer and authoring Markdown documents. This is for not only performance but also conformance. Avoid using inappropriate parsers, as flavors may hold dramatically different logic."}
{"_id":"doc-en-vscode-d788ef2c276f0e4f46064254b0b1a13d674008c16ac5d71e81764c936d88fd71","title":"","text":"For example, , , and can give mostly different results for the same input. The Markdown flavor of GitHub is GFM. GitHub processes user content with , and then pipes the HTML output through some \"filters\" to add GitHub-specific features, such as sanitization, heading anchors, emoji codes, issue references, and diagrams. , VS Code's provides default + , which is a few steps away from GitHub. Basically, you just need to install extensions for emoji and task list, and disable those that don't exist on GitHub (e.g. ). Additionally, since VS Code and GitHub generate heading ID with slightly different methods, a link to heading might work on one and break on the other. It's John Gruber, , that introduced \"HTML\" (but not real HTML). The world has no choice but to live with it. If you ask me to judge Gruber's decision, I'd say the \"HTML\" in Markdown is a sign of laziness, besides, thousands of collective developer hours have been wasted due to tons of lazy and ambiguous design of the original Markdown. He should have defined generic construct syntax first, and built language structures on top of it. Probably I'm bad at teaching. But other people have good skill in communication. I recommend their articles:"}
{"_id":"doc-en-vscode-4cfe948722588f598cadeba17c2befbe132f148b57e6f2c60c2e7f39acaefddb","title":"","text":"<!-- 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: Version: 1.85.0 (Universal) OS Version: Darwin arm64 22.5.0 Terminal input doesn't work ( is too slow almost feels like not working ) when using in Aux Window. Steps to Reproduce: Open Aux Terminal Window In Full Screen Mode or make it Full screen afterwords.\nThis seems to be working in OSS Dev container.\nThis looks to me like a case of scheduling something on the main window which gets throttled once hidden. is the terminal using scheduler for rendering such as RAF or ?\nI can reproduce and its pretty bad.\noff-topic: is there a way to move panel to separate window. e.g. bottom drawer or individually like terminal, debug console ?\nPR fixing it"}
{"_id":"doc-en-vscode-956f715813ed43d0ec70dec1506eb12b0ca2929c0d5433a8f1bc78068c6872d7","title":"","text":"Testing With the following settings: I saw the terminal migration notification and then clicked \"Migrate\", and my settings changed to: Which is defintely not what I expected to happen.\nPerhaps if the shell/shellArgs match one of the detected profiles, the name of that profile can be used? So in the sample above,\nI'm also kinda confused by this... here's what I had: and it turned it into:\nThe behavior should be: If there is an exact match (eg. just ), it should assign the existing profile as the default (). If there is not an exact match (eg. ), it should add the profile to the list and set it as the default. As for the name maybe something like would be best.\nTo verify, see and try other combinations\nor could you pls verify this?\nwith the following: I don't get a notification. Is that expected?\nIf you've already said don't show again to the notification in that workspace, yes.\nah... I hit the which didn't show the notification until I reloaded the window.\nthat was another fix that went in to make sure we're not annoying\nMigration doesn't seem to be working for me. Here's a gif: ! These are the same settings as here\nAh looks like if I already define then this migration doesn't work. If I delete that setting (and use instead as the default profile, the migration works.\nMeaning if you set the to the name of a profile that already exists within your it doesn't work? I think that's by design.\nGotcha. The only thing I'll mention is this, with a defined does not prompt me: but this without it defined does prompt me:\nI guess I would expect the migration to still happen (and a new profile be to my existing ) but maybe that's out of scope.\nThat seems wrong. It should happen as long as you haven't said don't show again. I'll try it.\nah... just opened dev tools:\nit's working for me on Windows.\nHmm what does that mean?\nHere's a repro on non-Windows without PowerShell:\nany errors in dev tools with that repro? can you turn on trace logging? and search for 'migrat'\nBeyond this: I don't see anything... which Output should I dig into specifically?\nRun set log level -trace -open developer tools."}
{"_id":"doc-en-vscode-243eaca6bc753504254cc93c86ffdbc67a8d8ee9dea1aa5bff4b1984675a3255","title":"","text":"you should see a migration message. migrated from shell/shellArgs...\nI wonder if this could be the issue\nHmmm I don't see\nThe fix here is probably:\nEven better is marking the type as readonly too:\nWe might be able to catch this in the future with\nI don't understand what's going wrong here though - if userValue is undefined, profiles get set to already\nI'd think making it readonly would be even worse since then we can't add properties to it - such as the newly created profile\nWhich works fine, the failure case was when had profiles set. The there just corrects the type we're receiving from the config service\nok, should this be a candidate or moved to June?\nI think it meets the candidate bar, we really want migration to be solid"}
{"_id":"doc-en-vscode-cdead3b237241e6cb930c4331e97dec9e85e474099efa596ad141d9e20f5feb5","title":"","text":"Testing Before reverting metadata ! After reverting ! language remains . If I try to revert, nothing happens.\nI was expecting the revert will revert the content to the version on the left side if the diff editor is opened from the timeline view, but it seems reverting to something different.\nI think this can be fixed next month.\nThats a duplicate of Marking as as metadta gets reverted\nYes, the plan is to fix next month, I have a PR, but do not want to merge it just yet Its a slightly convoluted issue,"}
{"_id":"doc-en-vscode-5fa344054195e4458ec82d8f9ed084339664548788da50503683da44f72549fe","title":"","text":"This works on web e.g. but does not work in desktop, either with a desktop git clone or with RemoteHub. The last time this happened it was due to a regression in the list of enabled codecs for our Electron builds.\nSorry for the breakage, the changes from has not been to Electron = 22 versions yet. It will be addressed in new builds this week.\nAddressed in\nReopening because of"}
{"_id":"doc-en-vscode-6777a28ddffc8a23260d905709d643036b939f7de5737ac15bba9d7c0526c45c","title":"","text":"When going over our telemetry for debug actions we have the ability to track usage counts of debug actions triggered from keyboard shortcuts and commands, as they execute commands which we emit telemetry for, but we don't seem to have telemetry in place for breakpoints set in the gutter (click or context menu). This is unfortunate as my hypothesis is that the majority of breakpoints are set this way. Ask Add ability to track breakpoint toggles (add/remove/change) from Gutter click Add ability to track breakpoint toggles from gutter context menu\nwould you like to contribute a PR for this? It shuold be fairly simple and you already have the nice code pointers.\nI'd be happy too, but we should land on an agreement on how to implement it. What's the best approach? 1) Add telemetry directly to the gutter actions 2) Re-wire the gutter actions to execute a command instead?\nfor the best approach let's first see what you want to get exactly? total amount of all breakpoints set (including the gutter) grained events for breakpoint setting based on the way the user initated that aciton In case of 1 we should just add a telemetry ping in the  since everyone should go through there In case of 2 depends on how fine grained you want it, if for every place then we should add an argument or something like that in the addBreakpoints method and then also report that to telemetry.\nI'd like us to be able to contribute a source/initiator to given breakpoint, so we can get an UI usage distributions, etc.\nI suggest the following Add a third argument In the implementation of that method use the telemetry service to report the appropriate event with the context. And you should nicely get all the errors of all the callers of , simply pass different string context for each caller and you shuold be good to go. Let me know if you have any questions\nCool, I'l see what I can get cooking!\nRemoving my assignment for this. feel free to assign me back if you do not have time to tackle this and if we need this for August\nhey, would you still like this? If yes I can also look into it in October\nI'd still like to do this to get my hands dirty.\ncool, unasigning myself and let's leave it for October\nVerified by code review, adding verified label"}
{"_id":"doc-en-vscode-127306f82f356c1ce1754b6bd4689d1579a367ce8ec3ed05034bef38bd98ed8b","title":"","text":"vscode window (given you have setting to put debug controls in the command center notice how the command center includes debug controls and then right away disappear See:"}
{"_id":"doc-en-vscode-5f61083dc6c15efae8fdc1dd41ac47cef16e2a42376c2d67c105a2b1356d16b8","title":"","text":"Could look like this, but have and/or tasks entries as well as a one. Hiding it by default is a good way to avoid cluttering the action bar - so people only see it if they want to <img width=\"285\" alt=\"Screen Shot 2022-09-30 at 12 56 57 PM\" src=\"https://user-\"\ncc\nTalked w Kai and we're thinking to instead add a action to the terminal dropdown which aligns with the menu and will aid in discoverability !"}
{"_id":"doc-en-vscode-8e535e94ce068c358ca87e9457b2f983e7dc5d88122b9af0f6cf2351c5ae90aa","title":"","text":"This is a valid bug. To repro: Open an empty window Open the explorer view. Make sure you have welcome page opened in the editor. Click on link the empty view Select a folder to open You will see above error trace in the console\nNo Folder Opened view () is removed when folder is opened. When removed this view is disposed. Following listener is getting invoked even after view is disposed It is because, view is being removed/disposed by listening to the same event It seems, once an event is fired all its listeners are invoked even if one of the listeners is disposed in the middle. This is causing the listener to be called even if it is disposed. Assigning to you also because it is related welcome view.\nWhat link should I click? !\nYou have to make sure welcome page is opened <img width=\"955\" alt=\"image\" src=\"https://user-\""}
{"_id":"doc-en-vscode-21ac1c47238d33bbba8b816317444b701dde286eaf9effd1db3dbd70128acc66","title":"","text":"<!-- 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: 1.71.0-insider OS Version: macOS Big Sur 11.6 Steps to Reproduce: a link in terminal containing \"[\" or \"]\" characters (ex. ) to cmd+click the link, observe that it is split on those characters. For example, links to , , , , and . In reality this is one valid path (nextjs uses \"[ ]\" to identify parameters in URLs) <img width=\"526\" alt=\"Screen Shot 2022-09-22 at 5 12 00 PM\" src=\"https://user-\"\nThis works for urls: ! Not local paths: !\nreported that it does (kind of) work: ! We would need to review all link detectors for this.\nThis happens with local links because [] are currently excluded chars:"}
{"_id":"doc-en-vscode-dccf5681783e4347602d9ddbbd53edfeb961647c2b5924b1e3a466986499d9a8","title":"","text":"<!-- 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 Steps to Reproduce: The documentation has a spelling mistake LINK: -Value of an environment variable on the host machine (in this case, called VARIABLENAME). Unset variables are left blank. To for example, this would set a variable to your local home folder on Linux / macOS or the user folder on Windows:\n/ , can you please point me to the GitHub page that corresponds to this page.\nThanks for pointing this out. It looks like we fixed the typo () but have not yet deployed the latest changes.\nYou are welcome, ! I was trying to fix the issue for Hacktoberfest 2022, but I was unable to figure out in which repo this file was located. Just out of curiosity I would like to know as to where the source file for the page with the typo reside in GitHub?\nThanks for looping me in! Opened a PR in is the repo for"}
{"_id":"doc-en-vscode-e94eb279bb36621a7c3a24e185aa4a067cf39142079ff34b2dcdd99acc75d2c4","title":"","text":"Open a file with multiple changed regions in git Move cursor inside/next to some change Run \"Show Next Change\" (alt+f3) It reveals and shows a different change- I think it always shows the last one in the editor. It should show the next one after the cursor position I can press it multiple times to cycle through changes, and that's correct, but it always starts with the last change\nI'd like to fix this for April, but it looks like the change could be risky. I will fix it for May.\nFound a low risk fix.\nThis works, thanks! But one thing that my muscle memory is unsure about, did this command previously move the cursor? I'm noticing that if I press it multiple times, then press escape, the view moves back to the place where I started, when I'm expecting this to be like a \"navigate\" action. I can open a new issue, or if it's always worked like this, it's fine\nI went back to 1.74 to check, and it didn't move the cursor there. \"Go to Next Change\" will move the cursor though."}
{"_id":"doc-en-vscode-8d7ce9627ab453856cdca4b967a241cd2275bbf8a8b7331bae3c5991a593f565","title":"","text":"Open Select the top cell and page down a few times Focus hits a cell that is longer than the viewport, which is maybe important, then the next page down moves to a higher cell\nWhen a list item is larger than the viewport, and it's also the only element in the viewport, pressing page down will reveal to the previous element, this is because we did a here (the catch is, the last page element is also the first page element)"}
{"_id":"doc-en-vscode-43e7ecc5986bc893fea494056b10e2a3c39d817d1f651932eaa9a8c733a4bcb5","title":"","text":"This is very useful when working with the commandline, and to pass the result directly into the editor. It's especially useful for getting a file out of git's history, eg: FWIW, this works in Sublime.\n+1\nHere is my workaround (I'm on OSX so might need to adjust accordingly): create ~/bin/codestdin: Then run: Now git log, git show, git diff pipe correctly into vscode\nSimilar to approach, I've this to my bash profile to wrap the command... definitely not flawless, but it works for my use cases (so far). e.g.\nFor you have to modify the function a bit and use , because is a BUILTIN in and will return the function itself: What does not work is something like\nHello, For using the redirect, does this express the intent of getting of copy of the file contents assigned to an anonymous file buffer? Would that be similar to for intents sake? I wonder if are the only thing to care for that scenario? Thank you. Good day.\nhello yes this should be equivalent as as I know.\nCan we get some priority for this issue? It's been open since 2016 (that's 552 days!) and it's a bit ridiculous that VSCode still doesn't provide this extremely rudimentary shell interoperability.\n+1\nPushed a change to feed the contents of stdin to a file and have it open in VS Code ( is implied when doing so): ! This currently works by or not, which is a bit brittle. If someone spawns VS Code without terminal emulation we might wrongly assume that data is coming in via stdin and open a tmp file. If it turns out that there are too many regressions, I might have to add a startup argument (, ) to explicitly enable this. If someone has a better idea how to detect if data is flowing in via stdin let me know.\nThis is great to see! Thanks so much! Is Atom's implementation the same?\nas far as I know, Atom does not support this.\nhuh, I really thought it did, but local tests (and ) suggest not. Anyway, thanks again!\nHello, would you be kind enough to update your OP to note that Atom did and does not as of writing actively support this (probably just taking it out)."}
{"_id":"doc-en-vscode-64a5bc76af3e3adb4546f751a428090463558fb456f63ad0ca6e9282444f86b0","title":"","text":"There is the PR for them, but it is nice to have the proper perspective that VSCode is in the forefront of this kind of feature. Its no harm to stay, just misleading. Thank you. Good day.\ndone\nThanks for the feature, very nice. Just my 2 cents on feedback, the implied seems unnecessary. EG: when I pipe to TextMate it gives me my prompt back. There might be other reasons though for having the wait that I'm not thinking about though. Regardless, cheers and thanks for the work!\nthe calling process is waiting because it is not clear how long data is being sent to . It could be that the editor is already opened but data is still flowing. A workaround on your side would probably to send the command to the background by appending \"\" at the end?\nHrm, wasn't aware that was even possible. I feel like most commands I pipe complete then output is sent to the editor.\nA terminal can have a specific encoding set which my solution did not yet account for. I pushed a change to try a little bit of terminal encoding guessing but I think the solution is not ideal. If someone has a better idea ( ?), let me know: Linux/macOS: use the output of running as encoding Windows: use by default any OS: if you specify an environment variable it will always win over the guessing This will not help if you change the encoding of the terminal ad-hoc as that does not seem to cause any configuration change that the command would detect. On Windows I see the  command but the output of that command seems to be intertwined with human readable text and not just the encoding. If someone has a better idea for Windows, please speak up."}
{"_id":"doc-en-vscode-d11b0f023a72851fbebb9a199b2f20369dcf9781b885785329baf697f17fbe67","title":"","text":"If user does not want the close button to be visible - vscode could make tabs more narrow to show more tabs. Tabs with changed content could get wider to show the 'dot' denoting unsaved file ! !\n[ ] Verify: when the tab close button is disabled, the tabs are not leaving room for the dirty indicator until the editor is actually dirty."}
{"_id":"doc-en-vscode-48c6598940606c23fdc7000c86f1a510ad5c8e6cd189aff61e925e91c2f111d9","title":"","text":"Found this stack while scanning through some failing smoke test runs From Deepak:\nWhat are some verification steps for this issue?\nI did check logs last week and could no longer find this."}
{"_id":"doc-en-vscode-789d7e08cf1a7a110c5b69826763b4fecacb2bbec0e7bf59689c81e4cf1faf57","title":"","text":"I noticed this in smoke test runner logs leading me to think that the type of the exit code is not a but an now?"}
{"_id":"doc-en-vscode-9b36d78218b1f7ae53d6a23cd37d47ccec7ae55e2332c4e95b9c6c7e9c3acec6","title":"","text":"Type: <bBug</bIn the most recent insiders version, audio cues no longer play. I ensured that the audio cues I expect are enabled (e.g. error) and entered the following json as an example: I ensured that the error was reported when moving through errors with f8, yet the cue doesn't play when I come across the line with up/down arrow keys VS Code version: Code - Insiders 1.71.0-insider (, 2022-08-05T07:36:58.753Z) OS version: Windows_NT x64 10.0. Modes: Sandboxed: No <!-- generated by issue reporter --\ncc\nWe didn't touch anything there the last months, maybe it is caused by an electron update. Will investigate for the next release.\nI can reproduce this. Easy repros steps: 1 list audio cues command cues do not produce sound Works fine on latest stable. Does not work on Insiders. fyi since most likely caused by Electron update (thus adding label). Maybe our future planned ffmpeg change will fix this? thanks a lot for reporting this, and sorry about this breakage.\nYou're welcome, I'm running insiders for a reason Looking forward to a fix.\nLet me also assign since we will now support would you like that all our audio cues are in format? If yes, would you like me to reach out to our sound designer for this? Thanks\ncan you track the conversion in a separate issue, this particular issue is a regression with the ffmpeg build shipped with internal builds. There was a recent build architecture change and it impacted this. I would like to close this issue as part of the next Electron version update :)\nmakes sense, thanks! There is actually already this one which we can use for the conversion\nThe same problem using code-insiders into a fedora workstation 36.\nIt is working again with orca.\nlovely, thanks for confirming. Adding verified label.\nFor me it also works like a charm on Windows.\nFor some reason I can't explain, this issue seems to have returned on my fedora workstation. No sound is played when I move the cursor to lines that contain breakpoints, errors and etc. Version: 1.71.0-insider Commit:\nConfirmed on Windows. Could tests for this be somehow?"}
{"_id":"doc-en-vscode-eba7226ab9a0cf71a3688840038e07f2784be75c07084e2d2ab062a583295bce","title":"","text":"Sorry for the regression, but this is a temporary expected breakage because we are updating our supported audio formats , audio cues will be updated to new format this iteration as part of /cc\nSorry about that We just pushed a fix, and the VS Code insiders from tomorrow will have the fix.\nThanks Given this feature turns out to be pretty important for us visually impaired users, would it be possible to create a system test for this? I assume it should be possible to throw a audio cue at FFMPEG and make it fail if the sound doesn't play?\nthat's a good idea. However I leave this up to since he is driving this from engineering and would have better ideas how we could test it exactly.\nWe would need a way to ask the OS if an application played some sound.\nIt works again, at least on my environment. Thanks.\nawesome, thanks for letting us know.\nI can confirm that it works here as well. Hopefully it stays that way"}
{"_id":"doc-en-vscode-6357f8318b7d24847f3db5ffc1c811b01745507b16904ce0c07c3095720417ae","title":"","text":"<!-- 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: 1.66.0 (x64) OS Version: 10.0. Build (Window 10) Steps to Reproduce: VS Code (or use the shortcut ) the first miliseconds after opening a new instance of VS Code, a \"Window 7\"-like window frame layout appears, before the usual VS Code look shows up (see the attached GIF). The GIF below first shows the expected behavior, opening version 1.65.0, followed by the current behavior of version 1.66.0. ! The two executables were downloaded from: and\nRefs\nthat's the reason I went back to 1.65, frames are so annoying.\nHi just a small update: I've downloaded the latest VS Code Insiders and the problem now only appears when launching VS Code for the first time, but no longer when opening new windows from a running instance of it.\nThis issue persists in the new latest version release, .\nThe issue persists in today's release, .\nSince the related bug in the Electron repo has a label, and today's VSCode uses , I believe we will be experiencing this bug for months.\nThe upstream Electron issue is at The issue was introduced in Electron v14.0.0-beta.5 and the commit that introduced the issue is The PR fixes the issue where frameless resizable windows show Windows 7 frames during startup, but there's a larger issue that is still unresolved even with that PR."}
{"_id":"doc-en-vscode-7859da4db8c5bead434bce14aa744a5f67ac562f76c125f01353575ac0e4e26c","title":"","text":"I also searched through the thousands of to see whether they had anything to do with the issue, but I didn't find anything relevant even after reverting several suspicious commits. Running with Electron v14.0.0-beta.5 or newer on Windows 10 reproduces the issue. The PR fixes the issue for frameless resizable windows by calling at an earlier stage of program initialization. Assume the window is frameless and resizable. Then, the program sets to earlier in , and the following occurs: is not run, meaning is not removed from the style set in Line 62. This style parameter is passed in to a call at . is not run. Instead, the block above is run, which adds a style to the style passed into the call. , because of these styles being passed in, after the window is shown, we get a single message, and no messages after. NC in this case refers to non-client area, which is the frame. DWM stands for desktop windows manager. After adding a long of 30 seconds to the call above, I was able to use Spy++ to log messages to that window and see the following: I have also attached full logs to the end of this comment. For frameless windows that cannot resize, even if we call earlier, because the program would pass in , for the and calls above, the style would not be in the styles sent to the calls. As a result, what I see in Spy++ is being toggled three times, and several calls that result in messages being emitted. Using Spy++, I confirmed that the calls have the flag set. I have searched the Chromium and Electron codebases for and (as well as ) to see why the frame might be rendering more often when is not passed in. However, I haven't found anything within the codebase itself. Searching Windows documentation, I found the following: causes to be sent. Reference: However, I'm not sure whether this could explain the difference in behaviour between resizable and non-resizable windows. can pass in or to send to the window, which is why I searched for those two constants within the codebase. Reference: Also, Chromium handles by returning at , which I assume causes the message to occur. Also, Electron calls at ."}
{"_id":"doc-en-vscode-0f84adde360ee479057ba382dd386b47bf11d83ae97a14569185a5ba41fe094f","title":"","text":"I noticed that if I don't call there, the Windows 7 frame doesn't show up, but then the Electron window doesn't render with the proper style (see ). I also noticed that when the Windows 7 frame shows up, it has the style of whatever was passed into that specific call. For example, if I add to the call, then for a second I see a Windows 7 frame with applied. I also tried creating a minimal project in VS to reproduce the issue but wasn't successful. The frame that rendered seemed to have a Windows 10 style rather than a Windows 7 one. I also tried registering a listener in for the messages, and it did seem to get hit, though I couldn't do anything with it. There's also the mysterious , but I wasn't able to apply it to resolve the issue.\nThe PR that linked above (partially based on ) should resolve the issue for VS Code Insiders and hence close this issue, but there's still more I'd like to investigate, especially for frameless non-resizable windows. I some lines to log the hwnd and style passed into each relevant and call. One example of the styles that show up: There's also another window being created really early, but I don't think it influences the issue. Good scenario (meaning no frame showing) with set to and staying Bad scenario with set to then Bad scenario with set to and staying The call with style causes the Windows 7 frame to render, and its style corresponds to is actually the same style just with , once again showing how mysterious the constant is. While working on , I also noticed that changing the order of the calls seemed to fix the issue for frameless non-resizable windows. In particular, on the Electron side, in , if I first called to pretend that the window is resizable, and then called (where ) after the call around line 365, then the issue is resolved even for frameless non-resizable windows. However, this workaround delays the call to hundreds of lines later, and I wouldn't be surprised if it would cause a regression elsewhere. Just like in the log file of the good case of the previous comment, only shows up once, rather than three times. For completeness, here are the logs with the styles for this scenario, excluding the logs: In this case, the style never comes up!"}
{"_id":"doc-en-vscode-7c286e9dc00e23861000dc3aa3c2eb8bdf88ab9b40e519456e57ed4c434f187e","title":"","text":"I also tried delaying the call and calling instead of , but that doesn't work because it fails to pass to the call as well as the first call, both of which need for the frame not to render: can be used to change the non-client (NC) rendering policy and hence result in a call. However, I did not find any references to within the Electron and Chromium codebases that were actually called when running my minimal repro.\nlets continue the investigation in\n<!-- 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!\n/verified"}
{"_id":"doc-en-vscode-ca2e1986b82b6a9002b4ff66253e1f6e10b6828f40a13a300bf503a592e5ea1e","title":"","text":"Just asked hi: ! Expected: ! Version: 1.88.0-insider (user setup) Commit: Date: 2024-03-25T05:49:32.344Z Electron: 28.2.6 ElectronBuildId: Chromium: 120.0.6099.291 18.18.2 V8: 12.0.267.19-electron.0 OS: Windows_NT x64 10.0. GitHub Copilot Chat v0.14. (pre-release)\nbecause of\nTo verify configure have a very wide view port ask AI to change some code make sure the input widget is full width of the zone widget"}
{"_id":"doc-en-vscode-d61af2ef1fbb20144b7c8ae7e852d4b351c1c69cf71b7f51c8eeb0cb37cf8445","title":"","text":"cmd+i now cmd+backspace invokes instead of deleting the line in the text editor The ChatWidget is writing its context keys to the editor's ContextKeyService, so we need a scoped CKS at some point, either inside the ChatWidget or outside in the inline widgets\npushing a fix to use a scoped CKS but this does look like debt. Isn't a better fix to reset context keys when hiding/dispose the chat widget?\nI don't think those context keys should be applied on the editor at all, they are intended to just be active inside the widget's dom tree."}
{"_id":"doc-en-vscode-e3ea470a912b4739aaf0edae74bc7bdc1582b53b75877f6b84d8a2657d1ef62b","title":"","text":"VSCode Version: Code 1.7.2 (, 2016-11-21T22:14:18.217Z) OS Version: Linux x64 4.8.0-26-generic Focus on debug: ! Focus on extensions: ! Can the bright one be on debug as well?\nFor me all viewlets show the same feedback once focussed: ! Please clarify the issue you see.\nOh I mean via tab focus.\n! still they all look the same to me?\nI see what you mean, when you focus into the current active viewlet, the orange bar to the left shows up stronger. I am not sure who this, I think might be the one?\nThis issue has been closed automatically because it needs more information and has not had recent activity. Please refer to our for filing issues. Thank you for your contributions.\nClosing as designed, no plans to change it currently."}
{"_id":"doc-en-vscode-f3fe6a65a5dce1889f29aeadb35e2fa5a25dea0a99859aa528074a160509e0ec","title":"","text":"Issue Type: <bBug</bthe integrated console viewlets to a vertical layout the viewlet narrow When wide enough: ! Once narrowed: ! Expected result: Debug Console search bar shrinks/hides itself in order to show other tabs first (like in the first screenshot). The 3 dots \"works\", but is, at least in my opinion, more annoying than not being able to search in the Debug Console when the viewlet is narrow. VS Code version: Code 1.63.2 (, 2021-12-15T09:40:02.816Z) OS version: WindowsNT x64 10.0. Restricted Mode: No <details<summarySystem Info</summary </details<!-- generated by issue reporter --\nThe min width is 300, I think that can be narrower. The problems view filter input goes into the body when the view is too narrow, which is sorta cool <img width=\"571\" alt=\"image\" src=\"https://user-\"but I won't implement that right now\nActually it was easy to opt into that. I tweaked the min widths and also when the pane is narrow, the filter box will move down into the body\nHoly, I forgot about this issue! Love the idea of copying the behaviour of the Problems tab! Excited to try it on Insiders :) Thanks !"}
{"_id":"doc-en-vscode-d63051adcb21ab5c7824b4ebb6d608d67aa80d04b9a026f0a8a21eb2835f2c43","title":"","text":"!\nupdated Insider's and the problem remains\nI think this is the same as We will need to always send the exit code and have it get evaluated on the renderer against the extracted command name to fix these problems.\nsometimes reproduces on mac\nyou can check if this is the same issue () by running a command a few times and then when is run if it's a single entry or multiple in the output.\ninteresting to me that it allows repro on linux/WSL and does so inconsistently on mac. here's linux: !\nK, let's try understand this a little better then, that shouldn't happen as the initial history id is 0:\nOh I figured out when it reproes on mac - if you run the same command in a different terminal, then the second and beyond ones don't have an exit code\nRunning the command again in the terminal where you first ran the command works every time and does not repro on mac. So mac steps are: in terminal 1 - again in terminal 1 - in terminal 2 - Linux: a terminal and run any command - placeholder decoration shown for the first one regardless of exit code\nIt would be nice to fix this since is the default shell used\nThink I see the problem, PR incoming."}
{"_id":"doc-en-vscode-20e73f61992ec1c3f873d643e1d8af8e4fc9dd47d5c1ce35c0323af43f660c1d","title":"","text":"Repro: Add a long string item to a list setting, e.g., . Try an item without spaces (like a really long identifier) or with spaces. Expected: Overflow of the item is handled somehow, e.g., elision, broken to separate lines with enough spaces. Actual: The item text overflows horizontally and vertically (depending on spaces in the item), overlapping other UI elements. E.g., <img width=\"854\" alt=\"Screenshot 2024-02-27 at 11 31 47\" src=\"\"<img width=\"815\" alt=\"image\" src=\"\"Version: 1.86.2 Commit: User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 Embedder: <!-- generated by web issue reporter --"}
{"_id":"doc-en-vscode-53cf4dbcc0722fcfc5f8587fcde3c1d8174ed4ddfed5802f75bcfc428fe20868","title":"","text":"VSCode Version: 1.2.0-insider OS Version: OS X El Capitan 10.11.5 Steps to Reproduce: by default settings !\nCannot type cyrillic as well\nUpstream issue\nThis is one of the issues I want to focus on for v1.4"}
{"_id":"doc-en-vscode-eacaa740b6edc1c7ac518042e55993a6c501170d7ddf47fb4270a8a7318c156a","title":"","text":"With latest release (1.21) you can split terminal infinitely. This breaks badly the terminal area. Probably the IDE should limit this to a defined maximum or something?\nI considered adding a max value but you would always be able to break it then by sizing down. As a mitigation we could disallow creating terminals if the desired room isn't there but the real fix is proper overflow behavior.\nThanks , I would agree that proper overflow behaviour is the way to go. Thanks!\nI think the easiest way to improve this is to only allow terminals to be created if there's a reasonable amount of room. This can exist with our current lack of overflow behavior as it's an improvement on the current and will prevent 100 terminals from being created..\nSome terminal can be resized to a small size if they are not important. In some case, showing multiple terminals is just to notify the user whether they are running. Currently the minimum size of terminal is too large.\nI suggest the minimum size of a terminal should be an option in Settings."}
{"_id":"doc-en-vscode-82f549c326896b0a606eafb5066d9deafce285e46dc7b519c8b0672f447af603","title":"","text":"One way of resolving this would be repeating the position information when I press any of the commands, even if there is no change. Another possibility would be to prevent the widget from refocusing when I am in the first / last element, and I try to move beyond that element. In that way pressing the next command will not produce any feedback if I am in the last one, and the previous will not produce any feedback if I am in the first one. Does it make sense? In any case, this would be a refinement, not something that would prevent someone from using the feature. Originally posted by in\nSomething else to consider when fine tuning the responses. Right now, position information is announced using an alert in macOS, and a status message in Windows. This is a situation where it makes sense to use an alert in all platforms so that screen readers prioritize this over other events. For example, right now JAWS is announcing position information after reannouncing the widget.\nHuh, I'm using for all platforms here which appears to be platform agnostic I think it might just be a JAWS issue - does this repro when using NVDA?\nIt doesn't, but NVDA handles aria-live differently. You may be right dough. I'll debug NVDA on Monday and we'll know for sure which event it is seeing. JAWS may be simply prioritizing the focus event.\nFriendly ping! Looks like this issue requires some further steps to be verified. Please provide us with the steps necessary to verify this issue.\nFocus an accessible view for which there are several elements (like chat responses or notifications). Verify that if you are on the first or last element, pressing next or previous does not result in repeated alerts. it should not notify the screen reader user as nothing has changed.\nNote to verifier there's an issue to disable these actions when they cannot be taken, which is the better fix.\nVerified. With NVDA, if I press enter on the Next button while on the last chat response, the focus goes back to the response text instead of staying on the button, though that might be by design."}
{"_id":"doc-en-vscode-a2f991c13850fa839e51c8fbb7f9e068c6d748d2fb5ac1c4455ead84ccba22f8","title":"","text":"Testing In the export flow, there's the step to \"Export as...\". The options are \"File\" and \"Github\" <img width=\"615\" alt=\"image\" src=\"https://user-\"I can make the educated guess that I'm not exporting the whole of Github from my VS Code window, but it'd be better to say \"Github Gist\" instead, or \"Export to\" instead of \"Export as\". I prefer the former since it's clear where it's going--otherwise people might assume it creates a repo on their account or something.\nIt was GitHub Gist before, after feedback I changed to GitHub. I will bring this to UX and see what other think too.\nGood feedback. We will also do a user study next week so we will see how users react here. Alternative rendering: \"GitHub\" and then \"gist\" as the description a bit to the right - QuickPick should support this.\nThere was some confusion in the user study when exporting as GitHub. They were expecting that it will be part of a repository. So calling it GitHub Gist might be the way to go.\nI think adding as description would be good\n!\nLovely, tried it out. Verified."}
{"_id":"doc-en-vscode-00527d4b5d681812c67966f052ed7f136013d13e98e820474110feb7399c5f27","title":"","text":"Type: <bBug</bAlt+C or Alt+W or Alt+R Now if area with code is in focus, broken search parameter selector will appear without search panel itself. If terminal is in focus, search panel will appear. I think it is completely unneccesary to intercept alt+c globally when no search panel is opened. In my setup it leads to conflict with alt+c fzf's key binding in terminal. VS Code version: Code 1.86.2 (, 2024-02-13T19:41:37.860Z) OS version: Linux x64 6.7.6-arch1-1 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (19)</summaryExtensionVersion ------ vscode-nginx-conf0.3.2 vscode-cython0.3.10 vscode-docker1.29.0 autopep82023.8.0 debugpy2024.2.0 isort2023.10.1 python2024.2.1 vscode-pylance2024.2.2 jupyter2024.1.1 jupyter-keymap1.1.2 jupyter-renderers1.0.17 vscode-jupyter-cell-tags0.1.8 vscode-jupyter-slideshow0.1.5 remote-containers0.348.0 cmake-tools1.17.17 cpptools1.19.4 cpptools-extension-pack1.3.0 rust-analyzer0.3.1860 cmake0.0.17 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nThanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.87.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!\nThis is feature - it influences bahavior of Add Selection To Next Find Match (<kbdCtrl</kbd+<kbdD</kbd) and Select all occurrences of current selection (<kbdCtrl</kbd+<kbdShift</kbd+<kbdL</kbd). However not sure how regexp is useful here, except it would be applied for next find.\nCan you share a screen recording? I'm not sure if I understand what you're talking about."}
{"_id":"doc-en-vscode-12ba88f755df36105e9eee14ed97e0f8a85ca09206e32aa2fb469c162d30ce55","title":"","text":"This video shows the behavior of vscode after pressing alt+c\nThis video shows what I expected after pressing alt+c in terminal It is configured with following lines in .zshrc:\nI can repro when the widget is visible even if my focus is in the editor\nNever mind, the little toolbar in the editor is coming from the editor command , not our terminal one."}
{"_id":"doc-en-vscode-33c3047cf74d705137b0b3b93c6a252fbe838169574b1670335fe6b1ae4d90f5","title":"","text":"I'm always returning to projects and see the terminal messages filled with the same repeated message and would like to clean them up and not be shown as I see no value in them for myself. <img width=\"630\" alt=\"CleanShot 2022-06-14 at 09 10 55 src=\"https://user-\"<img width=\"622\" src=\"https://user-\"\nThis bugs me too, tracks only showing it once in this case by avoiding saving new parts if there is no terminal input, similar to how it only saves and restored in the first place if the terminal has been interacted with. I don't think we should be hiding the message all together as it's misleading what is part of this shell's session, command decorations would be broken for the ones that aren't part of this session (look like a bug) and it would show up like this which is a bit weird: !\nWould it be possible to have an option to hide the previous session altogether and just show a new session? That would be a simple approach that would work for me personally, similar to <img width=\"566\" alt=\"CleanShot 2022-06-14 at 09 40 18 src=\"https://user-\"\nyou can just create a new terminal altogether by setting to false\nthank you! I was searching for a setting and didn't ever find that one, kept looking for \"terminal history\" and \"terminal clear\"\nthe name is definitely not discoverable. I wonder if we should change it\nor can we add any meta data or keywords to settings that will be picked up by search? cc\nI guess?\nOh that doesn't work, do we have a way to do search keywords?\nyou actually want , the setting will disable process reconnect across window reloads."}
{"_id":"doc-en-vscode-728954f4d98ab1937e4b27d9df95d96321b1739eec71ddf49f5f816f1a61b82b","title":"","text":"Testing I started the Troubleshoot issue flow and it took a long time to create my initial profile. All I had was a status bar item which took me a while to discover (I actually thought something else went wrong). I would love to see and editor / web view better guiding me through that process by: listing the steps and adding check marks when done showing me the number of bisects still necessary giving me a final report.\n<img width=\"258\" alt=\"capture\" src=\"\"\nWe should also have a UI to always stop the process (see ) for a situation where this is useful\nI now see that there is a notification for each step. This makes it better, so may be a simple thing to do is to show a notificatio with progress when the profile is created instead of a simple status bar item.\nActually, setting up the trouble shooting profile should be fast and instant.\nWas not for me :-(\nFollowing notification is shown now !"}
{"_id":"doc-en-vscode-4efd122653fe4a12ab0e3d19c30b9408752ce39c182a3239ea966d0fd1cbdebf","title":"","text":"Here's what I am seeing. It looks like the accessibility help always gets the content from the editor. Here's a gif: I might be doing something wrong ! Originally posted by in"}
{"_id":"doc-en-vscode-e0db2ca2e923c25e33b92e4356cbac6b3325f1bd1b87fc87184fac84a2bedfc1","title":"","text":"Open a new folder Trust the workspace Some of the colors in the window become wrong An editor has the wrong background color Opening the theme picker fixes it !\nI originally filed because I encountered this during Settings Sync but think it's not related as I also saw this when opening files: !\nStep to verify connect to settings sync install and set the Dracula theme () notice that the remote indicator is violet open a new folder that is not yet trusted the trust dialog shows up, approve verify that the remote indicator is still violet, not blue"}
{"_id":"doc-en-vscode-8e4e7f32674c3a07ce7001b04ee5abcc5bc69d48f66c8ee304a3c75034e35781","title":"","text":"For some projects, every commit has to have the signed off by tag. It would be very helpful if there was a workspace level setting that enabled signed off by flag when committing.\nVerified !"}
{"_id":"doc-en-vscode-68014fb67c6bf689e010a0182f4ff7184c159e6329fc34b5e6c3227e546e67a6","title":"","text":"I opened the Settings editor, hovered over a setting, and noticed a new grey line appear to the left of the settings. This issue occurs with the default light and dark themes. !\nI found that when calling , if we don't pass in the style override anymore, it will be reset to default I put this fix for notebook but I wonder if it's unexpected\nThanks for figuring that out. We shouldn't update options that are not set, that a regression. I fixed that with and updated your code to back what it was. Is different, it's about the indent guides which were disabled previously by not providing any colors. With my change we complete your colors with the default colors, which IMO is the right thing to do. is a simple fix. But I think we should not use the colors for that but the already existing option. I'm working on a follow up PR, but that needs to be reviewed by who is out today."}
{"_id":"doc-en-vscode-bb734d1be7674424aa63c773138b633eb3af32b70a444b7c10a7688a66631c36","title":"","text":"I'm not certain if this is a bug (in the tests), but while looking at the completion ranking I noticed there are some tests cases for the fuzzy scoring annotated with \"direct case match\" that don't appear to match exactly - the order of the lowercase/capital is reversed: It's possible this is deliberate (because VS Code handles some swapped characters), but if so I would've thought an exact match would be included also (to ensure it ranks above the entry with the reverse characters) and the comment would be more explicit. There are other tests in the same file with the same mismatch."}
{"_id":"doc-en-vscode-bc919ee9d8860701309c29261a7fc22654ac5bfdb6be2eb46dbe06bed3877a75","title":"","text":"This clear option can be into the exiting task property and would be called : { \"label\": \"ExampleTask\", \"type\": \"shell\", \"command\": \"echo hello\", \"presentation\": { \"echo\": true, \"reveal\": \"always\", \"focus\": false, \"panel\": \"shared\", \"showReuseMessage\": true, \"clear\": false } } Added to : / Controls how the task is presented in the UI. / export interface TaskPresentationOptions { …. / Controls whether the terminal is cleared before executing the task. / clear?: boolean; }\nThis doesn't work for me: I run it multiple times and see all the output, the terminal is never cleared.\nTurns out that if the only presentation option set is clear, this doesn't work. Thanks for finding!"}
{"_id":"doc-en-vscode-8cf6a0d2b3b69416bfd4497444105f4f9e484466f3119e89abe2b59c08712d69","title":"","text":"<!-- 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. --<!-- 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.76 Steps to Reproduce: Exported a user profile using the GitHub gist link . The user navigates to the link in their browser, where they enter , and the profile opens in the explore view. At the same time, the profile badge is to the settings icon prior to importing the profile. If the user clicks \"Import Profile\", they are prompted to overwrite an existing profile. The user has never imported a profile prior to this experience. !\nthanks for great repro steps. I can nicely reproduce. Assigning to since it seems like the Profile got applied to before hitting the import button, and hitting the import would double-import.\nthanks for fixing can you try with latest Insiders and if it works fine you can add the label. Thanks!\nVerified, however the profile badge gets to the Settings icon and to the Profiles list prior to importing the profile, but if you click \"Import Profile\" it imports as expected. Is this as expected? My assumption was that those would not show up until the Profile is imported. !\nYes. This is to indicate user that the profile is applied in preview mode."}
{"_id":"doc-en-vscode-329290d97705826e71dfcb3497adcf7d074dbe63236aa9dcb4ade93caf3e6055","title":"","text":"Steps to Reproduce: a notebook with a markdown cell that has multiple headers e.g. the preview for the markdown cell - shift+enter symbols quickpick ctrl+shift+o and arrow down through the symbols list :bug: cell decoration appears for the first item but then is removed for the second"}
{"_id":"doc-en-vscode-3dce611628b56abb2682d9a504aa127d9bbd04217e8ff5700001ddaa2cd885de","title":"","text":"<!-- 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.35.1 (also tried current 1.36.0-insider) OS Version: Ubuntu 18.04 VSCode's view seems to show all threads that ever existed, not just the ones returned by latest request. Repro: and run mock-debug extension from this branch: the folder and start configuration. all threads in the thread list and start stepping line by line. After each step the adapter will reduce the number of active threads by one. requests for invalid thread ids will be failed. By line 5, there will be only one thread remaining, yet VSCode tries to display all 5.\n(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.586 --- <!-- score: 0.462 --- <!-- score: 0.461 --- <!-- score: 0.461 --<!-- potentialduplicatescomment --\nmake sure that only the threads returned by the last thread request (plus additional threads coming reported via the \"thread\" event) are shown.\nthanks for the nice repo steps. I have changed that we now always respect the request as the absolute truth. So if a thread is not returned as part of the response we will delete it. I have created a PR which tackles this and I will merge this PR in next week since now we are in endgame and I would like to get more insiders coverage so we catch potential extensions which might rely on the current bugy behavior."}
{"_id":"doc-en-vscode-ccf99ca0df11d76f7747beafa4e8ce852eb81644e1abff66ba9260f97f8da170","title":"","text":"<!-- 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. --- Version: 1.74.2 (user setup) Commit: Date: 2022-12-20T10:29:14.590Z Electron: 19.1.8 Chromium: 102.0.5005.167 16.14.2 V8: 10.2.154.15-electron.0 OS: WindowsNT x64 10.0. Sandboxed: No Steps to Reproduce: a snippet for latex that uses $TMSELECTED_TEXT. The following is an example that wraps selected text in auto-sized brackets: 'lr' over a selected text and hit TAB. The selected text is not included in the output. ! F1 + Insert Snippet, however, produces the desired output. I have only encountered the problem in latex environment, including inline math in markdown files. The issue was raised in and was fixed in 1.73 update via (I think). But came back in 1.74.\nThe problem is the which requires two characters to be typed... This is what happens overtyping happens, we capture the overtyped text, and \"await\" the next suggest session to start this doesn't happen because suggest only auto starts at word ends and a single character is no word the next character is typed, erasing the overtyped, captured value suggest starts because the 2nd character makes this a word looping you in here and wonder if you know why such a word definition was chosen and if it can be changed\nI don't know why the definition specifies 2 characters."}
{"_id":"doc-en-vscode-6e0199b1063bd97959a3b1ac2ef3e4addf3581e4bdd056c6a06a12773d987f7e","title":"","text":"I'm not familiar enough with latex to know if there's a reason for it. Given that no other language does this I would be fine to remove it.\n+1 for changing the word definition. FYO who originally this via\nI confirm that changing the word definition to 1 character is fine.\n<!-- 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!\n/verified"}
{"_id":"doc-en-vscode-5bfa1dc4a59d72f59ae8af86ff760c2b913d0ec01186ddc1c8739f9c2b507d6f","title":"","text":"a folder/workspace in VS Code Insiders a git repository in the folder a file, make changes to it, and create multiple commits Expected: commits should appear in the history graph Actual: no commits are being shown in the history graph\nthis only works when there are multiple commits. I.e. if we has just one commit in the repo, then history isn't displayed. Else works as expected.\nThanks! I have filed to handle the single commit scenario"}
{"_id":"doc-en-vscode-978442ecf6282a9ad61d838beebf927056f82c551cc275d26b42cc95d71ff8b7","title":"","text":"<!-- 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. --Do not see similar issues here: Steps to Reproduce: interactive rebase click tab, \"Copy path\" file picker, paste path path file name from to . This is a file that git uses to track what is done. \"Language mode\" should be \"Git Rebase Message\" but it is not. I am using worktrees, but I don't think this is related, since has proper language detection."}
{"_id":"doc-en-vscode-48d9afdf11be971fd39ecbde2723054296b95bfbca2bb7d77b75e7887815728b","title":"","text":"Testing Insiders dated 28th March, 2017 Happens in linux and windows <img width=\"333\" alt=\"screen shot 2017-03-28 at 11 42 13 am\" src=\"\""}
{"_id":"doc-en-vscode-2c92eb23816863b43b19b0f9101ab0bdfde461beb712dbbf9abfc160bd251509","title":"","text":"My VScode and Cursor are broken since today's update. I can't use 'Run and debug', it doesn't open a terminal for my web app runs. Only runs work. VS Code Version: 1.93.0 OS Version: MacOS 14.6.1 (23G93)\nI have the same issue when trying to run and debug my Electron application. When I change to (or remove since is the default value) I can use 'Run and debug' again. I won't get the output of the main process (only the renderer process), but at least it's working for now.\nsame here, this launch configuration fails to start on macos when using or . it only works if you have or remove the console configuration. VS Code Version: 1.93.1 OS Version: MacOS Sonoma 14.6.1 Demo:\nExactly the same issue with nx and nest, also for some strange reason the breakpoints are marked as attached (red) even when no process is running. Something definitely was broken in the last version, this was working fine a few days ago. Not happening on WSL2.\nwere there any terminal-relate changes here? The on the debug side didn't change in the last release. (Or is there a better way to do things side from a 1s timeout now that shell integration is smart?)\nI'm experiencing the same issues; I can't debug anything in NodeJS/TypeScript. This started happening after I updated to MacOS Sequoia. The only way to make it work is if I set the value to the property in the . However, that's not the desired behavior. After a few hours of testing, I managed to make it work —although it's not the ideal solution— by adding the property with the value . Additionally, I with the value . In summary, I have the following configuration:\nYour case probably duplicates\nNothing comes to mind around recent changes to terminal launch, apart from a different path for SI scripts. The better way to run command is to use shell integration is it's available. There's no helper function for it just yet though. do you know what that issue was we were discussing a helper?\n<!-- 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."}
{"_id":"doc-en-vscode-5a62e34526a4c94af82e5a12eef3fb01b19826a7fc8a01a074630913523d0acd","title":"","text":"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!\nLooks like it's solved. Waiting for the official release so Vscode + Cursor will be fixed.\nfyi I think cursor is quite a bit behind vscode so I would not expect it to be fixed there soon\nWeird, the issue was immediate on both ides a week ago.\nMarking as verified due to confirmation."}
{"_id":"doc-en-vscode-09d4803916b01614d7c67a4d42ad13c2c2fece96842282b7f94d876e114fb212","title":"","text":"The rulers and indent guides do not display well on high pixel density displays VSCode Version: Version 1.21.0 (1.21.0) OS Version: macOS Sierra 10.12.6 (16G1212) Steps to Reproduce: out editor Does this issue occur when all extensions are disabled?: Yes Example !"}
{"_id":"doc-en-vscode-42949ae023af4ebdd70106c0934d31b7f23abe318b6a4edec46a74a11c436100","title":"","text":"Testing The feature is called . But it does more than fetch, it also pulls. Fetch typically only 'downloads' commits, but does not update any branches. Maybe the proper name would be:"}
{"_id":"doc-en-vscode-3980a748d8db942ba9e95d7b094184a3f12f305251c18340dc225d766f93c29c","title":"","text":"It doesn't matter in this case, but note that you collect all the keyListener disposables in the store of the AccessibleView class (even if you dispose them in , but the disposable is still in the disposableStore). This can lead to memory leaks. I can really recommend to compose components according to their life times. I think here the lifetime of the rendered content is owned by the caller of (the caller is supposed to call on the result). So the disposable returned by should be owned by whatever you return in . I suggest to create a DisposableStore in render, push the key listener to it once the text model resolves and return the disposable store at the end of render (also add the to the store). Also, note that the getTextModel promise can resolve after the caller called dispose. Originally posted by in"}
{"_id":"doc-en-vscode-74bfa4cfc62a21d6e2f220c178b5eedb1fe6a1a8547e0d468fba95e2d8c5151f","title":"","text":"<!-- 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. --Steps to Reproduce: long variables that cause scroll them that the scrollbar gets in the way of the \"relaunch terminal\" button"}
{"_id":"doc-en-vscode-dc151700b6d5e44272c9fdd7e831f1f7e050e87c5559b9ff82722e5f08086e6a","title":"","text":"We have a setting to disable the settings split view, but it might be useful to have a command to open the user outside of the split view for a one-off. From\nI am reverting the PR, it actually doesn't work. We intercept the editor open here:\nDamn, it's already a part of my workflow . What's wrong with it?\nSo it opens the raw outside of the split view for you? For me, it actually just acts the same as the normal open settings command and opens the settings split view.\nAnd you don't have ?\nI don't have . The command itself works for me. Does it break some other functionality? ! OS version: Windows_NT x64 10.0.\nI see now. Opens a split view on linux VM. Was it ever working before on non-Windows environments?\nYeah it only works on Windows, because the == check with fspath can fail due to drive letters being different. I guess that's a separate bug... I'll revert this tomorrow.\nWe got a good bug out of this:\nNow that the settings UI exists, I don't plan on investigating much more on the JSON editor. The split JSON UI will probably go away at some point (the JSON files themselves will always remain)\nBUT I CAN'T OPEN SETTINGS FILE (WITHOUT SPLIT) NOW AT ALL BECAUSE IT'S NOT LETTING ME. Are you planning to allow users to see plain json file or to forbid it completely?\nWe will always allow users to see the json file. Hopefully you can still open the raw json file with .\nI know about that option, it's not great.\nI'll close this just because I am cleaning up issues that are specific to the JSON split editor. But to be clear, editing the JSON file will never go away :)"}
{"_id":"doc-en-vscode-88aa6284b784bd90522980d1e97d27273eaf7c49062ae7b6433ca44f01947a53","title":"","text":"Add the following settings into user settings Create a Notebook (e.g. github issues notebook) Add a few cells, run (its ok if there are failures) Save and stage the notebook Make changes to at least one of the cells View differences using Notebook Diff view You'll notice that the screen flickers, This is because the heights of the cells are computed by taking the height of output & metadata sections After a few ms, these are hidden and the cells move up a few pixes.\nhit this and wasn't able to test:\nShould be available for testing with next Insiders, thanks1"}
{"_id":"doc-en-vscode-94f5c23a56e08fa6bcf46ebf09d84a23b3854a3b4e6e55b2a615055440588789","title":"","text":"<!-- 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.81.0-insider : : 2023-07-12T11:13:11.418Z : Mozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 OS Version: Mac os 12.2.1 (21D62) Steps to Reproduce: Configuration Display Language to . devtools after page auto refresh !\neg. does not exist, but exists.\nthanks for working on this. The true fix for this issue actually needs to be in 's source code. I've made that fix and this should work for you now. Let me know if you still see any trouble."}
{"_id":"doc-en-vscode-f21de36281c22ea994c021ac4420b1913fbbe778b2f8a633c94e771e7bf5f74e","title":"","text":"<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --Executing \"Surround with snippet\" from the command palette while there's no surround-able snippet, results in an empty pick list: ! Shouldn't it be like showing an information message saying there's no snippet to pick, or just not prompting the user to pick anything?\nPrompt might be too annoying but quick pick itself might have a way to show a lightweight in-place message\nDo you mean something like this (using )? !\nJust submitted the PR. Could you please check it?"}
{"_id":"doc-en-vscode-bbeb85c2b875a5dc7cec68af01cc21bf173d85ed4ba3fb893c980bd13ccd5ea5","title":"","text":"CC In , you type something in the input field and hit enter. When search result pops up, you need to press tab key tediously mutiple times to land in the search result treeview. It would be better if the search result tabindex could be adjusted so that users can quickly jump into the treeview after providing the search term (e.g., pressing from the search input field goes to the result treeview). Another way is pressing key in the search input field moves user focus to the search result treeview directly. Version: 1.78.0-insider (system setup) Commit: Date: 2023-04-04T09:32:52.453Z Electron: 22.4.3 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0. Sandboxed: Yes\nThe latter option is preferred for a screen reader user's better navigability.\nwhat do you think of this suggestion?\nYou can press ctrl+down/up to move between the input and the tree immediately, does that help? I don't quite understand the suggestion, that the tree come before the search input in the the tab order? And with pressing enter to move focus to the tree, I think that doing multiple searches while tweaking your search query is a common workflow, and this would interrupt that, but maybe something like that could be configurable.\nIf you want to jump directly to the results, you could add a keybinding like The command will focus the results view.\nand -- Thanks for sharing great tips! I did not even know that I could use Ctrl+Down/Up Arrows. This is working very well. -- I think this is now a \"discoverability\" issue. I recommend adding an aria-label or other similar techniques to remind screen reader users of these Ctrl+Down/Up key commands.\nI did not know that either, so agree that this is a discoverability problem. does it make sense to you to add this hint to the ?\n<!-- -96bd-47a8-a0e8- --This feature request is now a candidate for our backlog. The community has 60 days to the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it."}
{"_id":"doc-en-vscode-c5197042be733320932ab633da176566728606ddf165f00162c0b770fa3d8adb","title":"","text":"To learn more about how we handle feature requests, please see our . Happy Coding!\nYes, I could add it as an on the search text box. Is there an example elsewhere that I can follow in terms of adding a hint?\nHere's what we do for the terminal's\nI have found that Ctrl+UpArrow does not work when the keyboard focus is on the last item in the search result. Ctrl+Up only works in the first search result item.\nThe context key is why it only works for the first item: . Removing will do what you want\n-- Shouldn't it be removed by default for other users? It does not make sense it only works in the first item if we want to generalize this behavior.\ndo you know why was applied here?\nI'm guessing that it's because users wanted a keybinding that allowed them to move to the query fields when there were no more results to see. do you happen to know why it's like this and whether we can remove the check for ?\nThat keybinding also does other things- on mac. I didn't want to interfere with normal list keybindings. If this would be really useful, we could add a new keybinding which doesn't have that context key? Or users can customize it that way for themselves too?\nOn mac when the search results are focused, does not do anything.\nIt works for me\nAh yeah I see it working now. hb as it seems like it is more important to be able to get back to the search box in this case than to scroll one line up?\nI think I'd rather leave the typical list navigation commands alone, but if it's just behind tbh I'll defer to you. But I also remember that the ctrl+shift+F shortcut should just focus the search input too, if that helps.\nSince is a pattern we use elsewhere and screen reader users already have a high cognitive load placed upon them, I think we should follow suit here behind that flag.\nTo verify: With , search for something, navigate in the search results, and use to return to the search input fields"}
{"_id":"doc-en-vscode-8d97a9980799d25d618b421fda017a74c15b95b6fc39dbccb58e25c30fecc41b","title":"","text":"An information disclosure vulnerability exists in VS Code 1.71 and earlier versions. If an attacker is able to run arbitrary scripts inside of a webview (either created by extension or by core VS Code), the attacker could bypass the local resource roots check to read arbitrary files on the user's system The fix is available starting with VS Code 1.71.1. The mitigates this attack by performing input validation on the URL pointing to the repository to be cloned. Only use webviews from extensions that follow proper security measures to block script injection Do not disable VS Code's default security measures in the built-in markdown preview The patch for this can be found at An advisory for this can be found at MSRC details for this can be found at\nHi, just curious about this: The description of the vulnerability ends mid-sentence. I see the same phrasing on the GHSA advisory as well: Can it be revised to be clearer what is the nature of the vulnerability? (And of course: Thanks for finding and fixing it, and for making these advisories! Transparency and security are appreciated!)\nUpdated\nShould the references to 1.71 in fact be 1.72?"}
{"_id":"doc-en-vscode-3bea2ad55f3a165ca62b5bacb062d7215b77f2dc35912ae19cec3ff7e9be5564","title":"","text":"VSCode Version: Code - Insiders 1.12.0-insider (, 2017-04-13T06:10:58.128Z) OS Version: Windows_NT ia32 6.1.7601 Extensions: the listing exceeds the lower minimum of browsers' URL characters limit Steps to Reproduce: any file and try to horizontal scroll either via mouse wheel or shift scroll.\nHello i'm still experiencing this issue , I've noticed a separate issue was closed for Ubuntu users, but still noticing this with Windows.\nThis seems to be fixed in the latest release.\ncorrection, this issue still exists.\n/cc I'm seeing this issue again as well, on my Ubuntu work machine and on Windows: VSCode Version: Code - Insiders 1.12.0-insider (, 2017-04-21T06:12:00.370Z) OS Version: Windows_NT ia32 10.0. Extensions: ;\nSome more info: shift+mouse wheel does not work, however when I use the trackpad and two finger swipe horizontally it works fine. Unplugging and plugging in the mouse again didn't fix it.\nHmm the trackpad usually is for forward and back commands. I can confirm this is the same case for me. I'm wondering if electron has switched the forward and back commands for the horizontal scrolling. Because in my mouse settings if I set the horizontal scroll will to page forward and backward it works perfectly. But I shouldn't have to do that.\nI tried to reproduce and failed with my setup (Windows 10 and Windows 7 on macOS running in Parallels). Here is what I try: shift-scrolling in the editor wheel-left/right in the editor ! Are you doing something different? Does it reproduce when you run with blank settings?\nI tried to reload vscode insiders without any settings, and i'm still having the same experience.\nOne other note, I have mac os sierra at my home workstation and everything works perfectly there. It seems to be Windows specific. I'm running Windows 7\nHere are errors and warnings upon restarting insiders without typing anything. I wonder if this has anything to do with it.\nI assume those warnings would go away when you run code . I would not assume however that this would help you for this issue, but worth a try anyway.\nI wonder if we could do a little experiment."}
{"_id":"doc-en-vscode-e0ab04c49df3e8c5850e65be680a272cfd329ba5e6bb9924e268fea8cd0e0f92","title":"","text":"Can you: download run it from the window that opens make it small enough that horizontal scrollbars appear see if you can scroll ! If so, this would point to a general problem with our UI framework (electron) and we should report it there.\nseems to be this line that's throwing an error which may be causing the scroll to not work.\nI would think that is unrelated, but please follow my steps to find out more.\nI downloaded () on the Linux machine that I can reproduce it on and I can scroll just fine. ! Note that after this gif I updated to latest and it still doesn't work on:\nSorry I didn't see your message until just now. Yes it scrolls fine. On Mon, Apr 24, 2017, 10:31 AM Daniel Imms <:\nneed your help here for more debugging. First thing that comes to my mind is to add a breakpoint into  to see if this is even triggered when scrolling horizontally?\nit's hit, but is set, not as I would expect. ! is set though: ! Are we meant to handle manually?\nany chance you could debug stable to verify that e.deltaX is set? Is there any other property that has an increasing value? /cc if you have any clues on this Looking for chrome issues I stumbled upon:\nFixed via\nThank you guys, very much appreciated. Have realized over the last few days just how much I depend on horizontal scrolling.\nAs i'm not familiar with the insiders release pattern, any idea when we can expect this to come down the pipeline ?\nshould be in tomorrow's Insiders build\nThank you Daniel Imms <:"}
{"_id":"doc-en-vscode-86c3195eb4c0bbe54150bdbb712db75eb14315ee1914fbe60643c04c41e6b5e1","title":"","text":"In order to create custom keybindings to toggle focus between the editor and something such as the terminal panel, a command to focus the active/most recently used editor group needs to be . I believe this is the best that can be accomplished currently: Focuses the first group, meaning if the second or third editor groups were focused this would feel wrong: Or this which focused the most recently used editor group but opens the last editor/file in the group: Some context on request:\nisn't that as easy as providing a global command that just puts focus into the active editor? E.g. ? PR welcome if you wanna give it a try.\nyes, I expect it to be pretty easy.\ngot a better name than ?\nworks for me"}
{"_id":"doc-en-vscode-182fdf7dde27a0e5cc30bfda230b155ed287accc6cd3b32dd848896f1880bed8","title":"","text":"Testing I found \"Find in Cell Selection\" confusing label for the button given it is to find in selected cells. Does it make sense? Would \"Find in Selected Cells\" be a bit easier? !\nYeah, agreed that the labeling isn't perfect. Will workshop this in the next iteration, as this button will be serving dual purpose as a way to search in textual selections within a cell, as well as searching in multi-cell selections as the feature is currently. Thanks for the feedback!"}
{"_id":"doc-en-vscode-728c17f924469524a511b3b2c2ddcbb5527d26b05bf2e374be8d6f98dd108fe5","title":"","text":"Notebooks: ! Editor: ! Version: 1.90.0-insider Commit: Date: 2024-05-28T05:48:32.492Z Electron: 29.4.0 ElectronBuildId: Chromium: 122.0.6261.156 20.9.0 V8: 12.2.281.27-electron.0 OS: Darwin arm64 23.4.0"}
{"_id":"doc-en-vscode-387d7bfa310d3b5e7fd45860bd90d4fe55f4414bf29c0d3ee325ebdd05a9da46","title":"","text":"Type: <bBug</bThe default width feels small, especially that we have 4 icons in the notebook find widget. It can only render 6 characters and then truncate. ! VS Code version: Code - Insiders 1.88.0-insider (, 2024-03-28T22:10:25.599Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (27)</summaryExtensionVersion ------ esbuild-problem-matchers0.0.3 vscode-eslint2.4.4 vscode-deno3.36.0 gitlens2024.3.2805 EditorConfig0.16.4 prettier-vscode10.4.0 copilot1.176.0 copilot-chat0.14. vscode-pull-request-github0.85. vscode-mocha-test-adapter2.14.1 vscode-test-explorer2.21.1 vscode-dotnet-runtime2.0.3 black-formatter2024.1. debugpy2024.2.0 isort2023.10.1 python2024.3. vscode-pylance2024.3.102 datawrangler0.29.6 jupyter2024.3. jupyter-keymap1.1.2 jupyter-renderers1.0.17 vscode-jupyter-cell-tags0.1.8 vscode-jupyter-slideshow0.1.5 remote-containers0.353.0 extension-test-runner0.0.6 test-adapter-converter0.1.9 vscode-github-issue-notebooks0.0.130 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --"}
{"_id":"doc-en-vscode-e2e45faed0ca3308be388044453b703b2d59622ef22342a7f5f4bbc96deec710","title":"","text":"<!-- Please search existing issues to avoid creating duplicates. --- VS Code version: 1.59.1 Extension version (available under the Extensions sidebar): v2021.8. OS and version: Linux x64 5.13.11-1-MANJARO Python version (& distribution if applicable, e.g. Anaconda): 3.9 Type of virtual environment used (N/A ...): virtualenvwrapper Relevant/affected Python-related VS Code extensions and their versions: pylance v2021.8.3, jupyter v2021.8., Visual Studio IntelliCode v1.2.14 Value of the setting: Pylance from the VS Code marketplace to see if that fixes your issue] Extension loads successfuly Extension does not load, console reports \"Unexpected token ' in JSON at position \" [NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue] the extension by clicking a .py file <!-- Note: If you think a GIF of what is happening would be helpful, consider tools like , or . --<details<summaryOutput for <codePython</codein the <codeOutput</codepanel (<codeView</code→<codeOutput</code, change the drop-down the upper-right of the <codeOutput</codepanel to <codePython</code) </summary<p</p</details\nLooks like you might have a bad update. Do the following to remove stale versions of the extension: Python extension (if you have pylance uninstall it first). all instances of VS Code. to, (on windows) or on Linux/Mac. any folder with the name starting with VS Code, and install Python extension (also pylance if you uninstalled it in step 1).\nI followed all steps, but nothing changed. should I try to install older version of python ext?\nHi Can you try installing an older version of the Python extension, and if it doesn't work can you try a different version of VS Code (either an old one or the Insiders build)?\nI've installed python extension , jupyter and no pylance. here's the log: As you said I'm going to install older version of vscode\nHi Did you try installing an older version of VS Code?\nFYI - This looks like some JSON stored via the became corrupt."}
{"_id":"doc-en-vscode-72279de425cd06acf2e0c631319272da5f5183a45abd7945c4d7527807b3c555","title":"","text":"The JSON is written a few lines lower, so it is unexpected that the value is corrupted. This might indicate some kind of bug in the storage layer. I don't remember writing that code, did you perhaps write that? Do you think it is so important such to fail extension activation when the JSON is corrupt, or should we catch that exception and return ?\nI would suggest to be more resilient in extension activation as you suggest and fallback to an empty object here if any error rises from but log it as error: This is the first time I hear about a problem with persisting data into SQLite. However, seeing makes me think that this is not an officially supported Linux distribution.\ncurious if you could share the following 2 files with me (via e-mail is fine: find it on ). Steps: open the VSCode window where this issue happens View Command Palette =Log Storage Database Contents Help Toggle Dev Tools Find the 2 paths for the DBs send both files to me\nI can still see the original issue in vscode-insiders v1.61.0-insider\nwhats the exact version you are on? And is it the issue that the extension fails to activate?\nVersion: 1.61.0-insider (user setup) Commit: Date: 2021-09-16T08:31:28.161Z Electron: 13.4.0 Chrome: 91.0.4472.164 14.16.0 V8: 9.1.269.39-electron.0 OS: WindowsNT x64 10.0. python extension: v2021.9. Error 2021-09-16 17:51:12: Error discovering pytest tests: [SyntaxError: Unexpected token S in JSON at position at (<anonymous) at a.runTestDiscovery (PATH.vscode-insidersextensionsms-outclient) at runMicrotasks (<anonymous) at processTicksAndRejections () at async (index 0) at async _.refreshTestData (PATH.vscode-insidersextensionsms-outclient) at async v.refreshTestDataInternal (PATH.vscode-insidersextensionsms-outclient)] { stdout: '[{\"rootid\": \".\", \"root\": \"...\nI fixed the issue as reported in that extensions fail to activate when the contents in storage fail to get parsed."}
{"_id":"doc-en-vscode-9c2863ade4be33e8f4b9f9c58e071f91eb45064e93fa616af3479904c31dc062","title":"","text":"What you report here seems different to me. Looks like the python extension is calling on something that is not valid JSON? Have you asked the Python extension what this could be?\nI see, I'll create a new issue. thanks"}
{"_id":"doc-en-vscode-c9a6d85706d46e7e70efa0198b443f89d5897e5c2d250a91b6027e3136aa4d52","title":"","text":"We support for auto-populating selected text to quick search (), but setting overrides this. This is because takes precedence over any default string (even if is defined). (from )\nTo me, this feels backwards... I'd want whatever was passed in to take precedence... and only if the default is set to the default value (aka the prefix) should the LAST be restored. was there a reason for this behavior that maybe I don't know about?\nI do not remember. I assume you already bisected this to the origins?\nthe origin of this change came from: I now understand why this code behaves like it does. It's because it's provider (& prefix) agnostic. This code actually knows nothing about the prefix and nothing about the provider except the last accepted value per-provider. So basically, it's up to the caller of to say no don't .\nI've sent a PR that makes the search one work as we expect.\nverif steps: command, then search for some text and select one of the results. step 2, but make sure that the input that previously had is retained once you run the command. something in the pick to close it, then highlight some text in the editor. again. You should see your highlighted text in the input box."}
{"_id":"doc-en-vscode-c817020d68f8357b26b9c78d61456b8cb4ae88c059361b5e4b945c87ca1b19e2","title":"","text":"<!-- 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. --Steps to Reproduce: rename on a top level file element in explorer view in single folder workspace in developer tools that the div for that file row contains multiple invisible children elements which are input element containers !\nI can not reproduce this issue on my machine. How do you end the rename, with Esc, Enter or some other way? Are you doing anything else that is special?\nI just press continuously. I can reproduce this easily on linux(ubuntu) and windows. The setup it's just a folder with a single file and I drag and drop the folder on vscode.\nYes I can reproduce now.\nThis might happen again on tomorrow's vscode insiders. Thus unlocking converstaion so we can open this issue if needed.\nYou are right I can repro this again."}
{"_id":"doc-en-vscode-f82c4e0dd6e84c2c90c28f703491c648ac71859a731376ff3d01554945587632","title":"","text":"Issue Type: <bFeature Request</b The Test Explorer filter should be preserved if a window reload occurs, rather than resetting to default. This behavior could be gated by a setting. ! VS Code version: Code - Insiders 1.65.0-insider (, 2022-02-16T05:16:18.653Z) OS version: WindowsNT x64 10.0. Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (32)</summaryExtensionVersion ------ vscode-color0.4.5 vscode-opennewinstance0.0.12 gitlens11.7.0 filter-lines1.0.0 EditorConfig0.16.4 prettier-vscode9.2.0 copilot-nightly1.7.5030 remotehub0.24.0 gc-excelviewer4.0.50 todo-tree0.0.215 vscode-drawio1.6.4 change-case1.0.2 vscode-peacock4.0.0 git-graph1.30.0 vscode-azurefunctions1.6.0 vscode-azureresourcegroups0.4.0 vscode-docker1.19.0 remote-containers0.222.0 azure-account0.10.0 powershell-preview2022.2.1 indent-rainbow8.2.2 docthis0.8.2 pester-test2021.10.2 vscode-commons0.0.6 vscode-yaml1.4.0 vscode-inline-values-powershell0.0.5 errorlens3.4.1 vscode-icons11.10.0 codetour0.0.58 gistfs0.3.0 gitmoji-vscode1.0.9 better-align1.1.6 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nThat makes sense.\nI'm still able to reproduce this with the latest mainline build. May I pick this up since it's still open?\nSure!"}
{"_id":"doc-en-vscode-06f87dd869038d880bd200c77aaf0063165053e281ea64b5d9cf23d9aa8e0616","title":"","text":"re see\nsame for\nSame is true for Wanted to reuse the issue but didn't read all comments. Ignore mine. already mentioned it.\nI'll change them to ,"}
{"_id":"doc-en-vscode-38adbb4c21fe456f77fa631b1196323685b169240cfffd55e4913edb57d8ddd7","title":"","text":"When a quickpick has more items than can fit into the initial list, it's not obvious there are hidden items that need to be scrolled into view. The current visual treatment is a very subtle scrollbar flash when the quickpick is first opened, but thereafter there is no visual indication that there are more items. The current behavior presents issues for the remote indicator menu, which displays actions from all installed remote extensions (connect to host, create new codespace) etc. The remote indicator menu is meant to improve discoverability and ease of access to remote actions, and the current truncation inhibits discoverability of those remote actions. Proposals: a arrow button at the bottom of the quickpick when there are items offscreen which will scroll down to the next 'page' of items when clicked render the scrollbar\nLooking at prior art here: Slack ! Spotlight ! GitHub ! Teams ! Alfred ! Docker ! One thing I'm noticing is that some render the height as the middle of an item... which is an indication that there is scroll. Not sure if that is intentional or not, but it would be something that we have control of. While the is a neat idea, I fear that it will be in the way while reading the item it is on top of... My preference is either render the scroll bar... or maybe do nothing since the \"command palette\" experience can be seen across many products and most if not all allow scrolling.\nOh, I wanted to point out that the scroll bar does flash today: ! and if your mouse is hovering over the list, the scrollbar sticks around. This feels like enough of an indication that there's scroll.\nInstead of rendering it atop an item, what if we rendered it below all the items in the quickpick?\nDo you not think the flashing scroll bar is enough? The Explorer does this too.\nI don't think it's enough, particularly for the remote indicator scenario where you're triggering it by clicking the status bar--there will be a brief flash when it's first opened, and if you then use up/down arrows to navigate through the list, you don't see the scrollbar.\nIs this a hunch or based on user feedback? I talked to a bit about how the fading went when we rolled it out everywhere and there were some issues opened: not scoped to quickpick but rather holistically."}
{"_id":"doc-en-vscode-ff34f72bc393c8c559c62a5c270fa1d0dfaf59cc1aa8f5efa07d9f4462f98db8","title":"","text":"We have settings to control the behavior but only in the editor I guess: ! in terms of proposal 1 for scrollbar visibility, I feel like the issues I linked are a better holistic way forward. As for the ... I'm not sold. Either it makes the quick pick taller (just for a little arrow) or it covers up content.... plus I couldn't find a single quick pick example in the wild that takes this approach.\nI think it's fair to consider a global treatment for scrollable content as you say, the linked proposals look promising.\nProposed solution: increase the by a little bit so it renders like: !\nsteps to verify: open the command palette it should render in the middle of the item (like my last screenshot) to indicate that it does scroll"}
{"_id":"doc-en-vscode-6947b48c85bbda020300deb1a5ec0302f3ea85b5972b669f66fbd0d1dd710d99","title":"","text":"<!-- 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: master Ran into this issue while preparing Monaco release in vscode repo open monaco-editor test page switch monaco-editor-core source to not found error in Dev Console is registered through which is only read by workbench We can add the singleton services to standalone but a simple standalone service can also fix the problem <img width=\"576\" alt=\"image\" src=\"https://user-\" let me know if you have time for a quick fix, if not I can push my change to branch first to unblock publishing.\nFYI is also made to ensure work at this moment. Unluckily our intermediate typescript files for tree shaking don't apply to yet. The commit will be cherry-picked to master later.\nThere is no need for , the default implementation is good enough and just needs to be brought into the editor land.\nplease review\ncan you clarify the steps for this? I'm not sure where the monaco-editor test page is\nI can take this one"}
{"_id":"doc-en-vscode-82aa6915b02ea2eb8934fd299c412fff66640373da2adda5be0bf1ac9e0c3877","title":"","text":"<img width=\"642\" alt=\"image\" src=\"\"\nHow do you repro this? We don't show the hint for readonly editors:\nan file 1 -My guess is we don't re-evaluate the change"}
{"_id":"doc-en-vscode-bc3efd8a6a6bc385974a185c7c3f52a4bf9c060e1923686bb5904d5b38702183","title":"","text":"Users that don't want automatic updates should still be given the opportunity to stay in the same version. ping"}
{"_id":"doc-en-vscode-2f5fe5cb0bfaf760153b2b9fecd1d8411935160ed0dd3196f5ba1c64afa6426c","title":"","text":"<!-- 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.76.0 OS Version: macOS 11.6.2 Version: 1.76.0 Commit: Date: 2023-03-01T10:23:45.993Z Electron: 19.1.11 Chromium: 102.0.5005.196 16.14.2 V8: 10.2.154.26-electron.0 OS: Darwin x64 20.6.0 Sandboxed: No Summary When creating a profile with a name such as \"Typescript / Javascript\", the following happens: When exporting as a Gist, no result dialog shows (\"there was trouble\" / \"created profile successfully\") and a validation error is outputted in the logs When exporting to a local file, the text after the last forward slash is set as the filename. With the above example, it'd be \" \" To reproduce: a profile: Settings cog -\"Profile ([...])\" the profile: Select \"Export Profile...\" -\"Export\" the \"name the profile\" step, enter a name with a forward slash in like so: \"Typescript / Javascript\" either method for exporting: gist or local Expected results: If you select local: a system save prompt with the name you entered pre-set in the filename field If you select gist: A success dialog with a link to the website prefilled with your config Actual results: If you select local: only the text after the last forward slash is in the filename field If you select gist: No dialog shows."}
{"_id":"doc-en-vscode-a370a5319b36cbff23f07c89c57579acee75b24f6e2611b1661edc65c63014fb","title":"","text":"The following error is in the \"output\" window, under \"Window\": I can only test this on a macOS device, I haven't tried this on a Windows or other Linux device and I feel like (with the area in mind - filesystems etc) these issues could manifest differently or not even be an issue there. I'm assuming validation on the inputbox for the name will be required because filesystems (and Gist? not sure) don't typically support forward slashes in file names. Thanks and if you're reading this, have a great weekend :)\nGists do no accept in the name. Replaced with ."}
{"_id":"doc-en-vscode-87013af1ca20894d607305f7e924b22b83d98948f139c847a3aef6b438fef763","title":"","text":"Currently the hover disappear as soon as the mouse leaves the content hover. Sometimes the user leaves briefly the content hover. The ask is to wait until some times (ex. 500 ms) has passed before measuring whether the mouse is within the hover or not, then make the hover disappear or not.\nThis would be quite helpful in resizing the hover (because it's easy to go out of the hover when aiming for the angle to hover with a mouse). But I would think 500 ms is too much for that use case"}
{"_id":"doc-en-vscode-81f74b47a8a5e1849ac6478f56b0171966ec3fc451b16984dfea827100f8a699","title":"","text":"Testing When find box is not visible and I just type but there are multiple results, then maybe allow me via keybindings (F3?) to go to next/prev result?\nYou mean using the type navigation feature? I think this would be too implicit. I don't know of any other native widget doing something like this.\nI think the editor has a way to navigate in find results even without showing find. i think in that mode it only puts the search toggles up in a little overlay.\nThe editor opens up the widget once again, when pressing <kbdF3</kbd. Yeah we can do that.\nI think the tree does the same, I had tried and it showed the input box, but it was empty though.\nYeah. Renamed this to remember the input across usages, which is what the editor does."}
{"_id":"doc-en-vscode-eb5b7151e28477a6887fe4a4eff901022bbd5cda66e1d31b085eb04beb61df96","title":"","text":"<img width=\"285\" alt=\"image\" src=\"https://user-\"\nstrange as 1000 is a number <img width=\"1060\" alt=\"Screenshot 2023-01-20 at 3 28 32 PM\" src=\"https://user-\"\nvalue is here, not sure why <img width=\"1246\" alt=\"Screenshot 2023-01-20 at 3 34 09 PM\" src=\"https://user-\"\nOh, changed the default value to 10 and it worked. I think 1000 is viewed as too high somewhere so it gets set to '' <img width=\"1052\" alt=\"Screenshot 2023-01-20 at 3 39 55 PM\" src=\"https://user-\"\nalso tried because some other settings w high default values use that and it still didn't work\nI some logging and it's because converts it to , and then the inputbox doesn't know how to handle the comma"}
{"_id":"doc-en-vscode-916c451f05087dac3a8c802144f0a81d7a222dfc21918c7335bc5230ffcbcd15","title":"","text":"! should align more with <img width=\"672\" alt=\"image\" src=\"https://user-\""}
{"_id":"doc-en-vscode-4fc668b21de0762b5103ecfa0ddf505044447a39d12f3afa2cf659d88d977f8c","title":"","text":"When using the new diff editor with enabled, I very rarely get to the right editor position whenever I click the top action, above the editor.\nYou mean go to reference is broken?\ndiff editors have an action to open the original file (I think contributed from SCM?). When clicking that, expectation is that the current view state of the diff editors right hand side applies to the opening editor so that you stay in exactly the same view state (for example: the selection and viewport). <img width=\"140\" alt=\"image\" src=\"\"\nI really like the collapsed diff editor but this is a very frustrating regression from it which makes me want to shut it off. The issue is 100% reproducible in my usual workflow and I encounter this issue many times per hour.\nI can reproduce. The \"Open File\" command is a mystery to me. Debugging shows me that is called twice, but both times with unhelpful stack traces: ! ! The second invocation sets . However, there is no reveal mechanism.\nFurther investigation showed that the \"Open File\" action is actually implemented in the git extension (even when comparing two files on disk) :/ Which I think is very questionable design, as it should be a core diff editor feature."}
{"_id":"doc-en-vscode-e5edf67589e7aa701a5c9965deacece62f913c5a3bc765681e22bb3ffe03f34d","title":"","text":"Today when running out of sources and/or building, we get some components from online resources such as GitHub or our Marketplace. We should add SHA256 checksum verification to these: [x] [x] built-in extensions [x] electron\nAdding the foundation for this for and extensions in"}
{"_id":"doc-en-vscode-567ed468ae5fb5401c2599023c7cca6c8bc5b79a42f68ae41486f95392f07474","title":"","text":"Type: <bBug</bExpected: ! Actual: ! Steps to Reproduce: a file. one configuration for any language. in ${} block and intellisense doesn't provide proper hints. More Info: bug is likely related to and . bug can be reproduced in 1.79.0-insider. VS Code version: Code 1.78.2 (, 2023-05-10T14:39:26.248Z) OS version: Windows_NT x64 10.0. Modes: Sandboxed: No <!-- generated by issue reporter --\nGoing way back to , this change seems right since the configuration-editing extension has contributions for these languages but the extension doesn't actually activate unless I add explicit activation events. I can't figure out why the auto activation event isn't kicking in?\nOh, sorry--we revised the event to only do auto activation if the extension also contributed a language definition for that language, since otherwise this led to extensions like Python being activated too eagerly. For debug we should restore the explicit activation events too.\nI see, thanks"}
{"_id":"doc-en-vscode-72c5a6a7934f97a9657c163e3fbfd748a8f415ab1de1aafb9556a18a8536c0ce","title":"","text":"I notice that when I edit our 1.9 release notes, the markdown preview seems to jump up and down all the time there is a change. Compared to 1.8 stable, this seemed to not happen.\nBetter, I still see flickering that it jumps up and down a little bit and the decoration to the left to show me the current edited location is also flickering. let me know if I should open a separate issue on that or if you think that is fixable.\nThe flicker should now be better than VSCode 1.8, but we can still do better. I've noticed the same sort of slight flicker on images in particular and on the current paragraph indicator as you noted. Please open another, lower priority issue so that we can track further improvements Thanks"}
{"_id":"doc-en-vscode-0199f63a23eaf60acf3aed6c67224bcd291a8f2c73331b52d96fc24a56014562","title":"","text":"Build:\nHit this again with\nAgain:\nis trying to get more details when this happens:\nAlso saw this\nThis is because of atomic writing and in windows renaming is failing sometimes and I think this is because some other processes (defender ) might be holding the file that has to be renamed. I have seen similar issues in extensions when I implemented atomic installation of extensions long time back, ie. extracting the zip to a temp file in the same folder and renaming it. I have to retry renaming multiple times to avoid this. I am not sure if this is the right solution for FS atomic write. So, I would wait for until then I will revert my atomic write changes.\nCheck this issue - This is common in windows and it seems the workaround is to retry.\nshould the skipped tests be restored, I think they are still skipped\nSeems like they can probably be restored."}
{"_id":"doc-en-vscode-a3105b894db5ce1f31f1653b2ec4ba76bd1d4cb6536b9b95d76e1ed2cb91ee87","title":"","text":"Type: <bBug</bcc: Since Friday the 3rd, I have not been able to access the terminal accessibility buffer in my linux environment. I activate a terminal and am informed by orca about accessibility in the terminal. But pressing shift+tab does not move the focus to the accessibility buffer. Am I doing something wrong or has something changed from day 3? VS Code version: Code - Insiders 1.77.0-insider (, 2023-03-06T05:21:55.128Z) OS version: Linux x64 6.1.14-200.fc37.x8664 Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<details<summaryExtensions (39)</summaryExtensionVersion ------ doxdocgen1.4.0 vscode-markdownlint0.49.0 vscode-chatgpt3.9.4 rest-client0.25.1 better-cpp-syntax1.17.2 azure-pipelines1.208.0 vscode-docker1.24.0 csharp1.25.4 vscode-dotnet-runtime1.6.0 vscode-kubernetes-tools1.3.11 remote-containers0.283.0 remote-ssh0.99. remote-ssh-edit0.84.0 azure-account0.11.3 cmake-tools1.13.45 cpptools1.14.4 cpptools-extension-pack1.3.0 makefile-tools0.6.0 powershell-preview2023.2.1 remote-explorer0.3. vsliveshare1.0.5832 oracledevtools21.5.0 fabric8-analytics0.3.6 java1.16. vscode-xml0.25. vscode-yaml1.11.0 sonarlint-vscode3.15.1 cmake0.0.17 intellicode-api-usage-examples0.2.7 vscodeintellicode1.2.30 vscode-boot-dev-pack0.2.1 vscode-spring-boot1.44.0 vscode-java-debug0.49. vscode-java-dependency0.21. vscode-java-pack0.25. vscode-java-test0.38. vscode-maven0.40."}
{"_id":"doc-en-vscode-e0428face50cd968efe97d6fe4eabb851b59a76307d50957a77901acd5f813f8","title":"","text":"vscode-spring-boot-dashboard0.11.1 vscode-spring-initializr0.11.2 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nYou can use this command for now, but I can repro the issue\nThe other change that has been made here is tab moves focus mode has to be on for that keybinding to work. This prevents issues where the terminal should be handling shift + tab such as for or autocomplete. The clause for this command can be configured in the keybindings editor though if you do not like this behavior.\nAfter using the command Terminal: Focus Accessible Buffer, the behavior was a little strange. focus is on the accessible buffer, the tab key does not move focus to the terminal, but to the status bar. When I'm in the accessible buffer I need to press tab and then shift+tab to access the terminal. seems that the accessible buffer is not always updated when I execute a command in the terminal.\nYes thanks, covered in these issues:"}
{"_id":"doc-en-vscode-aba6f42ae293d72e66d36343f7c261fc459f4d4546c9f03f44892d59df65efe9","title":"","text":"there's an issue now because tabbing goes to the status bar instead of the terminal. I see that isn't set on the element. even when I set that explicitly, it seems like it's removed Originally posted by in"}
{"_id":"doc-en-vscode-de4e256946ffe28d90afb092a1fc5f53e0c26010c99a092338ca25a24f85a886","title":"","text":"Testing Works on macOS but not on Windows 11 !\nWorks for me on Windows 11. at the lack of command start decoration on the following line in the screenshot where this doesn't work. !\nLogs from\nis happening after the next in the above, which is pretty weird. We try to detect quick fixes , so it's not surprising this is failing. any thoughts?\nI likely caused this when making command markers more reliable on Windows\nSeems this is broken for the non-polling case, which is why I am not seeing it (with starship)."}
{"_id":"doc-en-vscode-239a4e59d54e56c6314fb6c91078e15edb1740000a1994cec9897d35653cddc3","title":"","text":"From Language specific settings are behind proposed API flag\nEnglish\n— when a fixed stable build can be expected?\nPlanning to release today."}
{"_id":"doc-en-vscode-a38b19deda3e45bdc3e93aaacbe001c14ba1a32ef610ea266223f0f4ef1db43e","title":"","text":"Testing ! !\nThis is because of the same problem that caused\nappears to be closed now, does that mean this has been fixed?\nNo, this issue is about fish acting atypical in that it applies the environment before is applied. This is because of how the automatic injection works in fish via an environment variable. Still not sure how we can handle this.\nDiscussed offline, maybe we could use the first pre exec hook in fish to run shell integration, instead of .\nNice !"}
{"_id":"doc-en-vscode-0892d6eb13977a1c1622582734ec159dab5ff6ad90aa775a100cc48c10db47c0","title":"","text":"<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --For Anonymous functions code lens is displayed although it has only one reference. This is a lot of noise for nothing. In my opinion these lenses can be removed completely.\nThis issue lacks name of the language/extensions that you are using/showing\nYou are right. My bad. I fixed it. Sorry.\nRequires: -\nI in those required settings and am seeing the screenshot below. Seems to now only say 0 references instead of one but the code lens still exists !\nI think the screenshot shows the expected (fixed) behavior. Previously the references codelens was on the line with . There are zero references because there are no uses of that class or method\nyep - this is exactly what I wanted."}
{"_id":"doc-en-vscode-e5c32eb39e963dce4305661efaef6a48cc0a973268036e3ce45aa8690a8aa738","title":"","text":"<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --Hello! Could you please allow for the output.ReverseAttributes to be defined as a user preference setting? This was implemented to and was implemented in the current emmet repo Why is this important? With Bootstrap, all of the generated code samples implement class attributes at the beginning of a tag. For example, a generated (As a note, this is how I've generally seen and used bootstrap classes implemented inside a tag), might have a section that looks like this: to add a new anchor with the same syntax, I would want to use the follow emmet syntax: However, the preview generated, and the implementation do not give me the style that I prefer: ! Now, I could implement a snippet for this specific anchor override, but now if I want to use this style across the codebase with all of my tags that utilize bootstrap, I now have to create a file that grows exponentially to cover every use-case. Since solves this behavior, I figured I could do add this override in my code workspace settings, such as But this did not work. also does not have a supported object for preferences based on . I think this might also open a bigger question of \"How can VSCode support any arbitrary snippet preference? (There are many from where this specific attribute was implemented) There doesn't seem to be a method to implement this behavior via the regular so if I want this behavior today, it seems I would need to fork emmet and vscode, and implement my own custom implementation to enable this feature toggle.\nthanks for the write-up. I wasn't aware of when output.reverseAttributes would come in handy. What I do know though, is that VS Code is currently using an older version of Emmet. Once it moves on to the newer version (the one you see at emmetio/emmet), it should be much simpler to get that preference implemented. I'll keep this issue open in the meantime.\nSounds great! Thanks for the quick response, looking forward to the newer version of Emmet being implemented!\nCreated a PR fixing this"}
{"_id":"doc-en-vscode-5178f86a50d44c0fe06c96dfc7fdb6fff09b7e669574034917ae83fd87fcf213","title":"","text":"Today which have which triggers quick pick to select a file. This issue is about also allowing to type a file name and have dynamic suggestions, like inserts"}
{"_id":"doc-en-vscode-3f0a73e32c1f41e2fbfdac9249d0cb652678a16a1eb35160e909baea57c84c45","title":"","text":"<!-- 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.63.2 .Steps to Reproduce: an error while coding, and open the \"View Problem\" box. that the up-arrow has the label \"Goto next problem\". Ideally it should be \"Goto previous problem\". !\nYou accidentally closed this let's reopen and assign to me. fyi"}
{"_id":"doc-en-vscode-9f33b589e9bc81be76309e4bf2feaf135d664136ecaf7878d143fe500dbf9986","title":"","text":"LSP now support pull diagnostics. Adopt for [x] CSS [x] JSON [x] HTML"}
{"_id":"doc-en-vscode-718334424be9cc560d5a170401d8c336755628bf793ae2b1423561fcdee6be9a","title":"","text":"<!-- 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.84.2 OS Version: win10 Steps to Reproduce: Theme: Dark Modern two cpp files in the workspace, move the tabs upwards and downwards respectively. +N, Open a new Tab, and copy some content into it. Move the tabs upwards and downwards respectively. When I move tabs downwards, the edge color disappears. Another sample This issue can be reproduced in vscode-insider\nI'm not able to reproduce this. Can you check if you see an error in the dev console? Run the command and check the console for errors.\nYou can try with a larger cpp file, simply copy code to many lines. Drag the tab down to change the tab's position\nIt seems the tab scrolls down, so the color bar is blocked\nI was able to reproduce it now. The reason I was not seeing it was because it only appears at specific zoom levels. Looking into it...\nThanks for the help we were able to fix it\nThis problem seems to still exist in the latest vscode-insider. (\"window.zoomLevel\" : 0 ) 86.0-insider x64 With untitled tabs, the tab can be scrolled down and up, Besides, It seems that the .json file is an exception"}
{"_id":"doc-en-vscode-f2da0c4672a9d44b21b04c0cea0e8a8316012c6f77d9666ff69e8d01456365ee","title":"","text":"Depending oh how many editors windows are open and the size of them, sometimes the standalone color picker is partially hidden behind other editor panel. vscode version:1.81.0 x64 !"}
{"_id":"doc-en-vscode-55614ab0ca2345d8132378f7260461afac9929dca2746d19d3b8c01e78eb424e","title":"","text":"There is a z-index error: <img width=\"572\" alt=\"Screenshot 2023-07-25 at 13 56 59\" src=\"\""}
{"_id":"doc-en-vscode-da5a5baffc3e505f21a9916c1c48cdcf553ed32eef354f61b5349dfb4d6ab6b9","title":"","text":"<!-- 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: 1.66.0 OS Version: MacOS 11.5.2 Steps to Reproduce: the relevant lines to to enable the prompt it works in regular OS terminal (outside VSCode or inside VSCode without experimental shell integration) <img width=\"302\" alt=\"image\" src=\"https://user-\"the experimental shell integration in VSCode the integrated terminal, visit the same location and see the error <img width=\"298\" alt=\"image\" src=\"https://user-\"\nI wonder if instead of replacing the entire , the VSCode change could update it with concatenation so that existing commands remain as they are?\nthe approach we're taking is to wrap the function, also we need some code before and some code after the original prompt and bash can have it in a bunch of different formats so it's not as easy as it sounds.\n/closedWith"}
{"_id":"doc-en-vscode-ff93aa5cb1407adc612187d3208c61cdfab0963ef46a4f8b3c70575bf53366d2","title":"","text":"Re , I was editing the endgame notebook in VS Code repo but it keeps moving the cursor to the next line, which breaks typing. It's very likely an issue with these two settings combined \"files.autoSave\": \"afterDelay\" We seems to have the same issue for files in text editor but untitled file doesn't suffer from this as it can't be auto saved. I wonder if we should have some special treatment for notebook cells, as it's very usual to create new cells, which are always empty at the beginning, typing in the first line is making it almost impossible. Maybe we could keep the cursor position for this scenario."}
{"_id":"doc-en-vscode-caa9d6072653eeba4ab926e5e689ee3397d21d660261c7f3b455fc82b8cf8777","title":"","text":"Microsoft/vscode Repro: PR ext description page something, shift+tab until you hit the start of the screen There are 4 focusable items, close, next match, previous match and the find input.\nWould you like me to start on this?\nYes please. It is too late to get a fix in for the January VS Code release but you can submit a PR any time and we'll try to get this fixed for February\nLOL ... my Dragon dictation did the equivalent of a butt dial , deleted assignments and pasted an eMoji sorry about that :-P\nFYI: started on this and I can reproduce and see it. simpleFind transitions in and out with animation, hidden only because of z-index and/or overflow. The widget always has display type:flex , therefore the four tabs stops for the buttons and input are always in the tabIndex order fix should be simple, however, there is an interaction between the animation and the display mode such that simultaneously going from display:none =flex messes up the animation. I'm working on separating the display mode from the transition to see if that will work. I have to do more experiments , May have a question or two later...\nSee PR: Verification: Use a screen reader with screen output on so you can see and track each tab stop Open the new pull request extension page Click on the upper pane to begin focus there Tab through the various toolbar buttons , after dependencies the next tab SHOULD land on With the webview not the simpleFind widget. Verify showing and hiding simpleFind has smooth animation as before Note: When focuses on bottom for web view pane , screen readers output a bunch of base64 encoded text (see truncated output lines below). But I think this is an accessibility bug, if you guys agree I'll post an issue. NVDA Output: with visibility fix (correct output, no tab stops within the hidden simpleFind) NVDA Output: original scenario without fix (can see tabs stops in widget)"}
{"_id":"doc-en-vscode-30a18704f6b08fd7fbebe9827529260b66e97fdc2720913da0eb8be38c6614d0","title":"","text":"Issue Type: <bBug</bI have been using for a long time. Currently I end up with a LOT of inadvertant selections when working in two side-by-side editor groups and switching back and forth between them using the mouse. The reason is that the editor scrolls 5 lines every time I click into it. VS Code version: Code - Insiders 1.58.0-insider (, 2021-06-11T05:22:19.992Z) OS version: Darwin arm64 20.5.0 Restricted Mode: No Remote OS version: Linux x64 5.4.0-1046-azure <!-- generated by issue reporter --\nI cannot reproduce. Does this reproduce for you when disabling all extensions? (The editor exposes a API to extensions). I have recently also got which seems incredibly similar, but I am having a hard time reproducing any of the jumping that is described. Here I am trying two side-by-side editor groups: https://user-\nThis reproduces only when the language mode of the files are set to markdown. I think this has to do with how the markdown extension is using the vscode API. But I think it should not use that API at all if no markdown preview is rendered. But it would also be interesting to test what the experience is when the preview is rendered. Given this doesn't reproduce with txt files, I'm optimistically giving this to you. Steps to reproduce: define open two md files side-by-side (preferably without word wrapping to see the top line number change) click on the editor tab of each one on every click, the editor scrolls up by 5 lines https://user-\nCould you please take a look at this since you were looking into markdown syncing last iteration?\nIt seems like it's a bug coming from the scroll syncing between the static and text editor changes that I made a while ago. I'll try to make a PR to fix this soon."}
{"_id":"doc-en-vscode-5141f063e579bf3b2463227831c301f81d11f901541ffbaed7b30c70b4f60042","title":"","text":"<!-- 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: 1.88.1 (Latest) + GitHub Codespaces OS Version: All? (Tested on Linux + MacOS) Steps to Reproduce: a folder or workspace (create if necessary): all the content from the above file and save it the command palette 'Tasks: Run Task' '+ Configure a Task' 'Open file' any provided task template notification error: \"Unable to write to Folder Settings because no resource is provided.\" Expected behaviour: Empty is populated with the contents of the selected task template <img width=\"898\" alt=\"Screenshot 2024-04-18 at 16 50 01\" src=\"\""}
{"_id":"doc-en-vscode-1d5c0dbc5ced7a5ddc2cc4749d834887de5bb61344dbda65553873d337bff419","title":"","text":"! should be highlighted: ! Version: 1.77.0-insider (user setup) Commit: Date: 2023-03-21T05:22:13.879Z Electron: 19.1.11 Chromium: 102.0.5005.196 16.14.2 V8: 10.2.154.26-electron.0 OS: Windows_NT x64 10.0. Sandboxed: Yes\ncc for TS\nI cannot reproduce, semantic occurrences seem to work fine for me. can you reproduce running from source? !\nI can repro out of sources as well\nLooks like a windows specific issue (slash vs backslash): ! ! (in TypeScriptDocumentHighlightProvider.provideDocumentHighlights)\nReverting fixes it.\nHm I don't think this was caused by . Instead I suspect the root cause was"}
{"_id":"doc-en-vscode-996ed47ca21fca605c2eb706d63231c90c36ea8eed0ba2522f15c8ed26641394","title":"","text":"This seems really aggressive and probably not intentional <img width=\"406\" alt=\"image\" src=\"https://user-\"\nI think this rule references a css variable that isn't defined <img width=\"501\" alt=\"image\" src=\"https://user-\" it looks like you were in this area recently, it looks like there is a default that we don't fall back to, do you know what's going on?"}
{"_id":"doc-en-vscode-191edb98879d0f66d9c36fc793a31f4c2bd664637d7d63de2a9b5d9f9b6f4d8a","title":"","text":"<!-- 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: 1.71.0 () OS Version: macOS 12.5.1 (21G83) Steps to Reproduce: any file on . the filename tab on the \"Editor\", hold + Click on it (the same as a right-click or two-finger click on macOS). See the image below ! Expected: it opens the context menu with options about the file. Actual: it blinks the context menu for a fraction of a second. A screencast of the problem: ! The problem doesn't happen on VS Code desktop.\nI can reproduce, and maybe is an issue that would reproduce on desktop too but we use native menus there and not custom menus.\nis this ctrl+click behavior mac specific?\nI am not entirely sure, but so far, we have only seen reports about this issue on macOS.\nYes, Macs by default consider CTRL+Click a right click. This works across the entire OS.\nThis is great, thanks for the fix!"}
{"_id":"doc-en-vscode-4c6b543dd05117870da38d458f14514ff33ac118602283fdb96691dd6d446119","title":"","text":"<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --This proposal affects Settings editor (Settings UI) users and extension authors. The search in the Settings editor currently shows results sorted by the table of contents so that commonly used settings can show up at the top, and so search results can be grouped by the entries in the table of contents. The change to sort the settings by table of contents was made as part of and However, the Settings editor performs two searches per query: the first search finds settings based on keyword matching, and the second search attempts to find relevant settings using similarity search algorithms. As a result, the second search is prone to finding less relevant settings, especially when the user had a specific keyword in mind. Because the Settings editor currently orders settings by the table of contents, the less relevant results from the second search sometimes end up showing above the keyword match results because they appear first in the table of contents. As an example, if I search \"title bar style\" in the Settings editor, actually shows up fifth due to table of contents sorting: ! This issue proposes reverting the settings search so that the keyword matches always appear at the top of the search results again. As part of this proposal, and would regress and become out of scope. In other words, ordering the search results so that keyword matches always appear first would break grouping the search results by the table of contents entries, but would make it so that users hopefully don't have to scroll down as much to find what they were looking for. Implementing this proposal would also break sorting extension search results by the settings order numbers given by the extension author in their extension's file. I noticed that the issue of having to scroll down to find a keyword match is made worse when the Settings editor is \"small\", such as when I restore/shrink the VS Code window. Screenreader users might also have to tab down more search results to get to the one they want. Feel free to upvote the proposal if you'd like to see it implemented, or downvote it if you'd like the settings search results ordering to remain the way it currently is. You're also welcome to comment on this issue with alternative suggestions for how the search results should be shown within the Settings editor."}
{"_id":"doc-en-vscode-843f96cb14c784b3ff7c6bf18a5335ed010bb4fa73d5925454e01908100a9267","title":"","text":"Pinging authors of the issues above along with those who I have seen express interest in reverting the behaviour:\nAnother idea I have rather than doing a full revert is to use table of contents order as a last resort sorting key for the keyword matches. Therefore, keyword matches in the title could come before keyword matches in the description, and the settings that all have a description-only keyword match could be sorted amongst themselves by table of contents order. With this concept, some extension settings could preserve their order, but an extension setting found by keyword matching would still always come before an extension setting found by a similarity algorithm.\nTo revert the search results in the Settings editor to order by keyword matches first in the Visual Studio Code extension, you can follow these steps Open the Settings editor: You can do this by pressing the Ctrl+, (Windows, Linux) or Cmd+, (macOS) keyboard shortcut, or by clicking on the gear icon in the Activity Bar and selecting \"Settings\" from the dropdown menu. Search for the \"workbench.settings.settingsSearchTocBehavior\" setting: In the search bar at the top of the Settings editor, type \"workbench.settings.settingsSearchTocBehavior\". Change the value of the setting to \"hide\": Click on the dropdown menu next to the setting and select \"hide\". This will disable the table of contents ordering and prioritize keyword matches. Restart Visual Studio Code: To apply the changes, you need to restart Visual Studio Code. Once you restart, the search results in the Settings editor will be ordered by keyword matches first.\nthat behaviour was implemented as part of , and yes, it is a workaround in a sense. This proposal is on ordering results by keyword matches first even when the table of contents is shown.\nTry doing this way In the file, add the following property to the contributes section: { \"name\": \"revert-settings-search-to-keyword-matches-first\", \"version\": \"1.0.0\", \"description\": \"Reverts settings search in the Settings editor to order results by keyword matches first."}
{"_id":"doc-en-vscode-7d3e23159a2c71a3c85d9352f1298875728b282253d2f98f1474170bbe53c18e","title":"","text":"\", \"publisher\": \"your-name\", \"categories\": [\"Settings\"], \"activationEvents\": [\"onStartup\"], \"contributes\": { \"configuration\": { \"properties\": { \"search.settings.sortByKeywordMatchesFirst\": { \"type\": \"boolean\", \"default\": true } } } }, \"main\": \"\" } the extension's main script file, add the following code: const vscode = require('vscode'); vscode.extensions.onDidChangeConfiguration(() ={ const sortByKeywordMatchesFirst = vscode.workspace.getConfiguration('search').get('settings.sortByKeywordMatchesFirst'); // Update the Settings editor's search sorting algorithm here. });\nSince I am coming from , it would be important to me that the order determined by the extension is retained when only \" is called (as you also suggested in ). This then serves as a filter for the items in the base order. If you then place a keyword behind it, you can search \"smartly\" again.\nVerification notes: for title bar style should show the setting first no matter what value is set to. for should show the CSS category first, followed by the LESS category, and lastly by the SCSS category."}
{"_id":"doc-en-vscode-606e0d22b1b6caa122a2eea665e001d4e23ab21a5e1a43c6d07ad5b211a21194","title":"","text":"Type: <bBug</bany open windows. to File Open Recent and click Clear Recently Opened. VS Code version: Code 1.83.1 (, 2023-10-10T23:46:55.789Z) OS version: Darwin x64 20.6.0\n<!-- 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!\n/verified"}
{"_id":"doc-en-vscode-f5fa9bf77eaec0421f93c339495a07db110744597eddaf742cdb739f3c513a26","title":"","text":"VSCode Version: 1.36.0 OS Version: Windows 10 Repro steps: Live Share extension 1.0.488, start a collaboration session two comment threads on a single line. Comment on a line, 3 for example Comment on a second line, 4 for example Delete line 3 Now there are two comment threads on line 3 (the line that moved up from 4) /Collapse the comments with the marker Collapsing/opening such comments might need a rework. Currently I can collapse each individually, and if all are collapsed (or all open), the box on the gray line opens (or closes) all threads. However, if only some of the threads are collapsed, the gray box toggles between the set of open threads and the threads which were collapsed. It never collapses all threads to return to code, and requires each remaining thread to be collapsed individually. Originally reported in Live Share issue\nAs I was just about to file the same thing, here is the screencast I created for illustration: !\nI agree the current behavior is a bit confusing. Clicking in the gutter is a common way to collapse open comments. However, the workflow fails when multiple comments are on the same line. This forces the user to think and use the alternative workflow (top-right icon). Suggested behavior: if at least one comment is expanded, collapse all comments on the line otherwise, expand all the comments The condition could also be reversed (expand if the line has both expanded and collapsed comments).\nSince we just came across the relevant code again in another context: clicks on the gutter icon currently toggle the collapsible states for all threads on that line independently here: already exists as a private property, if there was a public getter for it, behavior like the one suggested by above could probably be implemented very locally in the location I linked to above. let us know if that sounds reasonable and we can make a PR.\nyes, this sounds reasonable to me. l would accept a PR!\nI opened ."}
{"_id":"doc-en-vscode-a3db2d42043e573c3e55929c2e0f62f1d1f07fac193a4223cb712e52569372e3","title":"","text":"Does this issue occur when all extensions are disabled?: Yes VS Code Version: 1.77.2 OS Version: Windows 10 It seems that when refreshing () the in a short period, the second refresh is not actually performed. I have provided an example repo and a video demonstrating the issue. Basically we have a that shadows the active editor so whenever a user changes the active editor we update the read only document. However, if the user changes the editors quickly enough then the second change is dropped... Steps to Reproduce: the extension the command \"Open Read Only Document\" tabs quickly and see how it falls behind even though the content is up to date https://user- The content is actually set but it seems the second is dropped. Because if you refresh the document manually it shows the correct content (see the video above). The issue seems to happen more frequently if the content of the file(s) is large.\nI found out why it happens and attempted a fix (with explanation) in\nPinging so it does not get lost"}
{"_id":"doc-en-vscode-f4584483eeacc9b6b578d477980cde5539e707f5312e45cfc98ca6e4f06a758f","title":"","text":"Running out of sources I see this:\nThis means that the contribution isn't getting evaluated before is called. Not too familiar with how / when is handled, but we call when the is created\nI think perhaps moving that to the top of the constructor (before registering the command handlers) will fix this\nThis happens on window open\nand the quick fix does work for that extension !\nSeeing this in error telemetry for Insiders from 12/23:\nThis is the 6th error by machines in telemetry https://vscode-\nI cannot reproduce this in Insider's. did you notice this after doing anything in particular?\nI got this error when using remote dev container <details<summaryWindow</summary</details\nFixed in\nActually still found it in my devtools today:\nI can't reproduce, but I can simulate the race by adding to 's promise in\nHI, im having the same problem here 2023-02-16 17:10:14.453 [error] Error: No registered selector for ID: ms- at R.registerQuickFixProvider (vscode-file://vscode-) at r.$registerQuickFixProvider (vscode-file://vscode-) at m.N (vscode-file://vscode-) at m.M (vscode-file://vscode-) at m.H (vscode-file://vscode-) at m.G (vscode-file://vscode-) at vscode-file://vscode- at g.invoke (vscode-file://vscode-) at n.deliver (vscode-file://vscode-) at a.fire (vscode-file://vscode-) at r.fire (vscode-file://vscode-) at Z.onmessage (vscode-file://vscode-) I got vs code 1.71.1 running on W11 21H2 How i am supposed to fix this, or it's not a problem and vs code is working normally? Thank you!\nUpdate your VS code version, where this is fixed\nSorry, i typed incorrectly mi vs code version. It is the latest one 1.75.1, i reinstalled it today.\nI can still reproduce in latest stabel 1.75.1 https://user-"}
{"_id":"doc-en-vscode-fcf17903f09a86c2c65824ec53ba3acc77bd7c9fc72ec0faef8cdbbe40b794d1","title":"","text":"Issue Type: <bBug</bclick folder some chars and drag to the left to release GIF ! VS Code version: Code 1.41.1 (, 2019-12-18T14:58:56.166Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (29)</summaryExtensionVersion ------ vscode-css-formatter1.0.1 markdown-preview-github-styles0.1.6 vscode-intelephense-client1.3.9 vscode-markdownlint0.34.0 vscode-html-css0.2.3 php-debug1.13.0 auto-js-vscodeext0.2.3 composer0.7.1 markdown-shortcuts0.12.0 hex-rgba-converter1.0.4 php-namespace-resolver1.1.8 code-beautifier2.3.3 vscode-language-pack-zh-hans1.41.2 remote-ssh0.48.0 remote-ssh-edit0.49.0 remote-ssh-explorer0.49.0 cpptools0.26.3 Go0.13.0 php-docblocker2.1.0 vetur0.23.0 vscode-php-getters-setters1.2.3 minapp-vscode2.2.2 java0.55.1 vscode-xml0.10.1 datetime1.0.5 code-settings-sync3.4.3 vscode-java-pack0.8.1 vscode-preview-server1.3.0 html-css-class-completion1.19.0 </details<!-- generated by issue reporter --\nI can not reproduce this. Thanks for filling this issue. Can you reproduce using Visual Studio Code Insiders\nreproduce too !\nI can not reproduce this both on macOS and Windows and I am doing the same thing as you. Let's leave this open as see if more users hit this. If you are interested in providing a PR which fixes this, here's a code poitner\nreproduced as well, make sure you release the drag on the arrow icon.\npushed a fix for this. Please try it out in VS Code insiders from Wednesday and let us know if you still see the issue. Thanks\nThanks, but have a new problem: Input is cleared !"}
{"_id":"doc-en-vscode-7f0e481058f4197800976fa98d1dff1f3d4091c10e0fca3cf156ff72466e4aba","title":"","text":"Yeah I also saw that, it's caused because when \"expanding\" the row element the tree refreshes and the previous value in the input is lost. But I think that doesn't look as bad as the previous behavior where the children got duplicated"}
{"_id":"doc-en-vscode-d077a254cab99726ab8cca382ab96374f32472db8a8257f6303c5004e32046cc","title":"","text":"Build: Changes:\ndoes the error ring a bell? Should we be running with ? Besides, many crash dumps again, such as:\nCrashes are tracked in As for GPU initialization failure, it could be due to various reasons depending on the hardware. Need additional logging to identify the cause . I would suggest to disable gpu, since it is not worth addressing them for CI."}
{"_id":"doc-en-vscode-351dc39cd7f62534845a3c5a7cabcda8185493cc2f134a2ae5ad9d00c64569c1","title":"","text":"VSCode Version: code-insiders-1.8.0-.el7.x86_64 OS Version: CentOS Linux release 7.2.1511 (Core) Steps to Reproduce: code rpm from insiders build on CentOS minimal to launch it from cli Installing GConf2 fixes it ( yum install GConf2 ). maybe should be a dep in the rpm spec file.\nhello would love more information on the minimal install aspect for your use case. To clarify, are you starting with a \"minimal installation\" and then installing x11 after the fact ? !\nYes, and after that I just install the basic fonts and xorg xauth because I ssh into the devel box and use the editor via X11 forwarding. I've done this with other editors and is pretty handy, so I can avoid copying/checking out code from the workstation to the devel box (I write stuff meant to run over CentOS 7)\nThe exact same problem occurs on Elementary OS (based on Ubuntu). Running fixes the issue. It's most likely the same missing dependency problem in the .Deb file.\nthis should be fixed in 1.9\nHello, I had the same problem on openSUSE 42.1, when I ran the problem was solved. Btw I downloaded the .rpm file.\nOn ArchLinux pacman -S gconf"}
{"_id":"doc-en-vscode-d3846aea8f5357b3e52e804106d5d625082f36087264e01f64088e8eea34fd68","title":"","text":"Issue Type: <bBug</bOpen a Webview (for example: Help -Release Note) and start the search (Ctrl+F) and write the search term (for example: \"Update\") Only \"u\" (first letter) is selected on the view and not the current tipped search term. ! Notice: If i pressed \"enter\" then the full term is selected on the view. This behavier was other in the previous version (1.52.1) VS Code version: Code 1.54.3 (, 2021-03-15T10:55:45.459Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (31)</summaryExtensionVersion ------ mock-debug0.45.4 cortex-vsc2.1.0 npm-intellisense1.3.1 vscode-markdownlint0.40.1 jshint0.11.0 vscode-eslint2.1.19 vscode-npm-script0.3.18 vscode-firefox-debug2.9.2 auto-close-tag0.5.10 code-runner0.11.3 vscode-test-explorer2.19.6 code-coverage1.2.3 vscode-docker1.11.0 csharp1.23.9 python2021.3. vscode-pylance2021.3.3 jupyter2021.3. cpptools1.2.2 powershell2021.2.2 debugger-for-chrome4.12.12 vetur0.33.1 java0.76.0 vscode-xml0.15.0 vscode-yaml0.17.0 markdown-preview-enhanced0.5.17 vscodeintellicode1.2.12 vscode-java-debug0.32.1 vscode-java-dependency0.18.2 vscode-java-pack0.13.0 vscode-java-test0.28.1 vscode-maven0.28.0 </details<!-- generated by issue reporter --\n(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.526 --<!-- potentialduplicatescomment --\nThe search behaviour changed between Electron 9.3.5 and Electron 11.4.1. The parameter should now be whenever we're doing a search for the first time."}
{"_id":"doc-en-vscode-2afcbdfc93c910f052e49ac88eaae4d6feb57105aec9d1e5d28b6f87b35607fc","title":"","text":"[X] Notebooks (.ipynb files) [ ] Interactive Window and/or Cell Scripts (.py files with #%% markers) Hello. As the title says, I can't make a internal link in a jupyter notebook in vscode if the cell's title starts with a capital letter, contains an underscore or contains a space, as you can see on the images. Also, on the sole option that it works, non-capital letter header, when clicked it brings me to the bottom of the notebook, and the focus is not brought on the right header itself. Initial tests: ! The test headers: ! 64.5 v2022.2. Python v3.8.5 Python Extension: v2022.2. No response Local\nThis is actually handled by VS code core (and not the extension). I've included a demo notebook that repros the problem .\nIn the demo notebook, the href jumps all work ! But none of the header jumps do unless you rewrite them to be only lowercase. All of the links work fine when running in 'jupyter'.\nVscode this notebook is still with all the bugs. Even on the links that work, they jump me to the very bottom of the notebook, not to cell 2, cell 3 or cell 4. Also Section jump and Section with space jump still doesn't work at all. I'm using portable Vscode btw, but I think this doesn't make any difference since when I was using the regular one this bug still existed. Even now, about 2 years later (that I recall) it still goes on on notebooks in Vscode. I can record a GIF if you need. I assure no weird magic was done on my vscode, just regular installation and all... and I can confirm that this issue still occurred years ago on my other PC too.\nDoes this reproduce in the ?\nIt did for me.\nWill this issue be addressed on any new version of Vscode? I've headed to version 1.67 and to \"April+2022+Recovery+2\"+is%3Aclosed and found no mentions of this issue. Perhaps on the next, if it would be implemented/fixed at all? Thanks anyway! :)\nThis issue was fixed in 1.68 (the May 2022 milestone)\ngot a look at and pull request ( ) doesn't appear there."}
{"_id":"doc-en-vscode-79e0521818fff115c1ee1334717ee202249eb88a1c0cb5d76cb14fda8c7b393b","title":"","text":"Will it be ? Thanks :)\nDid you test it?\nYes! everything was fixed. Capital letters, underscore and space headers now work like a charm. I was just asking if this specific commit ( ) will be listed on the update website. I don't know how it works, if minor fixes won't get listed or something like that. I just wanted to show to some friends that somehow I've contributed to Vscode with my bug report Anyway, everything buggy was fixed. This issue may be closed anytime."}
{"_id":"doc-en-vscode-898cf41e17b3e7b46ccfa7dc59da05c314d83596164d7b4192df698ffc07aa05","title":"","text":"Testing So I was testing the terminal sticky scroll and I noticed that the sticky code block disappears in an abrupt manner when the beginning (not the end) of the multiline terminal command, reaches the end of the scope. To give more context about what I mean, I the GIF below. I was sort of expecting the code block to start disappearing when the line reached the end of the output for that command. I noticed that the code block disappeared however when the line reached the end of the output for that run. I don't think this is a problem per say, it's a different manner of animating sticky scroll. I was just wondering if this is intended? I think the potential issue with this approach is that the sticky scroll block is hiding the next terminal command and its output while you are scrolling until it disappears. In the editor, sticky scroll starts disappearing progressively when the bottom of the last block/line touches the end of the scope. Perhaps we could explore something similar?\nThis is actually a bug, it's meant to scroll up as in the editor and was doing that at some point. Note that it's not as smooth as the editor since there's no \"partial line scrolling\" in the terminal\nRepro that demonstrates more clearly what's happening: Run: Run: Run: when scrolling, sticky scroll from a command should never obscure the command below it like this: !\nI see the prompt line sort of being obscured here"}
{"_id":"doc-en-vscode-5ce533ff9752f9a00550f5f3d04c1013c97187cb585a751ee3bb3d806bd6a9ee","title":"","text":"I try to add a keybinding with ${selectedText}. but it will resloved as a normal string. Steps to Reproduce: ! Version: 1.75.0 (user setup) Commit: OS: Windows_NT x64 10.0. Sandboxed: No\nwould you happen to know why the variable isn't resolving to a value here? Is there something that the command must contain to resolve variables?\nThe decision for whether variables should be resolved in a command needs to be made on a per command bases. If you want, you can run your commands arguments through the variable resolve when your command is called. For example, the terminal uses the variable resolver here:\nFrom It would be great if more variable resolution was achieved in keybindings - I think it has been requested many times.\nverif steps: a keybinding for : that the keybinding correctly sets to the current path."}
{"_id":"doc-en-vscode-446f87812b5e4ae507073a0f2479fd81c8eefa281fc9ccb0c30e88288ce3f0fd","title":"","text":"When creating a breakpoint in an active debug session and this breakpoint cannot be verified, the resulting icon is almost invisible: ! The problem is that the icon's stroke is too thin. In previous versions the icon had a thicker stroke: ! I suggest that we restore the previous icon.\nAgree that it is a bit too light. I do not just want to take the previous icon since the color and style are different. Thus it would be great if could tackle this Also fyi\nNot quite as strong as in the 'before' above, but stronger. Marking verified. !"}
{"_id":"doc-en-vscode-902303e05784e838dc9d6fe0de67b378c4daf211ab05c5e10c7db4115fd2c604","title":"","text":"Type: <bFeature Request</bCC Just like other audio cues, please reduce aria alert when \"\" is used. VS Code version: Code - Insiders 1.84.0-insider (, 2023-10-17T05:34:42.128Z) OS version: Windows_NT x64 10.0. Modes: <!-- generated by issue reporter --\nalso when is used\nTo verify, Enable Enable a screen reader Format a document Verify that the screen reader doesn't alert and you just hear the audio cue\nVerified, but found this:"}
{"_id":"doc-en-vscode-e24ca3411e9c3d8a6d75334599e3b0c8e97b5caa80cdd5188303293343410bb9","title":"","text":"Originally reported by\nFriendly ping! Looks like this issue requires some further steps to be verified. Please provide us with the steps necessary to verify this issue.\nwould you mind verifying this one please?"}
{"_id":"doc-en-vscode-0db54f2d7e77a1c5b6156aed543795045aa85f6391a208f5e37d900a54887111","title":"","text":"Open Set some breakpoints They show in the wrong place and cover a character, but seemingly get fixed when setting a breakpoint on the next line !\nIt is non-deterministic: ! Maybe that depends on the timing of the debugger. If I add to this statement (effectively removing the condition), I cannot reproduce anymore: Unfortunately that might cause performance problems. I think this is because needs to be called when injected text is inserted before it.\nI am currently still reproing it here: <img width=\"445\" alt=\"image\" src=\"https://user-\" btw make sure you add labels and a milestone to issues for verification and tracking\nAny chance this could be looked at soon? It comes up pretty often <img width=\"1018\" alt=\"image\" src=\"https://user-\"\nThanks"}
{"_id":"doc-en-vscode-5c48d291187b6396fe85150541d46397f4a5c684da7ff9fb4084eb819b4ca014","title":"","text":"Testing There are \"\" \"notebook.outputLineHeight\" \"\" \"notebook.outputFontFamily\" \"notebook.outputFontSize\" Ideally these would be all namespaced or prefixed .\nThis affects how they show up in the settings editor UI, btw: <img width=\"919\" alt=\"image\" src=\"https://user-\""}
{"_id":"doc-en-vscode-e15e2f345d2055721ebeffdb4e8644b57bd8f7e99bd00ea0b1c311423b1a6e5e","title":"","text":"Following on from comments at , it would be good to have basic Dart language configuration as a built-in extension in VS Code, allowing things like syntax highlighting to in the case where the Dart extension is not installed (for example a Live Share client that hasn't installed it) or is disabled (for example in an Untrusted workspace). From : There is a Dart Team-owned grammar here that can be used - it's the (except for a small bug fix that I'll file an upstream PR for shortly): Great! Though what's the advantage of depending on the built-in extension? I try to support a few-versions-old VS Code where possible (so wouldn't do that for a few versions) but also the extension is published to open- for use by other clients so the dependency may complicate things (if they don't have the same built-in). I'd probably do some investigation into this before removing anything from Dart-Code then (it sounds like there's no downside to having the grammar/config provided by both for a period anyway). (fyi\nIt also works without a dependency, but only because the extension is built-in. No problem if the Dart extension keeps the grammar and language configurations for a while until it is all settled. Do you want to look into a PR or should I?\nIf it's easier/quicker for you to do, feel free. Otherwise I'm happy to do it but may need some pointers for how built-in extensions are set up.\nI pushed the PR We have a new built-in language :-)\nSuper, thanks! For future reference - for changes to the language config I can send a PR to , and for grammar changes I can run (after the changes are landed in the upstream dart-lang repo)?\nI just noticed in the it has the path but this doesn't seem to match the location of the file ?\nGood catch, thanks. Pushed the fix:\nFor grammar changes, I'll pull them in about once per month so you can just rely on that if you want. If there's a change that needs to be picked up sooner than that, then feel free to make an issue an @ mention me and I'll pull in the change earlier.\nPerfect, thanks!\nis this support in the Code May Update (1.57) that just went out?\nYes, in microsoft/vscode you can tell what release an issue is in by looking at the Milestone. !\nYep!"}
{"_id":"doc-en-vscode-4ee66b3ef55cec6a2ea5c0894af826b99a76db040ba587ed909df24d8dd969c5","title":"","text":"An easy way to test it's working is to disable the Dart/Flutter extensions (accept the prompt to reload), then open a Dart file. You'll now still get syntax highlighting (note: you won't get analysis or much other editor functionality, that requires the Dart extension). <img width=\"650\" alt=\"Screenshot 2021-06-14 at 15 52 25\" src=\"https://user-\"\nYeah I just did, and it works great :-)"}
{"_id":"doc-en-vscode-69696b2a90d96f6377a218dabe20153aab053c9d8ef938235125c5d9fe59b38c","title":"","text":"! Notice the red icon, I find that somewhat unexpected. //cc\nI bisected this to gonna add you to assignees.\nThanks for tracking this down."}
{"_id":"doc-en-vscode-3de137b0eb820a467a2996d7de9fe483bc9b8fb446b221a9cba51d6b6867e0d8","title":"","text":"The change for went in without a UX discussion. IMHO we should reconsider adding these two actions to all editor context menus. IMHO we need to be more critical with adding things there and have good reasons to do so. <img width=\"284\" alt=\"image\" src=\"https://user-\"\nI figured it wasn't a major change since they are already in the context menu during a debug session. Would a Debug submenu help? Or how about only showing them if the user has previously debugged in this workspace?\nI see how it might not feel like a major change, but IMHO we should approach this with a different mindset. We have many useful commands, and we can add many of them to the context menu, but just because we have the ability to add them is not IMHO a good enough reason. Adding something to the context menu has two disadvantages: it makes our editor feel bloated (think typical IDE of the early 00s) it detracts from the value of the existing items, since there are so many of them. I think we need to have a good reason to decide to always show something in the context menu, like a very important feature that we feel will differentiate VS Code from other editors, a reaction to a lot of user feedback, an action which would make the product incomplete if it would be missing, etc.\nWe discussed this in standup and I will likely just remove them when not in a debug session.\nFrom and Keeping the changes so that they will work and appear in the command palette when not in a debug session, but only appear in the editor context menu while debugging"}
{"_id":"doc-en-vscode-8e54a43b75e4591590c8fb5b474cf421e093f9b40ea45d0351cff944de635aad","title":"","text":"When the content hover contains a color picker and it is resized too small, the text and the color picker box overflow. Perhaps the text should disappear when there is not enough space for the text.\nAt least the text does not wrap to the next line anymore, but imho the text should remain visible for as long as possible and could possibly also have text-overflow: ellipses? <img width=\"153\" alt=\"image\" src=\"\"\nHi thanks for your comment. The following PR which was merged yesterday should set a minimum width on the content hover when a color picker is embedded and resolve the issue. The fix should appear in today's insiders with commit number\nIndeed, thanks!"}
{"_id":"doc-en-vscode-ae498c52c27aa3859bd7cac16cdf708d468984bc25cb42006133864e677ea336","title":"","text":"Hovering inlay hints should show problems \"underneath\": !\nCame here to report the same thing https://user-\nThis happens because inlay hint have their own hover which are anchored on a . The diagnostics hover explicitly checks for that and . Would be OK to pretend to be a \"normal\" range hover anchor so that I can get all the hovers together? Or should the diagnostics hover not check for the hover type?\nThe is used both by inlay hints (via ) and ghost text (directly instantiates it). I think in the case of inlay hints you would want that markers are rendered in the hover, but perhaps ghost text wouldn't want that they appear in the hover, it might want to show only these actions: <img width=\"598\" alt=\"image\" src=\"https://user-\"My suggestion would be to add something to to be able to distinguish the two cases.\nCan still repro this\nPlease update this issue with a real code snippet that allows to reproduce this, please update this issue with what you have tried. Thanks\nI just found a reduce function in VS Code sources such as and replace the returned value with the void keyword such as\nSomething like this only gives a squiggle for the return value, not the arguments or anything with inline hints. To clarify, this will only work for squiggles that spawn across inline hints <img width=\"699\" alt=\"Screenshot 2023-01-26 at 14 49 07\" src=\"https://user-\"\nHmm, maybe it's because it's in a function so the return value becomes incorrect? This in <img width=\"917\" alt=\"image\" src=\"https://user-\"\nThanks for updating\nLooks good to me. Version: 1.75.0-insider Commit: !"}
{"_id":"doc-en-vscode-f87b764e56af7fda90e2f1ab491c9cb168af223c177a4684c98ce8fb4b68f10b","title":"","text":"<!-- 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. --- Version: 1.75.0-insider (Universal) Commit: Date: 2023-01-10T05:21:34.436Z Electron: 19.1.9 Chromium: 102.0.5005.194 16.14.2 V8: 10.2.154.23-electron.0 OS: Darwin arm64 22.2.0 Sandboxed: Yes Steps to Reproduce: an existing workspace folder with git a few branches with commits to switch branches list of branches does not display the recent branches on top the same workspace folder in vscode stable and the order is as expected"}
{"_id":"doc-en-vscode-90307ece4431c197d80d4216378d974f7b430c17094c9429cc11b4b2942c2729","title":"","text":"I started seeing this error since yesterday, then remembered that I this setting trying to commit from scm view: ! saving the file which triggers : !"}
{"_id":"doc-en-vscode-b77a021ae49f1fac78b20dc244815a2ebe54b9ca3083254e3fda0303f2a203c2","title":"","text":"Issue Type: <bBug</bI remapped command to [Alt + V]. And such keybinding doesn't work. KeybindingService log is as follows. Keybinding seems to pass through vscode to terminal since when I run in terminal it registers keypresses. VS Code version: Code 1.67.2 (, 2022-05-17T18:23:40.286Z) OS version: Linux x64 5.15.41-1-MANJARO Restricted Mode: No Remote OS version: Linux x64 4.19.119-30.2 <details<summarySystem Info</summary </detailsExtensions: none<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nThis is working fine for me, I do see the warning that I don't understand though. any insights into what could be happening here? Could the soft dispatch teh terminal does be causing problems with this ignore single modifier thing?\nYes, I think is not dispatched through the keybinding service in this case. Looking again at the OP log: And comparing it with the output I see when binding to : Notice how the OP's log does not contain the keydown event for (i.e. this line ), but there are logs about being dispatched. I think the logs about being dispatched relate to the call the terminal does, but it looks to me that the keybinding service doesn't really get to dispatch the keyboard event, so it doesn't execute the command. I see how is making the log confusing so I will push a change to improve logging to better distinguish between and the real dispatch.\ndo you have or set in your\nYes I have enabled, but I didn't override . As far as I understand is included in by default.\nIt is but when is set to true it overrides as a convenience setting for users who use a lot of shell-based keybindings. If you're getting into needing to customize , I'd recommend setting back to false and tweaking instead. I checked the docs and it looks like this is already explained so I don't think there's anything we need to do on our end: !\nok, thanks a lot for your help"}
{"_id":"doc-en-vscode-b9e12a8a196f8c5932b9de606e20965bbf4c70bf5c88b7cf74dfd71fbfb21b37","title":"","text":"<!-- 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. --<!-- 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. --Something has changed in the latest Insiders so our CI started to fail with errors (any branch but here is an ): Do you have any idea what might cause it so we can make changes on our side? Might it be something with your dependencies?\nRuntime has no changes with insiders, this seems like a regression from the recent http proxy changes based on in upstream. Passing onto From a quick look the extension relies on package which makes network connection. it would be great if you can reduce the test case to a minimal extension sample for us to debug this issue further. Thanks!\nUnfortunately, we haven't been able to isolate the issue for a minimal extension sample so far. To reproduce the problem, you can follow these steps: the and install the extension. the following commands in the terminal: When running all tests, you may observe multiple failures with the . However, when running the failed tests separately, they randomly may or may not fail again, which makes it hard to identify the cause of the issue. It is possible that your proxy patches might be the right place to look for further investigation.\nMaybe a related discussion:\nFound it. The place in our code that fails with the latest Insiders is . I created a so you can try it, but here is the code snippet for a quick look:\nThanks for putting together this test! My investigation so far: is called with resulting in the reported error when it calls here: The check at would prevent from being called when , but that is only with in 19.0.0."}
{"_id":"doc-en-vscode-d8f7740b419ca5e92e159de0fc3307bac93637cf56206d7cd841cb791ff56265","title":"","text":"Still need to check older versions to see if that check was backported and see if there is a way to test this assessment.\nis available in 18.8.0 and 16.18.0, our exploration builds based on Node v18 has this change, you can use the builds from to verify the assessment.\nThe test does not reproduce the issue in the exploration build. Still trying to understand what is happening (please ignore the above code pointers) by looking at the code at the tag. I see the failing call to being triggered in : What I don't quite understand is that the callstack to with comes from : But at that line is supposed to call not as it appear in the callstack: Could you point me at the source that went into Electron? I believe that is not the exact same as that at\nElectron pulls source from when building, what you are looking at is the correct one. I think the async stack is missing a trampoline calll, but you are seeing a write after shutdown stack same as\nThanks This looks like an upstream issue to me, should not be called when is already . I don't see the change in 18.15.0 (the version the exploration build is using) yet that might have fixed it.\nWe have reverted to the previous way of loading certificates as we are getting close to a release ().\nWe're seeing this again in our macos and Windows CI jobs for VSCode \"Insiders\" (not current VSCode stable version 1.82.2). Was node or electron updated in the last 2 days on VSCode Insiders?\nThere is fix in upstream for the above scenario, I will backport it to relevant release lines.\nCould you confirm that todays Insiders build fixes the problem? Thanks!\nConfirmed, thanks!"}
{"_id":"doc-en-vscode-e129e2faf4c785694b8203639583595ef3bb9e95b4b48241554cd7634d24cb36","title":"","text":"Testing Open keybindings editor and interactive window in two editor groups Check that input editor has shift + enter as keybinding to execute Change the keybinding to some other key Placeholder is not updated\nThis doesn't seem to work for me on Windows:\nsorry that's the wrong command, the Jupyter extension contributes multiple Shift+Enter keybindings. Could you please try changing the extension's keybinding for ? E.g. !\nThanks!"}
{"_id":"doc-en-vscode-12bfae9c4d4eec713a1af163345aa0db82529ad30805cc072ec8862832ed9906","title":"","text":"I just now noticed how the progress bar was a the very end of the quick pick but not below input box, I think it should be below input box because the progress is for what I typed. Steps: have some history entries in Cmd+P picker be on a slow OS (Windows) start to type and notice progress bar is below the history entries //cc\nSeems like this might have been a regression at some point. for relocating it back near the input.\nI like where it is now. To me it says \"the results are still populating\".\nThe reason I do not like it: the progress bar is at a non-deterministic location depending on the number of items the progress bar indicator is away from the location that triggers it (the input box)"}
{"_id":"doc-en-vscode-d96d1bee3930ed98cfe5c3721616ff23a4db7056a16a94bda30bc412ed7a4633","title":"","text":"For\nVerify: write an extension that exercises the following APIs by passing in a selection as option and verify the selection is revealed and showing up in the opened editor: command API Provide a property of type to get it. !"}
{"_id":"doc-en-vscode-ac995d2e1d20af33eee5652c3d99c5b864c547f061f0a25ee0005d5aa4c526e1","title":"","text":"<!-- 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 VS Code Version: 1.61.0 (I've seen this before and see it on too) OS Version: MacOS 11.6 Steps to Reproduce: Have 2 editor groups in workspace. Open a search editor (Cmd+Shift+F [can't remember if that's a default or my custom keybinding]) it to the other editor group. something to search for. At this point, you have to scroll up to see the results.\nI've been looking into this. Any ideas where to start? I see that the following code does get called, but doesn't seem to position it correctly. If I wrap in a for 500ms, it works, but that's not a good long term solution."}
{"_id":"doc-en-vscode-378099c03434bc24c0d8b49628bd698b26eabc3c1d312e136026f3386e4f3b3c","title":"","text":"VSCode Version: Code - Insiders 1.5.0-insider (, 2016-08-09T16:02:06.523Z) OS Version: Darwin x64 14.5.0"}
{"_id":"doc-en-vscode-22b1fe8b6fa694f0ef8b6c24f7aadc32d5dde64811c0198968f905753a6954e6","title":"","text":"Testing Unfiltered notebook noob feedback: ! I was expecting a tooltip to tell me what it meant.\nAgreed that we should add tooltip for it.\nhow would you interpret it if there was a tooltip that said \"Execution Order\"?\nwhen you run all cells it goes in that order? I was expecting that to be sequential from the top?\nIt's the order that it was executed it, not the order it will execute in. Hopefully a user would figure that out if they run the cell and see it change.\noh, more explicit would be better then imo I also question why this is useful but I'm guessing this is a common notebooks feature elsewhere?\nYeah it's what people expect from Jupyter and can help you understand the state of the kernel\nThanks that needs to be localized though. btw if you are going to merge your change in, you can just commit directly, no PR needed"}
{"_id":"doc-en-vscode-810682e1a52a57677b408f69b939fa0d34f67fda30834833302f788b208a7d62","title":"","text":"Ref: To align with regular menus and command palette entries, this menu should use capital casing e.g. or\nI proposed a fix in with just CSS but feel free to propose a cleaner way if you'd like. Unfortunately it ends up as and not . Not sure how that logic works for menus/commands."}
{"_id":"doc-en-vscode-7043bfe30eb961dd32acdb1b8268f3b10ca3a5fe5d66b28f66dca3146c12a93c","title":"","text":"Bug ! vscode-inno- VS Code version: Code - Insiders 1.21.0-insider (, 2018-02-09T06:14:31.856Z) OS version: Windows_NT ia32 6.1.7601 <details<summarySystem Info</summary </detailsExtensions: none Reproduces without extensions\nThanks! Very interesting. Can you somehow check which process has an open handle on ? I usually use for this.\nI have the same problem. Using Process Hacker, I got this result: !. Even after closing MEGAsync, I still get this problem. ! Here's the content of the log file: The last line means .\n!\nWhen VS Code isn't running, I can move/rename this file without problems.\nBTW, my OS is Windows 7 Pro x64, not \"Windows_NT ia32 6.1.7601\" as reported by VS Code. What's your OS?\nI'm on Windows 7 Pro x86 (6.1.7601 Service Pack 1 version 7601). I haven't tested on other architectures yet.\nLove it that you guys are already collecting stuff for me. I'm getting a Windows 7 image and trying it out. Can you also give me the list of extensions you currently have installed?\nIt works for me: Windows 10 Home(Build .rs2_release.-1834) I'm paying attention to the next updates, perhaps I can give you the needle of information.\nhas no extensions it seems (according to his first post). For my part, I have plenty ones: <details<summaryExtensions</summary- Bracket Pair Colorizer C/C++ C# Clang-Format CMake Code Runner cpplint Debugger for Chrome Doxygen Doxygen Documentation Generator Git History Git Project Manager gitignore GitLens - Git supercharged HTML CSS Support HTML Snippets IntelliSense for CSS class names JavaScript (ES6) code snippets jshint LaTeX Compile LaTeX Preview LaTeX Workshop latex-formatter Markdown All In One Markdown PDF Markdown Preview Enhanced markdownlint mssql npm One Dark Pro PHP Debug PHP IntelliSense PowerShell Python Unicode Latex VS Live Share vscode-icons vscode-pdf </details\nI could easily reproduce in Windows 7!\nPerfect :)\nI am having an issue updating Visual Studio Code - Insider's Build,"}
{"_id":"doc-en-vscode-ac8b775cf2b5bf963057112a8d65c42984dc8006deaa46a30dbdf569c3b10721","title":"","text":"The log output from the installer is shown below: Feb 12 13:40:40.605 INFO Starting: C:Program FilesMicrosoft VS Code InsidersCode - , true Feb 12 13:40:40.668 INFO Checking for running Code - processes. (attempt 1) Feb 12 13:40:40.681 INFO Code - is running, wait a bit Feb 12 13:40:41.182 INFO Checking for running Code - processes. (attempt 2) Feb 12 13:40:41.193 INFO Code - is running, wait a bit Feb 12 13:40:41.694 INFO Checking for running Code - processes. (attempt 3) Feb 12 13:40:41.706 INFO Code - is running, wait a bit Feb 12 13:40:42.206 INFO Checking for running Code - processes. (attempt 4) Feb 12 13:40:42.218 INFO Code - is running, wait a bit Feb 12 13:40:42.719 INFO Checking for running Code - processes. (attempt 5) Feb 12 13:40:42.729 INFO Code - is running, wait a bit Feb 12 13:40:43.230 INFO Checking for running Code - processes. (attempt 6) Feb 12 13:40:43.240 INFO Code - is running, wait a bit Feb 12 13:40:43.741 INFO Checking for running Code - processes. (attempt 7) Feb 12 13:40:43.749 INFO Code - is running, wait a bit Feb 12 13:40:44.250 INFO Checking for running Code - processes. (attempt 8) Feb 12 13:40:44.258 INFO Code - is not running Feb 12 13:40:44.267 INFO Starting update, silent = true Feb 12 13:40:44.267 INFO doupdate: \"C:Program FilesMicrosoft VS Code InsidersCode - \", Feb 12 13:40:44.373 INFO header: Header, id: Inno Setup Uninstall Log (b) 64-bit, app id: {1287CAD5-7C8D-410D-88B9-0D1EE4A83FF2},"}
{"_id":"doc-en-vscode-20430c19ecdb1502c9c232f48145a37491c12880d49d28aa0afae5770154d4b3","title":"","text":"app name: Visual Studio Code - Insiders, version: 1048, num recs: , end offset: , flags: 0x35, crc: 0x545ea7d9 Feb 12 13:40:44.374 INFO numrecs: Feb 12 13:40:44.374 INFO moveupdate: \"C:Program FilesMicrosoft VS Code Insiders\", _ Feb 12 13:40:44.374 INFO Delete: \"bin\" (attempt 1) Feb 12 13:40:44.374 INFO Delete: \"Code - \" (attempt 1) Feb 12 13:40:44.425 INFO Delete: \"Code - \" (attempt 2) Feb 12 13:40:44.626 INFO Delete: \"Code - \" (attempt 3) Feb 12 13:40:45.077 INFO Delete: \"Code - \" (attempt 4) Feb 12 13:40:45.877 INFO Delete: \"Code - \" (attempt 5) Feb 12 13:40:47.128 INFO Delete: \"Code - \" (attempt 6) Feb 12 13:40:48.929 INFO Delete: \"Code - \" (attempt 7) Feb 12 13:40:51.379 INFO Delete: \"Code - \" (attempt 8) Feb 12 13:40:54.585 INFO Delete: \"Code - \" (attempt 9) Feb 12 13:40:58.636 INFO Delete: \"Code - \" (attempt 10) Feb 12 13:41:03.636 INFO Delete: \"Code - \" (attempt 11) Feb 12 13:41:03.650 ERRO Access is denied. (os error 5) I suspect that this has quite a bit to do with how this laptop is configured by our IT dept. I am connected to a local domain with standard user privileges. In order to install any software on the laptop I am required to enter my local administrator account privileges. VSCode installs and runs just fine, the issue occurs when VSCode is self-updating. Once VSCode is loaded, it reports that it has an update and I click \"Install Update...\" when I click on the gear icon. VSCode then downloads the update."}
{"_id":"doc-en-vscode-ed0bb3a7b78978c1599802c05adf11e297d9d301069d0a7579e1931a7110ea92","title":"","text":"When it completes the download, it requests that I restart VSCode and that's when this error is generated. I've tried running VSCode as the local administrator and follow the same steps above, but the issue still persists, any help that you can provide will be much appreciated!\nWhat is your Windows version?\nOh, it looks like is loading up that DLL! Gotta figure out how to prevent it from doing so.\nI saw your commit I tried to update my VSCode application after that but it doesn't seems to works. Though, I don't have the same errors. When I hit \"Restart\", I got this message error: ! The differences between the old problem: There is no more the little window telling that VSCode is updating (see below) ! The log file is different: EDIT: I'm still on the same architcture. Windows 7 Pro x86 (6.1.7601 Service Pack 1 version 7601)\n- Windows 10 / Version 1703 / OS Build .850\nEasy, I still haven't pushed the fix.\nOh... Indeed! Sorry about this, I thought changes were effective since I didn't get the same errors. I wanted to provide a little more information not putting any pressure on this. Thanks for your involvment in this issue, I'll be more careful next time! :)\nOK pushed a fix to . Guys, tomorrow there'll be a new version. The background update step to get that version, from the current one, will still fail. But background updates should work successfully from that build onwards. So, make sure you get that build from tomorrow and try to get a background update Thursday or Friday. Let me know how that goes.\nYour issue is separate. Let's move our discussion over here:\nNothing failed, it has simply successfully updated. :+1: !\nAlright, I uninstalled VScode yesterday, reinstalled it and today, the background update worked, just as you said. Thanks once again! o/\nMarking as verified. I use background update on Windows and it doesn't fail for me."}
{"_id":"doc-en-vscode-ed9e046681539778e43716cce0b7a44112b37d5252b367b48052950f4d01aae3","title":"","text":"Opening the view menu I only see them screaming at me due to their size. Can we somehow decrease their size. The native mac arrows are slightly smaller. While visual studio on windows uses a much smaller version ! !\nVSCode uses Electron's toolbar if I'm not mistaken. It is basically menus in Chromium and the drop down menu in Chrome, which have arrows larger then those shown in the screenshots. So unless the toolbar can be customized, I don't think it's possible to tweak the arrow size without creating a custom toolbar. Please correct me if I get anything wrong. Thank you.\nThis is the custom toolbar on the windows we are currently working on. So we could customize it here imho\n+1 I think the arrow could be reduced a bit"}
{"_id":"doc-en-vscode-1e70b0091ee1ba7cc9d2e3ba266c2bdf6859056fd7a0a4dd9b53589dea858494","title":"","text":"Here's a recording demonstrating Insiders (left) and previous Stable 1.74 (right): https://user- Steps: the SCM view and add a long line the width of the side bar such that the text wraps Notice how: When selecting the entire buffer, the selection expands beyond the text When selecting a subrange, sometimes the start position of the selection moves The rounded corners is generally broken: not all corners are rounded any more. This applies even for 1.74.\npoints to and a manual bisect points to being the first bad commit\nReverting from the change fixes the rendering problem. This diff fixes the rendering problem: The root problem here is that it is not supported that the editor background color is transparent. The class name \".monaco-editor-background\" is used to render rounded corners and that stops working if it is transparent.\nThank you Tested the changes the created a PR.\nThanks for fixing. This has been on my list for weeks and I've just been, well, slammed"}
{"_id":"doc-en-vscode-2fe84bbe663ec9d431c9ef37a3217bf1e42810942f29316af8e9444c61c15dbd","title":"","text":"Type: <bBug</bwith the following code in a javascript file: the symbol \"UserClient\" which is missing an import is not automatically imported. if i only remove the JSDoc Comment then it is already working. if i remove the return statement it is also working. i tried it with all extensions disabled, nothing. please fix this. VS Code version: Code 1.72.2 (, 2022-10-12T22:15:18.074Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (11)</summaryExtensionVersion ------ lit-html1.11.1 vscode-html-css1.13.1 lit-lang0.0.7 prettier-vscode9.9.0 csharp1.25.0 powershell2022.10.0 vscode-xml0.22.0 lit-plugin1.2.4 markdown-preview-enhanced0.6.3 blueprint3.0.0 markdown-all-in-one3.4.3 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nPlease share a minimal, self contained project that demonstrates the issue\nThanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our . Please take the time to review these and update the issue. Happy Coding!\nnote: is just a bundled version of the lit-html plugin. the project i'm using works has the requirement to work without any kind of build so we bundled the only npm dependency it had into this file. still looking for a better solution though...\nI'm facing the same issue. and get executed as expected, but seems to not working. To reproduce, just open a TS project, set the to the option, remove an import from any source file and save. The imports gets organized but the missing imports doesn't get imported.\nI even noticed that it still works under certain circumstances. like in my demo project, if you remove the JSDoc comment. something in the code context seems to be killing the import feature. but manual import still works (like with hovering the item, quick fix, import)\nany updates, info requests, anything? did you find a lead, can you work on it?"}
{"_id":"doc-en-vscode-0d254c703af8fa971919e3fb560cb4dee4637da162106f15766b84efa204ed22","title":"","text":"can you fix it?\nI can confirm this issue, I can trigger the autocomplete for the import with either ctrl+space or ctrl+. however it is not automatically on save even with enabled. This feature was working for me some time ago, but I can no longer get it to work.\nAny fix yet?\nChanging the order to solved the problem for me."}
{"_id":"doc-en-vscode-3a36a8ca017c13418e69300f740fc1bfcebbc6337db56bdd7e992923bac49437","title":"","text":"<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --This could include platform specific instructions. Curious to know which platforms we're talking about here... Windows for sure but what else? Does Raspbian ship git?\nHi, I would like to work on this please assign this to me.\nthanks! We cannot assign you as you are not a member of this issue, but please feel free to submit a PR. The relevant code is here:\nI can take this up if it's not already done. Could you elaborate on what new step needs to be ?\nhello guys, i'm really trying to get started in contributing to open how i get started here?\nHello this is my first time contributing to an open source project and I'm willing to work on this issue. I just set this repo up on my machine and its working. I had a look at the file you've shared and there are conditions for few steps which checks if git is missing. So, I tried simulating the inexistence of git just by disabling it in vs code settings. Is that fine? And also, should there be a button which says \"Install Git\"? If yes, what should it be linked to? !\nWe can use I recommend testing this by fully removing git if at all possible, otherwise there my be unexpected behaviors when a new users is actually running this for the first time.\nIs this complete, or I can still work on this?\nI am not aware of any work done here.\nCould you assign it to me? I would like to work on this quickly. Edit I guess, Only members can be assigned. So, I will open a PR and link to this issue.\nHello, I'm sorry I should've kept you updated but I've made those changes and I just have to test it out by uninstalling git.\nI have tested with uninstalling git. Can I take this?\nOmg I just did that to push. What do we do?\nJust tested this on Windows, and the \"Install Git\" item is marked as ticked when you click on the \"Install Git\" button regardless of whether you have actually installed Git - is this expected?"}
{"_id":"doc-en-vscode-1ec6f52be55196f53f62885b1f90e4dcd0616e68e3a981dfb6d9d2595c09c9a7","title":"","text":"Or would it be better to only tick the button when an installation of git is detected? The screenshot below shows that I clicked the button but didn't actually install Git. The item is ticked but attempting to run git in the terminal (or git pane) fails !\ngood idea, changed so that the item checks off when git is initialized.\nOhh yaa..I did not notice that Thanks for fixing it ! :)\nI uninstalled git and reloaded to see the new \"Install git\" item. Then, I installed git, but the item wasn't checked off, and I wasn't sure what to run to get the item to check off. After reloading again, I didn't see the item. I uninstalled git again and reloaded. The item showed up, but checked off this time. I unchecked the item and reinstalled git, and ran git in the terminal, and the item still wasn't checked off. I switched workspaces, and I didn't see the item again.\nCan we have which checks if git is installed when we reach this step?\nNo, it should work based on context keys, which have change events.\nOhh okay\nHi. What is the current status of this issue? Is there a bug for the current implementation? I can work on it if no one is working and someone gives me the context. Thanks.\nIsn't it the expected behavior? If VS Code is open and git is installed, even Source Control tab doesn't notice this change; a reload is required for that. If this is not the expected behavior and automatic discovery of git existence is necessary, then this tab should also be fixed. I assume the item can be checked off by clicking the checkbox or Mark Done text below. This is also an expected behavior, I think. For example; you customized your shortcuts using Customize your shortcuts, then this item is checked off. After then you reset shortcuts but the item is still checked off. You probably doesn't expect the opposite. Because you understand how to configure the option this item provides. I think the key of checking off here is understanding the option. Otherwise most items may be reversed and should not be checked off after the reverse. On the other hand I think your statement shows that the natural flow of the Install Git item doesn't suit well to a checklist."}
{"_id":"doc-en-vscode-320df0282fc47ccbb0ac3219c9777fbd9f0b4d7c3c028f3ad67960181ce04d28","title":"","text":"I am not able to test this at the moment due to some system issues, but I would consider the following sufficient for marking this complete: a user does not have installed, a tile is shown pointing them to steps for installing git and notifying of a need to reload the window to complete installation. A button/link could be shown to trigger a reload. completing the installation and relaunching VS Code, the tile for installing git is no longer shown, and the tile explaining git use inside VS Code is shown instead. I believe today we have this minus the part where we explain that a reload is required to complete git installation and provide UI to facilitate the reload.\nUpdated step to include link to ."}
{"_id":"doc-en-vscode-42767a96b89915616f890107ceb1c6db3503aff6a2b8d7b3137085f7fa39e5bb","title":"","text":"<!-- 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: V1.81.1 OS Version: Linux kkuser-virtual-machine 5.15.0-83-generic ~20.04.1-Ubuntu SMP Mon Aug 21 14:00:49 UTC 2023 x8664 x8664 x8664 GNU/Linux Steps to Reproduce: are constant changes in attribute states in the treeview calls to () functions result in memory leakage\nThanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.82.2. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!\n<!-- 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!"}
{"_id":"doc-en-vscode-c08b9f9c54b4811aaada5960dd97540b4a6c1e41ba41922e0d30190cf79621c4","title":"","text":"<!-- 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 (N/A) <!-- 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.88.1 OS Version: macOS Steps to Reproduce: the shell, run , UPDATE: the system need to have a existing tunnel already running that the machine name is always inferred from Hostname instead of the machine name set through <img width=\"931\" alt=\"image\" src=\"\"\nUpdate: I noticed the \"Connected to an existing tunnel...\" line, and if I kill the tunnel first using and run the same command, it would correctly set the machine name. I'll update the issue description to reflect that.\nYea, if there's an existing tunnel we just connect to it and never enter the process in which the name would be set. Renaming a running tunnel is also possible but could lead to unpredictable side effects. We should just log a warning in this case.\nI'm not seeing any warning:\nstill no warning. I made sure I was on the latest !\nin your screenshot you can see the warning which is what I for this."}
{"_id":"doc-en-vscode-75cd81cff3d3459d6d488824d4bac092e74cd758035c87425f1a656df4b9d412","title":"","text":"<!-- 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?: Unknown- repro uses a virtual workspace <!-- 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.80.0 Commit: Date: 2023-07-04T15:06:02.407Z Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.80.0 Chrome/108.0.5359.215 Electron/22.3.14 Safari/537.36 Steps to Reproduce: a Github repository using \"GitHub Repositories\" extension, eg microsoft/vscode \"Settings (JSON)\" and add all tabs except Getting Started Extensions panel, search for \" typescript\" the Typescript and JavaScript Language Features extension and Reload Window \"Settings (UI)\" and search for typescript- no settings appear. Close \"Settings (UI)\" Extensions panel, search for \" typescript\" and re-enable the extension. Note, the extension activates immediately, the panel doesn't recommend Reload Window. \"Settings (UI)\" and search for typescript- Actual: no settings appear. Expected: settings appear"}
{"_id":"doc-en-vscode-6d747b98de0f6adac3230566fc0d3ee26844bd8870820588c64f53839c273dc4","title":"","text":"<!-- 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: Insiders 1.71 OS Version: Ubuntu 18.04 amd64 Steps to Reproduce: to install latest code-insiders packages from MS repository () The issue is that with the dependency on Debian derivatives changed to which only exists on newer releases (20.04 and later I think). I realise that support for Ubuntu-Ancient is low on the priority list, but I am sadly stuck with it, and would appreciate if there was a workaround. Installing newer libgcc releases as suggested in some places easily leads to a very broken system.\nThis is a side effect of now using bullseye sysroot, we should apply the following change https://chromium- to our debian calculate package deps."}
{"_id":"doc-en-vscode-3543955b6cddb27c76b2f9bf4c0a32596204d9cce4ece3fa7c619be1dba1c938","title":"","text":"empty profile open terminal, run or any other command that prints something press to clear the terminal :bug: the keyboard system is waiting for chord to be completed"}
{"_id":"doc-en-vscode-1b2ca4430abf1df5aad073fd62956f1abe1f76be8bfbadc0b8b373f49c0b3a17","title":"","text":"When resizing the windows while the accessible help menu is visible, the help menu slides diagonally: !"}
{"_id":"doc-en-vscode-c98200368b2ce8b594885ee019f49ea2c360e40de50afe73a7146de99b7ac82c","title":"","text":"Repro: Alt+F1 ! If should be in the center as that's the most obvious location Version: 1.80.0-insider (user setup) Commit: Date: 2023-06-28T08:01:04.380Z Electron: 22.3.14 ElectronBuildId: Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.\nPutting it here makes the most sense to me because that's where we put other components - like the quick pick. I want to get feedback from low vision users\nThat's fine, but if you're styling like the command palette we should position it in a similar way ! So below the title bar and not quite and maybe a little less wide\nRe , we should also size the height similar to quick pick\nBut shouldn't the height be determined by the contents?\nyes, but have a similar height cap to the quick pick\nWe should also use the same font as the quick pick\nI think you've convinced me - this should be in the center.\nPersonally I preferred the top position, I'd just render it as the quick pick: Same position and same style. VS Code does not have many vertically centered dialogs. If you want to make it vertically centered, I'd suggest to align it with other vertically centered dialogs, like the trust dialog (notice the background shadow): ! ! Generally, I think, if there is no particular reason to be different, we should try to have a consistent UI throughout the entire product. I'm still in favor of the top position, as the workspace trust dialog is the only vertically centered dialog I know of and it is strongly modal (you have to click one of the buttons to make it disappear). FYI\nFading the background like the trust dialog is good imo, I like centered as it's a very special mode and it's modal as in clicking outside will always dismiss it, unlike the quick pick which may not dismiss when clicking outside. In the end the visual appearance isn't that important really, I just want it to be very obvious when the accessible view is up.\nI agree that we should try to align with existing design. My personal preference is to have it positioned like the quick pick."}
{"_id":"doc-en-vscode-b14aa818500acce731e16614bb7efc79709d2489922085856b2c0762d1b116b6","title":"","text":"But in the end, it is not super important as pointed out.\nOne issue with doing it as the quick pick is it would look wrong being so narrow, and making is narrow would make it less accessible, say if a low vision user was using it.\nNot sure it needs to be as narrow as quick pick. I just think the positioning of the quick pick is fitting. So the top and center. It could be wider or longer.\nNow that we have the focus border, it is more obvious, so fine to be at the top IMO.\nThis is still not fixed imo, it should follow quick pick and look like this (native title bar): ! Not this (custom title bar): !\nVerified off main :+1:"}
{"_id":"doc-en-vscode-d0162bc86736d9c67f8d2692239ca1c4f698884c7eec8e9dee3be16886ef7140","title":"","text":"! The highlighting is important to understand which conflict in the bottom view corresponds to which conflicts in result. I think the change of the color of the dashed border is difficult to notice."}
{"_id":"doc-en-vscode-0f3df0793896095ab05c8ac448c4e7015f8b82dd25c8500ca3d6d015426bfbd2","title":"","text":"We can add the same regex validator for the terminal find widget input box if the underling regex engine is JavaScript regex. Close this one if we are using another regex engine somehow in\nSo in the terminal widget show things like this and reject the search? <img width=\"238\" alt=\"screen shot 2018-10-11 at 11 58 06 am\" src=\"https://user-\"\nI would like to try and work on this feature. Could someone tell me where to start working on this feature?\nthe terminal find widget code is here: It extends the SimpleFindWidget: Not sure where the validator is but I'd look around the and files."}
{"_id":"doc-en-vscode-1f5fa2d5eb7f938c377301bbbd9b8fa45634a5976f9fe3b83daddb02818cc098","title":"","text":"Issue Type: <bBug</bWith the latest update, active and inactive menu in settings UI does not look any different from each other VS Code version: Code 1.66.0 (, 2022-03-30T05:50:14.623Z) OS version: WindowsNT x64 10.0. Restricted Mode: No Remote OS version: Linux x64 3.10.0-1127.10.1.el7.x8664 <details<summarySystem Info</summary </details<details<summaryExtensions (42)</summaryExtensionVersion ------ LogFileHighlighter2.15.0 remotehub0.28.0 better-cpp-syntax1.15.13 blockman1.5.7 jupyter-keymap1.0.0 remote-containers0.231.1 remote-ssh0.78.0 remote-ssh-edit0.78.0 remote-wsl0.66.0 remote-repositories0.4.0 material-icon-theme4.15.0 rewrap1.16.3 vscode-icons11.10.0 vscode-todo-highlight1.0.5 path-intellisense2.8.0 vscode-clock0.0.1 gitlens12.0.5 systemverilog0.12.1 prettier-vscode9.5.0 seito-openfile1.8.8 html-preview-vscode0.2.5 jira-plugin0.22.2 gitlab-workflow3.41.2 gc-excelviewer4.2.54 beautify1.5.0 path-autocomplete1.19.1 svg1.4.17 vscode-jira0.6.0 restructuredtext183.0.0 python2022.4.0 vscode-pylance2022.3.4 jupyter2022.3. jupyter-renderers1.0.6 cpptools1.9.7 veriloghdl1.5.3 subtle-brackets3.0.0 LiveServer5.7.5 code-spell-checker2.1.11 vscode-input-sequence0.2.0 simple-rst1.5.2 vscodeintellicode1.2.17 better-align1.1.6 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\n/gifPlease\n! ! ! !"}
{"_id":"doc-en-vscode-bd3797c6f34f9dcf9289989fb68b4d6d2360088bb2b9a1e41e2236d4404553a8","title":"","text":"By \"active and inactive menu\" I assume you are referring to the tabs labelled \"User\", \"Remote\", \"Workspace\" etc. Which color theme are you using? Do you also see the issue when using the default themes (Light+ and Dark+)?\nYeah, I am referring to \"User\", \"Remote\", \"Workspace\" etc. I am using Night Owl Light Theme\nDoes this problem occur when you don't have a multi-root workspace open?\nThe issue is seen only with a multi-root workspace. Is it a known issue?"}
{"_id":"doc-en-vscode-d75ba56f60abff9b3b5c1cb778978285b99b336934d6409fecaa44ce6b0fbfc7","title":"","text":"<!-- 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: 1.77.3 OS Version: Ubuntu 20.04.6 Steps to Reproduce: VSCode on an Ubuntu computer (or on Windows using WSL) the built-in terminal the command and paste the following 39-character string into nano: : nano shows the error message \"Unknown Sequence\". Can no longer interact with the terminal, need to kill it and open a new one More details: nano version 4.8 This does not happen in nano using an external terminal. Only in VSCode's built-in terminal This does not happen for any other length of string, even other multiples of 39 This does not happen in other CLI text editors, such as vim\nI can confirm this issue on Windows using WSL.\nIt happens with other 39 long strings as well. It also happens when not using WSL. Copying more characters solves the problem. For us it also happens with multiples of 39 (e.g. 156 characters, line breaks included)\nWhen trace logs are enabled this is the exact sequence we send: Compared to 1 less : Note that the 200/201 wrapped around it is bracketed paste mode (which I just a way to disable so that may help ). So this seems to be either a problem with one of nano, conpty or node-pty.\nI also just ran into this. I'm on Windows 10, using Remote - SSH plugin to connect to an Ubuntu 22.04 server. Right-click to paste in Nano, terminal locks up, have to Kill it."}
{"_id":"doc-en-vscode-64bd95e4f8b4f6467bdfa6dd1584ba008e0ef1bcfab029d6b8c80860d4dead0e","title":"","text":"Add/remove one character from the string and try again, works.\nWe closed this issue because we in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider. If you wonder what we are up to, please see our and . Thanks for your understanding, and happy coding!\ni opened a bug on gnu nano's bugtracker:\nI think I found a workaround, but haven't tested it: vscode , nano doesn't deal well with across writes and it is apparently difficult to fix in nano. vscode could split writes differently, using this algorithm that keeps escape sequences at the beginning and end unsplit (like bracketed pastes):\ngreat info, we should definitely do this . I'll probably tweak your proposal a little to try catch escape sequences in the middle too.\nI don't expect input sizes to be 50 bytes except when pasting, when pasting there should only ever be an escape sequence at the beginning and end, never in the middle (terminal apps are unlikely to deal well with pasting a string containing escape sequences anyway).\nunless I missed something in the issue you linked, it's not that they need to be on the boundaries of the text but need to be included entirely in that string and not clipped?\nyes, escape sequences need to be contained entirely in one write syscall. basically I am saying you shouldn't have escape sequences in the middle of a long input, so you don't need to look for them to avoid splitting them, they should only occur towards the ends of a long input or in a shorter input.\nNano's workaround was released in Nano 8.0:"}
{"_id":"doc-en-vscode-f68640296a916587ae56c36743e167b77be812409a09338b73697ac096e60545","title":"","text":"Type: <bBug</bI have an extension that has been making use of the executeCommand API for \"vscode.executeDocumentHighlights\" to get the for different positions in a file. Essentially calling something like below: After a recent VsCode update, the API is no longer returning any values and simply returns . I'm not sure the best way to provide a reproduce for this. I originally encountered the problem with a custom extension/language server. However the problem also appears to occur when calling the same command on a simple typescript file so I believe it's a general issue rather than any thing specific to my environment. I've had a quick search in the VsCode sources and I have a feeling this commit might be responsible: I think the problem is due to now returning instead of . When it gets to the ApiCommand layer I think the function fails and returns as the function has been given a instead of VS Code version: Code 1.84.2 (, 2023-11-09T10:51:52.184Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (30)</summaryExtensionVersion ------ vscode-markdownlint0.53.0 vscode-eslint2.4.2 mfcobol1.0.53 mfenterprise1.0.53 vscode-language-pack-ja1.84. csdevkit1.0.14 csharp2.12.19 vscode-dotnet-runtime2.0.0 vscodeintellicode-csharp0.1.26 python2023.20.0 vscode-pylance2023.11.10 jupyter2023.10."}
{"_id":"doc-en-vscode-06d9ff9cbe8c78b303a1ea1702de4dee8deac625b76237defebf727762ec7883","title":"","text":"jupyter-keymap1.1.2 jupyter-renderers1.0.17 vscode-jupyter-cell-tags0.1.8 vscode-jupyter-slideshow0.1.5 remote-ssh0.107.1 remote-ssh-edit0.86.0 remote-wsl0.81.8 powershell2023.8.0 remote-explorer0.4.1 test-adapter-converter0.1.8 java1.25.0 intellicode-api-usage-examples0.2.8 vscodeintellicode1.2.30 vscode-java-debug0.55.0 vscode-java-dependency0.23.3 vscode-java-pack0.25.15 vscode-java-test0.40.1 vscode-maven0.43.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nThanks This is a good find!\nTo verify: make sure this test has passed:"}
{"_id":"doc-en-vscode-807257615cf28e1ed9e1e77658f928f9a7f506dd1cba86b2a47ca73cb93dd9a4","title":"","text":"Type: <bBug</b I am not sure whether the insiders version reflects the up-to-date patch though, does not seem to work in Powershell. I have noticed that this works in my remote z shell though. VS Code version: Code - Insiders 1.85.0-insider (, 2023-11-03T15:11:12.179Z) OS version: WindowsNT x64 10.0. Modes: Remote OS version: Linux x64 4.18.0-477.27.1.el88.x8664 <details<summarySystem Info</summary </details<details<summaryExtensions (104)</summaryExtensionVersion ------ aiprm-lang0.0.2 Bookmarks13.4.2 spellright3.0.118 mermaid-markdown-syntax-highlighting1.5.3 vscode-firefox-debug2.9.10 codespaces1.16.2 remotehub0.62.0 overleaf-workshop0.4.1 easy-snippet0.6.3 scheme0.2.0 better-cpp-syntax1.17.2 lilypond-snippets0.1.1 vscode-edge-devtools2.1.3 jupyter-keymap1.1.2 remote-containers0.322.0 remote-ssh0.108. remote-ssh-edit0.86.0 remote-wsl0.81.8 vscode-remote-extensionpack0.24.0 azure-repos0.38.0 remote-explorer0.5. remote-repositories0.40.0 vscode-serial-monitor0.10.0 vscode-speech0.3."}
{"_id":"doc-en-vscode-7acd1d2552dc6e7bbee350b75bb406230ed5d4339aee830f8c0cf553ca989a91","title":"","text":"multi-command1.6.0 errorlens3.15.0 Bookmarks13.4.2 openscad1.2.2 zoterolatex0.4.1 mermaid-markdown-syntax-highlighting1.5.3 codium0.7.13 doxdocgen1.4.0 vscode-markdownlint0.52.0 vscode-eslint2.4.2 vscode-quick-select0.2.9 vscode-deno3.26.0 gitlens14.4.1 EditorConfig0.16.4 prettier-vscode10.1.0 shell-format7.2.5 vscode-google-translate1.4.13 codespaces1.16.2 copilot1.133.531 copilot-chat0.11. remotehub0.62.0 vscode-github-actions0.26.2 vscode-pull-request-github0.77. cslpreview0.2.2 path-autocomplete1.25.0 latex-workshop9.14.1 lilypond-syntax0.1.1 scheme0.2.0 better-cpp-syntax1.17.2 vscode-lua-format1.3.8 lilypond-formatter0.2.3 lilypond-pdf-preview0.2.8 lilypond-snippets0.1.1 vslilypond1.7.3 git-graph1.30.0 vscode-docker1.27.0 black-formatter2023.4.1 flake82023.10.0 isort2023.10.1 python2023.20.0 vscode-pylance2023.11.10 jupyter2023.11."}
{"_id":"doc-en-vscode-8a42d6e81894f1b05e21246c569146bbc3764bdb5e674f1e6e1540c2cdb56e47","title":"","text":"jupyter-keymap1.1.2 jupyter-renderers1.0.17 vscode-jupyter-cell-tags0.1.8 vscode-jupyter-slideshow0.1.5 azure-repos0.38.0 cmake-tools1.15.31 cpptools1.17.5 cpptools-extension-pack1.3.0 js-debug-nightly2023.11.217 remote-repositories0.40.0 vscode-github-issue-notebooks0.0.130 vscode-selfhost-test-provider0.3.20 vscode-serial-monitor0.10.0 vsliveshare1.0.5892 autodocstring0.6.1 pandocciter0.10.3 shiny-python0.1.5 shinyuieditor0.5.0 quarto1.106.3 r-debugger0.5.4 java1.24.0 vscode-xml0.26.1 r2.8.2 multi-command1.6.0 vscode-deepl1.0.6 lua3.7.0 latex-utilities0.4.10 cmake0.0.17 errorlens3.15.0 intellicode-api-usage-examples0.2.8 vscodeintellicode1.2.30 vscode-java-debug0.55.0 vscode-java-dependency0.23.2 vscode-java-pack0.25.15 vscode-java-test0.40.1 vscode-maven0.43.0 markdown-all-in-one3.5.1 grammarly0.24.0 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nit is working for me on windows with PowerShell. could you share a gif?\n!\n-- Also, I have noticed that sometimes the first letter typed in Accessible View is not bypassed as demonstrated in the z shell.\nThanks for the gif, yeah, it's not working for you. I cannot reproduce even when I use a terminal in the editor area. Could you pls set terminal log level to debug, repro, and provide me with those?\nLooks like shell integration isn't working properly for you for some reason, which is why this isn't working. We run the open command , so that's not happening.\nAnd yeah, I can reproduce sometimes the key not getting sent to the terminal."}
{"_id":"doc-en-vscode-a75f56ccd701329b7403ca9c66a240734eec1730db6ff74349d99df9a310925f","title":"","text":"It's a timing issue related to the context view that is shown.\nI'll split that issue out\nAs expected, your logs do not show , which explains why it's not working for you.\nI wonder if is loaded for you. That would be the only way that event wouldn't happen\nCan you pls run and provide the output?\n!\nSo is disabled for you, which is why this isn't working.\nIf you add this line to your , it will work\nis disabled by default when screen reader is used, and enabling it does not resolve the issue. Please see the gif: !\noh, seems we'll have to use instead for this case then.\nI still cannot repro. I have the likely fix, so you'll be able to verify it tomorrow."}
{"_id":"doc-en-vscode-3401c82d33a003fa02565e4ad56dceb58f1a54c2c6046435d34acc72d57867ad","title":"","text":"Type: <bBug</bVS Code (with or without extensions disabled, makes no difference) File -Preferences -Settings blank UI with no actual settings in it. ! If you leave the settings tab open and restart vs code (such that it reopens the settings tab automatically on restart) the settings GUI will be there, but all the extension settings will be missing (observe that it is missing from the menu here): ! If I then close and reopen settings they will again be empty. VS Code version: Code 1.84.2 (, 2023-11-09T10:50:47.800Z) OS version: Linux x64 6.2.0-36-generic (Ubuntu 22.04 LTS) Modes: <details<summarySystem Info</summary </detailsExtensions disabled <!-- generated by issue reporter --\nI also tried with to run this on the nVidia GPU instead of the built in Intel GPU. Makes no difference.\nAfter running the command \"Developer: Toggle Developer Tools\", do any errors show up under the Console tab?\nYes I got 3 errors, they all seem related to that I'm behind a corporate proxy though. Note that I ran this with , but I still get errors related to extensions. I find this very strange ! ! !\nWhen I'm not behind the proxy, settings work as expected. I find it very odd that VSCode would need to call out to the internet just to open settings. Opening the marketplace for extensions I understand, but not settings. Especially since I can also open settings just fine if I'm completely disconnected. It is just if I'm connected via the corporate network that it falls flat on it's face. For some further debug information: We use Zscaler at my workplace, which acts as a transparent HTTPS MITM proxy (no need/not possible to set any environment variables, but you do need to install the CA certificate). The proper certificate is installed in the system certificate store () and that works as expected with other programs. Also, other internet features in VSCode work fine, such as github copilot. EDIT: I also tried some of the settings in the proxy section of the settings to see if it made any difference. They were all set to the default values before."}
{"_id":"doc-en-vscode-5b7247c7096549f29c9c14bf47221c0a8af5ca097008c04370a9062524495c6b","title":"","text":"made no difference made no difference is set, but I doubt I want to uncheck it if I understand it correctly. is set to override (default), and it sounds like it only affects extensions, so I didn't touch it. I don't see any option to manually add a certificate anywhere in the settings.\nBased on I found that does work. That is a bit of a sledgehammer though, and not really an ideal (or even slightly secure) solution.\nThe Settings editor currently recommends the Copilot extension when it's not installed, which lines up with the error messages you're seeing. I'll put up a PR that skips over showing that feature in case of networking errors.\nTomorrow's should contain the fix.\nwhat about the bit where it seems to ignore the root system certificates though? It seems there were actually (at least) two bugs here: one you fixed, where settings can't open when there are network errors fact that a corporate proxy with correctly installed CA certificates in the system store doesn't work. Presumably it isn't picking up the system CA certificates correctly.\nthank you very much my problem is solved after follow this step (Open VS Code disable all extensions disabled, and enable once again all extension then i am successfully able to see my settings))\nPlease see on how to add a root certificate for Chromium, that also applies for Electron-based applications like VS Code. The root certificate example is:\nThanks this works. I thought I had already it, since I it in Chromium. But of course on Ubuntu Chromium runs in a snap by default, so it didn't use the same store as VSCode..."}
{"_id":"doc-en-vscode-e28ed666496e39ffbc4b31969f62cfaa9f0f541da5286ea00c808d8a2cbac672","title":"","text":"Example block quote in the extensions page. <img width=\"375\" alt=\"image\" src=\"https://user-\""}
{"_id":"doc-en-vscode-6ea7d83fb797818cbfd11bcddb8d72fe8ade79b7fd49d69f78bb488ffbfd769c","title":"","text":"<!-- 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: 1.84.2 OS Version: Ubuntu 23.04 Steps to Reproduce: an editor the editor that a was created but not removed In Chrome devtools, the retainer chain points to : !\nI discussed with and when an editor is closed it is not disposed unless it is the last editor in the group and the group isn't the default group, so in the scenario described in this issue, the is still expected to exist. Here's how to check if the is being leaked: an editor. Check how many s you have. a second editor in a new editor group. the editor in the second group. Check how many s you have. If there is no leak, there should be the same number as in step 1. I have tested, and I don't see a memory leak from .\nThanks a lot for the info, it's really helpful! And apologies, you're absolutely right! I was so focused looking for something that would explain the two and didn't really think about anything else. Your steps make much more sense and with that I don't see a memory leak from . No wonder it took me so long to find the apparent source, when there is none... xD Thanks again!"}
{"_id":"doc-en-vscode-8b22bc7a9c8c1ed4ab932fbe1f11a2611ab8515df23f79eacf9647ba0e3b9a9e","title":"","text":"Type: <bBug</bis enabled. Ensure is set to , or (any option that will restore the last open window after quiting and re-opening VSCode). a terminal in the editor area, e.g. using the command \"Terminal: Create New Terminal in Editor Area\". Type something into the terminal e.g. . VSCode via \"Developer: Reload Window\". Note that the terminal tab in the editor area is still there (restored) after the window is reloaded. This is the expected behavior. VSCode then reopen the application. Note that the terminal tab is not present (is not restored) when the window is restored (and since there is no terminal tab, there is also nowhere to restore the session to ) . This is unexpected behavior as previously this terminal tab would be restored into the editor area, with its session history, even after quitting and reopening VSCode. Another terminal persistence bug on 1.74.0, also related to killing terminals: VS Code version: Code 1.74.0 (, 2022-12-05T16:37:54.581Z) OS version: Darwin arm64 22.2.0 Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (16)</summaryExtensionVersion ------ vscode-neovim0.0.94 calva2.0.321 file-browser0.2.11 portal0.35.0 viml0.1.7 prettier-vscode9.10.3 vscode-htmlhint1.0.4 vscode-sshfs1.25.0 ssh-config-syntax-highlighter0.0.4 sqltools0.26.0 sqltools-driver-pg0.4.0 errorlens3.6.0 learn-vim0.0.28 vspacecode0.10.10 whichkey0.11.3 markdown-all-in-one3.5.0 </details<!-- generated by issue reporter --\nI cannot reproduce that in Insider's https://user-\nhave you typed in the terminal before reloading? if not, that's by design\nPardon me I was unclear in the original writeup. The problem occurs in step 4 and is now reflected in edits above. Thank you! Regarding the direct question: yes, I have typed in the terminal before reloading."}
{"_id":"doc-en-vscode-200e3b044ead9ae24a3f9fa5a1a3caefc040d1b8c38cab902d43018f290daa2a","title":"","text":"/duplicate\nReviving editor-area terminals was working great in 1.73.x. This was marked as a duplicate of a feature request. Is it not a regression?\nCreated a PR with a possible fix\nVSCode v1.74.2 occurs the same problem, does the fix takes effect or I need to config some settings?\nThe fix will be available in 1.75 release or you can try it in insiders"}
{"_id":"doc-en-vscode-bafb13dde0052b78bd82fc1394458a1e2598fe104d991ad7561b31fbad5c5432","title":"","text":"When running unit tests:\nSimilar problem in\nThis is not coming from those tests, the ugly part is these errors just report async. I found the following tests to be the underlying cause: The best is to run and add a breakpoint here:\nI think I may have found a central fix..."}
{"_id":"doc-en-vscode-2f2ec050ffc791ae714dad7c13bbc4647fc9df76c61fd7819a4a6eaf040d729a","title":"","text":"Repro: Windows open test resolver window folder everything except !\nI'm not able to reproduce this, even when I select the entire series of subfolders before before deleting. Is this on a VM?\nNo folder, just test resolver. It's an easy repro for me: ! Code - OSS about: Version: 1.69.0 Commit: Unknown Date: Unknown Electron: 18.3.5 Chromium: 100.0.4896.160 16.13.2 V8: 10.0.139.17-electron.0 OS: Windows_NT x64 10.0.\nYour slashes are going the wrong way, which is suspicious. How do you launch Code - OSS?\nand then new test resolver window command\nI've repro'd the slashes, but nothing I try will cause the missing directories to repro. Only difference I see is that I am on Windows 11 and you are on 10. Can you try swapping the separator on the resource label formatter? If that doesn't resolve it then we'll set up some time to debug.\nI'm on Windows 11 too, 21H2, .739\nRegardless of the value above it doesn't work for both and . Is there anywhere of interest I can debug into? Where does the trigger character code live?\nWe debugged into this together, seems related to the being (or ) and not\nAfter our debugging yesterday this started to feel familiar:"}
{"_id":"doc-en-vscode-fca52ebaf6cde7b1cb7a5488ef6a619e6568bc00f2d07999e8312c0e1959240d","title":"","text":"Issue Type: <bBug</b(I have fixed this myself and will send a pull request in a minute) Steps to reproduce: accessibility mode in settings. a new document and type: to the beginning and press Ctrl+Right. Expected behavior: Cursor should jump to the letter w - that is the beginning of the second word. This behavior would be consistent with word navigation in most other Windows programs, e.g. notepad, MS Word, Visual Studio - just to name a few. Actual behavior: Cursor jumps to the space immediately after the first word, and the screenreader announces \"Hello\". The biggest problem with this behavior is that screenreader users would have to relearn how they make small edits in text files. For example, if I want to delete the word \"world\" in my example, I would go to the beginning of the line and press Control+Right until my screenreader announces the word I'm interested in. And then, assuming that cursor at this point is at the beginning of the word, I would press delete 5 times. However, in VSCode the cursor would be at the end of the word, and I would end up deleting wrong part of the line. VS Code version: Code - Insiders 1.40.0-insider (, 2019-10-25T14:03:31.497Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </detailsExtensions: none <!-- generated by issue reporter --\nFYI, I found related discussion here: , but that thread is now locked."}
{"_id":"doc-en-vscode-0f7b581aa667d8209d2061b45fb246a8b30d297a2281343337b6cb31ad835498","title":"","text":"testing It would be nice to have a link on this prompt to open the workspace . that way i can see what was done. !\nLink in the text mostly is not possible, as that works only for actual links. We might have to add a button that says which opens the file that was edited."}
{"_id":"doc-en-vscode-3b9fdf36bab60fc30c121c9d63578242f8b301fc2d95f93c614f7aeabf663911","title":"","text":"Originally filed here Problem: Notebook kernel pre-load scripts are now defined statically via the contribution However VS Code throws a 401 error when loading resources from within the Jupyter extension, If however we have a dummy script file (in the Jupyter extension directory) that is defined as a in the VS Code API , then all resources from Jupyter extension directory are loaded I.e. using the above API in some way registers the Juptyer extension directory as a supported for scripts, and using the static contribution does not.\nI have a work around in the Jupyter extension right now, i've a dummy placeholder script that does nothing,\nCan you share steps to reproduce this with the fix in place? Also, does this happen on normal desktop too, or only sshe Unclear why this is not working as we should add preloads to the local resource roots:\nHere are the steps Install Python Install VS Code insiders and latest pre-release versions of Jupyter and Python NOTE: Install the pre-release version of Jupyter extension that is 2 days old Add the following setting into vscode Create a python env and install the following dependencies You can use the command to create a directory with Pytohn in a particular workspace folder (optionally you can use Python extension to do this for you) Run the following code in a notebook pointing to the above venv (i.e. select the above venv as a kernel) You might get prompted to enable CDN download, hit cancel for that The widget will not load, network tab in vscode will display a 401 error Note: This is now working in the latest pre-release version of Jupyter extension\nI believe the broken version is be but I'm having trouble reproducing this The output either never renders anything (but there is no network error) or renders as an image: ! ! Any other steps?\nNot sure which pre-release to use anymore, as the pre-release has changed since Please use the vsixc from this build (check the artifacts for the vsix) here is the Install Python Add the following setting into vscode (reload VSCode) Create a python env and install the following dependencies You can use the command to create a directory with Pytohn in a particular workspace folder (optionally you can use Python extension to do this for you) Run the following code in a notebook pointing to the above venv (i.e."}
{"_id":"doc-en-vscode-ed2bf0f7f4674eeceb1bcd45f7e9072be5b1870eb9ddb997ac7917655b80f0bb","title":"","text":"select the above venv as a kernel) You might get prompted to enable CDN download, hit cancel for that The widget will not load, network tab in vscode will display a 401 error !\nI'm still unable to reproduce this issue Are you running the jupyter out of sources by chance or have you patched VS Code/jupyter in some other way? The path to the resource we a trying to load looks weird: . This looks like an extension development path In normal installs, we should load resources from a path that looks more like: If you are able, you can also try and sharing the result of that function compared to the path of the js file we try loading in the webview\nThis issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!\ninformation was provided\nlets you specific an additional set of localResourceRoots that should be allowed when loading the preload. Can you please try adding these for the python static preload contribution? Let me know if fixes the problem!\nThanks , seems to work,\nChanges were made upstream in VS Code, marking as verified."}
{"_id":"doc-en-vscode-8f0e780fee2385eea1e9b2acbff7d390b1514cf6174a26a6ebc690a312dcd01c","title":"","text":"<!-- Do you have a question? Please ask it on --VSCode Version: 1.12.1 OS Version: OS X EI Capitan 10.11.3 Steps to Reproduce: some project from GitHub. a file A.cs which has no fresh changes at all. on the editor of A.cs, and notice the button of on the top right corner above the editor doesn't display as disbled! Clicking it has no effect of course, but it should display as disable in this case just like what in the old versions.\nCan't fix without , closing for now.\nsince it connot be fixed without , should this be kept open and linked to then?\nSure.\nTo keep the number of issues in our inbox on a manageable level, we're closing issues that have been on the backlog for a long time but haven't gained traction: We look at the number of votes the issue has received and the number of duplicates issues filed. Thanks for your understanding. Happy coding!\nHoping to re-open this because I got this as a feedback item from a few CS educators. They notice their students clicking it accidentally and being confused when there is no apparent action.\nI think this has regressed, I now miss this button when a file is staged.\nFixed regression with\nThere is another regression (), so I will be reverting this fix for this, and will refactor it."}
{"_id":"doc-en-vscode-363bb9dc562a8b9edc39dab5dd22b2447795e7eb0e7462befb19b7fd31336ea5","title":"","text":"takes much longer to render with file nesting enabled. Impact is lessened by disabling file nest auto-expansions. is not significantly slower to render with nesting, though I have not collected proper numbers yet.\nclosedWith\ntakes a comparable amount of time to render with file nesting enabled, though there is a perceptible delay for both. However, I do also notice that the window becomes intermittently unresponsive after expanding , e.g. when scrolling in the explorer. Is this known?\nYeah, same thing happens with nesting disabled. There's an open issue somewhere for ways to reduce that (like streaming the dir contents)."}
{"_id":"doc-en-vscode-fe96929cc65a42ac88815fa1cdd48825567d9e886fd218aba6643dbede6d9540","title":"","text":"In Markdown preview with light theme, numbers in code blocks are not clearly distinguishable because of their color. It will be good if a different color can be switched in light theme mode ! It seems that in , the following part may add a switch. Thank you!\n(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.474 --- <!-- score: 0.457 --- <!-- score: 0.456 --- <!-- score: 0.451 --<!-- potentialduplicatescomment --\nPlease share the text of the code along with screenshots\nActually, code itself does't matter this issue. It influences on many kinds of code with numbers.\nHey, I am a new contributor here. I want to give a try on this issue."}
{"_id":"doc-en-vscode-b9a4facb6b9e507bbf71d276826ad983db7a2e240bb94994931cad2f296584d6","title":"","text":"I did this on accident, but it took a little effort to figure out how I did it. Drag file from Finder onto Explorer Get scrollbar in Explorer to be visible, like by dragging near the top/bottom of the Explorer The entire explorer becomes highlighted when you hold the file over the scrollbar Drop file onto the scrollbar The entire explorer stays highlighted. It stays highlighted through interacting with the explorer and even switching to another viewlet. Only can be reversed by dragging another file onto the explorer. !\nActually a much easier way to repro is to two-finger scroll while dragging the file to get the scrollbar to appear.\ni'm able to reproduce it. will try to fix it\ncouldn't find where to start. help is appreciated\nI gave it a go in this PR:"}
{"_id":"doc-en-vscode-abb322c7900ce776ede6d85da1889cd687a132f6c20934e8949776ca332f3f57","title":"","text":"<!-- 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. After updating to VS Code 1.92, I noticed several scroll-related issues with the integrated terminal: exiting a full screen CLI app ( or ), sometimes scroll up or down doesn't work anymore until I press cmd+c - at which point I am teleported back to the start of the cli log. See the below video: start scroll works (though way too sensitive - see issue 2) press scroll up down no longer works press as soon as I try to scroll again, I am teleported to the top of the cli log output (though, at least scroll works after that)Note, while the above triggers the issue, sometimes the issue also occurs even without that (at one point I just run and this bug was triggered) full-screen CLI apps (, , ), the scroll sensitivity is way higher than when scrolling in non-full-screen apps. This scroll sensitivity is uncomfortably high, way higher than it was before, and remains high even if I set to a very low value like 0.1. scrolling through full-screen CLI app ( or ), sometimes the terminal will not let me scroll up. If I try to scroll up, I am \"teleported\" back to previous position. As soon as I scroll down, I can't scroll back up to the previous text. <!-- 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. --Relevant information: VS Code Version: 1.92 OS Version: macOS 14.5 Issues are reproducible in ZSH."}
{"_id":"doc-en-vscode-1b9cb99fcde8ee10e56fb8e2ac2b12cefcd7851bafb1e60907b25a8e304bd41e","title":"","text":"I was also able to trigger issue 1 in BASH In ZSH, I am using oh-my-zsh and powerlevel19k, BUT I was able to reproduce the issues even after I temporary disabled oh-my-zsh and powerlevel19k in my Issues are reproducible even if I start VS Code with empty user dir and empty extensions dir. A few relevant settings: is off. Enabling it does not make things better N/A as I am not holding the key - I am just scrolling using the touchpad is off. Enabling it did not make things better I am sorry if some of the above reproduction steps a bit vague - some of these don't happen each time so it's hard to see what triggered it. But these all started happening as soon as VS Code got updated to 1.92. I will keep updating this issue if I have more details. <details<summarySystem info</summaryGeneral: System info: System Information | -- | -- CPUs | Apple M1 Pro (10 x 2400) GPU Status | 2dcanvas: enabled canvasooprasterization: enabledon directrenderingdisplaycompositor: disabledoffok gpucompositing: enabled multiplerasterthreads: enabledon opengl: enabledon rasterization: enabled rawdraw: disabledoffok skiagraphite: disabledoff videodecode: enabled videoencode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off Load (avg) | 2, 2, 3 Memory (System) | 32.00GB (6.06GB free) Process Argv | /Users/mak13180/site/esri/arcgis-web-components --crash-reporter-id -0746-4857-a17b- Screen Reader | no VM | 0% Enabled extensions (BUT, issues are reproducible with all extensions disabled): Extension Version -- -- vite 0.2.5 shell-syntax 1.0.5 vscode-tailwindcss 0.12.5 vscode-eslint 3.0.10 apc-extension 0.4.1 gitlens 15.2.3 vscode-html-css 2.0.10 prettier-vscode 10.4.0 lintlens 7.5.0 copilot 1.219.0 copilot-chat 0.18.1 vscode-github-actions 0.26."}
{"_id":"doc-en-vscode-8da6607b72752714006365f59f609de0ad42630398e136b4753126c237c89529","title":"","text":"3 vscode-pull-request-github 0.92.0 gc-excelviewer 4.2.59 todo-tree 0.0.226 search-node-modules 1.3.0 nodejs-repl 0.5.15 rainbow-csv 3.12.0 remote-ssh 0.112.0 remote-ssh-edit 0.86.0 remote-explorer 0.4.3 vscode-css-peek 4.4.1 vscode-yaml 1.15.0 code-spell-checker 3.0.1 vscode-stylelint 1.4.0 vscode-mdx 1.8.9 vscodeintellicode 1.3.1 explorer 1.0.6 vim 1.27.3 pretty-ts-errors 0.6.0 markdown-all-in-one 3.6.2 A/B experiment info: My (BUT, issues are also reproducible when VS Code is started with empty user dir): The log when VS Code is started as : </details\nUpstream PR fixing it"}
{"_id":"doc-en-vscode-a5a86fe651c2258bd8f453d96a9fa9989ddc9f5c1199f0b933e263d68a4dc65b","title":"","text":"<!-- 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: Windows 11 OS Version: 1.75.1 Steps to Reproduce: Using the following settings: ! ! a typescript file within a method/function following gets output (might have to navigate through some of the suggestions) even though snippets are off: !\nThanks for the patience. I cannot reproduce, please share more of your settings that might influence this. Also share data in a copy-paste friendly way (text over images)\nHere are the settings that I am using to reproduce (all extensions disabled ): Once typing and going to the 3rd suggestion, I get this as a suggestion: !\nThanks for clarifying, looks like we aren't passing the filter here:\nI can't figure out how to get that ghost text to show up for suggestions to verify this. I've never seen that ghost text for anything but copilot completions Do I need a suggestion provider extension?\nYou are right. I made a refactoring after this fix and that broke this feature Thanks for the diligence on this one!\nTo verify, use the steps from Make sure no snippets completions are ghost-texted with and that they are when the setting is set accordingly\nI still cannot get snippet completions to show up\nYou need to say what you are trying because I do see them working just fine <img width=\"922\" alt=\"Screenshot 2024-01-26 at 18 14 32\" src=\"\"\nThis works correctly for me now, no snippets with , and they do show up without it.\nBang on."}
{"_id":"doc-en-vscode-5c535562f10cb90e9a2414f8db6161c16460c880373a2068dbf97c36c1af775b","title":"","text":"The whole point is that the -setting is honored also for ghost suggestions\n: <img width=\"1792\" alt=\"Screenshot 2024-01-26 at 9 19 47 AM\" src=\"\"\nthis is about ghost text, please see and the comment linked from there\nthere was a syntax error in my file, so the settings did not get applied. Now it works"}
{"_id":"doc-en-vscode-d5dbf9499a4c5d5da9d85ef8b1ece5ce0ecf4880c3cda588beb8f6eb353e995b","title":"","text":"Type: <bBug</ban image file from the VS Code explorer into a md file Bug No markdown image inserted, just the file name VS Code version: Code - Insiders 1.88.0-insider (Universal) (, 2024-03-29T22:24:49.191Z) OS version: Darwin arm64 23.4.0 Modes: <details<summarySystem Info</summary </details<!-- generated by issue reporter --\nClosing for verification."}
{"_id":"doc-en-vscode-7610f364ff485ba6ab7bd2c1186e47e60e59fec48d1135066cd458c0a1022943","title":"","text":"Type something so that the suggest widget appears Once it appeared and an item is selected, press on the left arrow key The text in the suggest widget disappears There remains a black box with nothing inside where the widget was positioned\nhm... doesn't reproduce for me. can you check devtools console for errors?\nnvm - I can reproduce running out of sources\nregression from\nHi sorry, I just saw your messages. I think I didn't receive the notifications because the tab with this issue was open in chrome, and notifications were not sent. Anyway thanks for looking into this."}
{"_id":"doc-en-vscode-d802c2140725b2dd82423579ec8bd6d0dd09bcc69e2a9855fc915fa8c08f6c80","title":"","text":"I think the border should be thicker and the color should have more contrast. <img width=\"881\" alt=\"image\" src=\"https://user-\"\nI think the thicker border is a little too heavy but agree that the light themes in particular suffer from a contrast issue. Do you think it's as much of a problem on the dark themes?\nIt works much better on the dark themes (maybe also because my code-oss uses dark theme)\nOk, I'll propose some updates this week\nBefore Light: ! Before Dark: ! After Light: ! After Dark: !"}
{"_id":"doc-en-vscode-056bfbfab2d54b48821d693983efce1b749aa724dce6114a6946a2831153ec8e","title":"","text":"When tabs are enabled, the close button is slightly larger and unbalances the tab. This button should be different than when tabs are disabled and the close button is moved to the editor toolbar. !"}
{"_id":"doc-en-vscode-b563a2c65a64eae7be033784b3e58edea87872d40da5cb07f9fd9a9b824b0320","title":"","text":"\"Add\" text in these screenshots. JSX ! HTML !\nThat's just how it it. All depends on what scopes the differents grammars (html: no scope), jsx: ) use and the decisions of the themes on what to colors. The workround is to use a theme that doesn't color , e.g. the default light theme.\nfixed by , thanks"}
{"_id":"doc-en-vscode-7f1209f9618d72eb9e6931e3d535ebf3903fe4af3ec5cd928a06f0d39c29af9a","title":"","text":"<!-- Do Not Delete This! bugreporttemplate --Version: 1.66.0 (system setup) Commit: Date: 2022-03-30T05:50:14.623Z 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. New \"striped\" gutter decorations were in . These decorations do not respect the existing SCM: Diff Decorations Gutter Width setting: Changing the above setting has no effect on the new decorations.\nI think this was an oversight and have a PR that can help address this. Thanks!"}
{"_id":"doc-en-vscode-85e7d715168e0af7a18e7385cfaa0f6e9c95ccb66e7121e9d8a1617d6b496c5d","title":"","text":"Type: <bBug</bAfter updating to v1.76.0 command \"Show Next Change\" () no longer works. My file has uncommited changes that are highlighted in a bar to the left of the file, and when I press the shortcut or trigger the command manually from Command Palette I expect my cursor to move to a line with a change and a panel with a diff to appear (as it used to before the update). But nothing happens. ! I tried testing this with all extensions disabled and in VSCode Insiders v1.76.0, same there. VS Code version: Code 1.76.0 (, 2023-03-01T10:22:44.506Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (18)</summaryExtensionVersion ------ overtype0.2.0 pascal-language-basics0.1.10 vscode-django1.10.0 vscode-eslint2.4.0 xml2.5.1 gitlens13.3.1 hoogle-vscode0.0.7 language-haskell3.6.0 isort2022.8.0 python2023.4.0 vscode-pylance2023.3.10 jupyter2023.2. vscode-jupyter-cell-tags0.1.6 vscode-jupyter-slideshow0.1.5 remote-wsl0.76.1 block-travel0.0.2 selectline-statusbar0.0.2 haskero1.3.1 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nSame for me, neither the nor work since upgrading. & seem unaffected, but I want to see the context of changes quickly without having to click the mouse or change switch editors.\nI'm having this problem too.\nSomething seems to be pretty busted in 1.76.0. The Show Next Change (Alt-F3) and Show Previous Change (Shift-Alt-F3) commands do nothing. But worse, the Git: Revert Selected Ranges (Ctrl-K, Ctrl-R) command completely messes up my file.\nI believe that this should be fixed in the latest Stable release,, so I will optimistically close the issue."}
{"_id":"doc-en-vscode-85d6da2915880b0a6c65fbc42d7e858f7b4d342b0de7de05895a689ddb0cee79","title":"","text":"Please reopen it in case you are still able to reproduce the problem with the latest Stable release. Thanks!\nUnfortunately cannot confirm, the shortcut and the command are still broken both in 1.76.2 and in 1.77.0-insider. I cannot reopen the issue but I hope someone else will.\ncould you please take a look and see if this could also be related to your changes? Thank you!\nGlad to see this fixed; for me however the diff peek that opens seems to always show several lines above the current change. Are there settings that might affect this?\nI'm not aware of any settings that would affect this. Do you see this behavior 100% of the time? If not, do you know if there are any specific steps that cause it to happen?\nJust found out that it's probably the sticky scroll that's causing this. I disabled all my extensions and still managed to reproduce this. I didn't pay attention at first, but now that I think of it, most of the times it's happened, I've had a bunch of lines showing in the sticky scroll header. I have this in my settings: Tried disabling it (or just lowering the number of lines shown) and now the diff editor shows the difference correctly (albeit a bit towards the bottom). So maybe the diff editor should either account for the number of sticky scroll lines, or not show the sticky header at all.\nthanks for following up with your findings. I agree that we shouldn't use stick scroll in the quick diff: there just isn't enough vertical space for it to make sense. I'll disable it."}
{"_id":"doc-en-vscode-13f9dafbfe8b70e32df84d807bd96463cf5f663f68679eef576de86e8b1156bc","title":"","text":"Testing Have the following code in an notebook cell. Run the code Scroll the output. Notice as your scroll reaches the top you can continue scrolling and it will scroll the whole notebook file. This is unexpected and I think no other widget in VS Code behaves this way. I suggest instead the following strategy when scrolling: If a mouse is in the Cell then scrolling it will only scroll that cell. You can not scroll the large notebook while the mouse is in the cell. Same way you can not scroll the Cell with the mouse unless the mouse is in the cell IMHO this is what makes the current experience feel weird.\nWe don't often have nested scrollable elements in VS Code workbench and also this is how browsers handle nested scrolling. Current behavior feels right to me. I can see the value of scrolling only when the focus is inside/on the output, there is a catch with that though, users need to move cursor to outside of the cell output to scroll the notebook, and the hit area for that is very narrow most of the time.\nThanks for providing more info. But what other UI element scrolls like the notebook does right now - so that you can scroll the element until it hits the end, and then if you continue scrolling that the outer element starts scrolling? This really felt unnatural to me, but I might have missed this pattern in other parts of the workbench. Or what do other Notebooks products do in this case?\nthe peek view actually behaves this way. That's the only other nested scrollable element that I know of.\nThanks! If I am the only user that it complaining feel free to close this one as designed :)\nI tried using notebook in VSCode again last week, and came to GitHub to open this exact issue. I feel this scroll is extremely unintuitive. Here's an example. A cell is outputting more lines than , so we're currently viewing it's last line. I want to scroll to top. I speed scroll up, but this reaches the top and keeps scrolling the notebook, so now I'm all the way up. I have to scroll back down to my cell. If I go fast, I might miss it. If I go slowly, some other cell's output might catch my scroll and scroll that to bottom, before the notebook scrolls again. Same happens to my cell."}
{"_id":"doc-en-vscode-30b9f389b881aa2eacea36616e4b0742693414fcf01a377928d8964ea65c13a4","title":"","text":"I need to be frustratingly precise to scroll this output to the top. Here's a recording to illustrate (I hope you can see it, recorded on MacOS, encoded as AV1; can add YT link if not viewable here): It took me 15 seconds to manage to get that top. And I knew exactly what I wanted to achieve, for the sake of the video. Now here's the same experience in native Jupyter Notebook (exact same notebook and cell). First, I can easily toggle the output scrolling. If untoggled, the output scrolls natively with the notebook, and since it expands downwards, without the notebook jumping, I can immediately see the top, which is right next to the cell. Then I toggle the scrolling again, to illustrate the behaviour compared to VSCode. I initiate scrolling inside the output area, and so only that area is scrolled. No matter the speed, or direction, I can easily reach the top or bottom as many times as I need, without losing context of my notebook. If I do want to scroll the notebook, I need to scroll outside the output area. This is easy because the cell does not take the whole width. This is in relation to what said above: Yes, but the cell does not need to take the complete visible width. In native notebook, cell's width is limited, and there's still plenty of space for code. But even if the cell does take the entire width, the user can initiate the scrolling outside the output area, i.e. over a cell. In this case, it scrolls the notebook, and never the outputs. The outputs do not steal the scrolling from the notebook, like it happens in VSCode. So: scroll initiated on cell or outside the cells area -scrolls notebook only, never output scroll initated in scrollable output area -scrolls only that output area, never the notebook\nshould we reopen this? What do you think?\nsure, that's a reasonable request. It would be inconsistent with how the peek view scroll works, but the possibility for many scrollable regions makes these cases more noticeable in notebooks. - one thing that might help - you can toggle output scrollability per output in vscode as well with , by default\nI have the same issue."}
{"_id":"doc-en-vscode-97ee551184b0009533f8511c3b7f85df47d20e4186ae420a9bc798f6a9a1e41d","title":"","text":"The usability of the scrollable element suffers greatly due to the current crazy behavior - when the scrolling inertia reaches the end of the scrollable output and scrolls the whole notebook! If different users want different behavior, this can be an option in the settings, e.g.: current behavior behavior like in the native Jupyter Notebook (in the video above), i.e. the notebook never scrolls if the pointer is inside the scrollable element there may be a 3rd option: the scroll that reaches the end of scrollable area doesn't scroll the notebook, but the subsequent scrolls in the same direction (even if the mouse pointer is inside the scrollable area) - scroll the notebook\nfor verification, please check with a mouse wheel and scrolling with a trackpad, since they behave quite differently. Hitting the boundary of the inner scrollable region will prevent further scrolling for that same scroll action. After a short pause you should then be able to scroll the outer region since the inner region can't be scrolled any further. (similar behavior to a browser)\nVerified on trackpad. Still have to verify with a mouse wheel.\nverified on mouse! there was a pause/delay, but wonder if there should be a larger delay - I find that sometimes I spam scroll and it moved up a little quicker than I anticipated. if it matches browser tho, should be all good ~\nhello , thank you a lot for the work on this issue! I hate to say this, but I think it's not solved: It looks like only a certain \"scroll length\" is ignored, and the rest of the scroll inertia is still applied. Here I do: one fast scroll (as you see, the notebook moves) then I scroll back down then one fast (a bit slower) scroll (the notebook moves) Only if the scroll isn't fast enough the \"scroll length\" will be small enough to be completely ignored. <br /Here I do: one long scroll - all the way until the end of the video: <br /The behavior in the native jupyter notebook is certainly different. Here I do: one fast scroll - different than in VSCode (the notebook doesn't move) one long scroll- different than in VSCode (the notebook doesn't move) one after-scroll (the notebook moves as expected) Could this issue please be re-opened?\nwhich version of vscode was this on?"}
{"_id":"doc-en-vscode-fae0a4a326f6536862fc67658bc4fec550702715c0026f64bddc74ff3635d53a","title":"","text":"Version: 1.88.0 (Universal) Commit: Date: 2024-04-03T13:28:18.899Z (1 day ago) Electron: 28.2.8 ElectronBuildId: Chromium: 120.0.6099.291 18.18.2 V8: 12.0.267.19-electron.0 OS: Darwin arm64 23.3.0\nok, yeah. looks like I broke the behavior with a related bugfix\nVersion: 1.89.0 - still isn't completely fixed: If I scroll hard enough, the notebook scrolls."}
{"_id":"doc-en-vscode-79b544cb848a6cec792c5990ac9bb7505c2cb4374da5de40fd64827528ec4296","title":"","text":"Testing edit keybindings leave out args or have an empty array of commands trigger the command, nothing happens. This is expected but I wonder if an information/guiding message should be shown that the keybinding needs some commands to be useful?"}
{"_id":"doc-en-vscode-e2b89f707fa1357d45cc8b224b7630a028ae3dd4f8f9ce200b1b14708061c44e","title":"","text":"Pick up final TS 2.1.5 for the bundled version of TypeScript. Insiders version of TS 2.1.5 is already in VSCode 1.9 insiders"}
{"_id":"doc-en-vscode-fc59ec853d93cf02ba524034cb5cf76d3b5578abbe9cf9d5c75a04d9b0205179","title":"","text":"Testing I wonder how well it scales to show multiple tag icons, why not find a new icon that resembles multiple tags: !\nI like that. Adding as that would require a new Codicon...\n!\nOr just show one tag in the row, but show all of them on hover like you do now.\nHow about showing one badge pert type (ex: branch, remote branch, tag) and a number indicating how many they are. That way there is no need create new icons that would cause further confusion.\nI am actually not entirely sure what value there is to distinguish 1 tag from N tags? I would just show 1 icon if there is any tag.\nSeems reasonable. Let's start with that and see how things go."}
{"_id":"doc-en-vscode-43a804368c63b8fd7dd77611a9e65512038f62565145ffbf59586b3f0794c71a","title":"","text":"Type: <bBug</bIn the \"Source Control Repositories\" view, if you have several repos selected, and then right click on one of them and choose \"Open in Integrated Terminal\", it will open the terminal in the directory for the first selected repo regardless of which repo you right clicked on. However if you right click on a repo under \"Source Control\" then it will open the terminal correctly. VS Code version: Code 1.90.2 (, 2024-06-18T22:33:48.698Z) OS version: Linux x64 6.6.15-2rodete2-amd64 Modes: Remote OS version: Linux x64 6.6.15-2rodete2-amd64 <details<summarySystem Info</summary </details<details<summaryExtensions (22)</summaryExtensionVersion ------ jupyter-keymap1.1.2 remote-containers0.375.1 remote-ssh0.112.0 remote-ssh-edit0.86.0 vscode-remote-extensionpack0.25.0 remote-explorer0.4.3 remote-server1.5.2 rewrap1.16.3 githistory0.6.20 gitlens15.1.0 go0.41.4 debugpy2024.6.0 isort2023.10.1 pylint2023.10.1 python2024.10.0 jupyter2024.5.0 jupyter-keymap1.1.2 jupyter-renderers1.0.18 vscode-jupyter-cell-tags0.1.9 vscode-jupyter-slideshow0.1.6 preview-vscode2.3.7 code-spell-checker3.0.1 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nThanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.91.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!\nIs that option being contributed by an extension? Please use the command to investigate.\nThe menu option is there even with no extensions loaded by \"Start Extension Bisect\"\n<!-- UNABLETOLOCATECOMMITMESSAGE repo --Issue marked as unreleased but unable to locate closing commit in repo history."}
{"_id":"doc-en-vscode-a49af69135f6400c12907dcd69d069337bf1e2b78819be574cbc94cdf477aaaf","title":"","text":"If this was closed in a separate repo you can add the label directly, or comment .\n<!-- UNABLETOLOCATECOMMITMESSAGE --Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting , or directly add the label if you know this has already been releaased"}
{"_id":"doc-en-vscode-98ce646222a08b728c18552067667e2d1960a1362e1367e6159161fa7558c50f","title":"","text":"Hei! Found issue with folder delete operation. The point is, when you delete folder (first time), no matter how, via mouse or keyboard combination, then select another folder and try to delete it, you will get popup message saying \"Cannot read property 'isDirectory' of undefined\" Only when you select another folder again (second time), delete operation will be successful. Tried several times with same results. And as i remember, this bug i found some time ago, so it is not introduced exactly in last insiders build. Visual Code Insiders 1.41.0 from 2019-12-02, commit: macOS 10.15.1\nthanks for filling this great issue. You should have the fix tommorrow in vscode insiders\nthe problem was that it was happening that the tree would sometimes set the trait on one element two times. In this particular case Selection would be set on the element A and A. So if I say tree.getSelection I would get the same item twice. Instead of the array with one item. I decided to fix this with a workaround on the trait level. Repro steps: set compact tree to true. Go up and down with the focus always ending up with the focus on the one select item. Put a conditional breakpoint tree will try to set the double selection trait\nThis seems to be coming from Where the selection would already contain the folder, but as oldSelection/oldFocus also has the id, it will push the same object to the selection again. You could also fix it there by doing some sort of duplicate filtering or selection.indexOf to prevent duplciates being I could reproduce it consistently by: Putting a breakpoint there Creating a new folder Focusing on that folder Result: The function ends up setting selection to contain the same object twice.\ngreat pointer. I think you are right, give me a sec and I will push a better fix. Thanks a lot!\nI was planning to submit something along the lines of But I'm not sure if this is considered good code, it might be better to create a set of Ids (like oldSelection) does, but as selection is of type T, I could not access the id parameter.\nIf you would like to create a PR you are more than welcome to! It would be great if you could do it today since we are wrapping up the milestone and we need this fix asap."}
{"_id":"doc-en-vscode-ae5e6bb6e2fa84c94044cb271e993da2b0cdc6e7f664cc006daf14eef5ae1efa","title":"","text":"Just make sure to remove my wokraound introduced with Thanks! And make sure to ping me on the PR"}
{"_id":"doc-en-vscode-49905f3647df31c61019503115d01b22d80bd4d12a1d225ccc24af41df31ed83","title":"","text":"<!-- 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: stable and from sources Steps to Reproduce: server vscode in safari simple browser :bug: Observe icons don't load (icons load if disable Cross Origin Restrictions in develop menu is checked)\nHow are you running the server? I see the icons loading in but not on localhost using : ! This seems expected since Safari seems more strict about loading content from localhost in this case\nTry codespaces, it repros there too. (For running the server I use ) It works on serverless (i.e. and ) because they are served in a different way I think\nI'd also like to see it fixed. It's still reproducible on latest Safari version. <img width=\"290\" alt=\"image\" src=\"https://user-\"\nThis definitely seems like a webkit bug but I can't put together a minimal repo. The issue is the the codicon font face doesn't go through the service worker during loading despite it's parent css file being loaded by it: ! I also tried debugging the production code in codespaces but Safari's dev tools are pretty much unusable with our minified service worker Instead, I'm going to push a change that inlines the font in the css file to hopefully work around this issue\nLooks to be working in latest insiders !\n<!-- 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."}
{"_id":"doc-en-vscode-9c9fa2173a0efd70fa667f74eee1881b9ef4a6b3db3946a70f20eddcdf0041d3","title":"","text":"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!\n/verified"}
{"_id":"doc-en-vscode-bd5bdd36199fa4db971f3e2ad936e2f5a9844c881f3458c63e53d17f19d36e61","title":"","text":"<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --When developing an extension, I sometimes mess around with versions, e.g. install an (unpublished) extension with different content using the same version, or going back a version. It can happen then that I can install the extension (via file) successfully, the extension appears, I get the notification to reload VSCode which I accept, and the extension is gone after the reload. It does not load, and it does not appear in the list of installed extensions. There is no warning nor any trace in the extension host output pane. I recently figured out that this appears to be caused by an auto-generated entry in the file, listing the installed version of my extension. There might be a bug here, since it also lists the highest version ever installed. However, this feature request is about the lack of notifications why the extension is not loaded. I would appreciate if you could tell the user, e.g. via a warning during install and maybe during every load, that an extension has been blocked because it's obsolete. Furthermore I suggest listing the extension as installed in the extension pane, as deactivated/obsolete with a warning attached to it.\nCan you please provide exact steps to reproduce this behaviour?\nI did not mean this as a bug report, but rather as a request to add additional messages telling the user what's going on. However, I've tried to reproduce it and it seems you can get this issue if you do: a for some extension E in version 0.0.1 E in version 0.0.1 from vsix (I'm doing this on a remote machine using the Remote SSH extension). . a for E in version 0.0.2 E in version 0.0.2 that now contains an entry making E in version 0.0.1 obsolete . E in version 0.0.1 . that now contains both an entry making E in version 0.0.1 obsolete as well as version 0.0.2 obsolete. that the extension is not loaded. At this point, you can also install E in version 0.0.2 and it still won't load.\nI am not seeing this behaviour."}
{"_id":"doc-en-vscode-1406bab9dd37b8e5600661eca76cf7753ca4e3b4cc756dd192f1c28f8b2b9e1d","title":"","text":"When I install 0.0.1, .obsolete file now contains 0.0.2 version only.\nSorry for taking so long to answer. I've now taken a fresh VM (Ubuntu 22.04) and a new extension (, just modified the so it would package) and could reproduce it. No \"Remote - SSH\" involved either. The steps: Generate two versions of an extension, 0.0.1 and 0.0.2 Install VS Code. At this point, does not exist yet. Install 0.0.1 and reload. Install 0.0.2 and reload. This creates the file with a single entry . Install 0.0.1 and reload. The file now contains . The extension is not loaded and does not appear in the list of installed extensions. Even if you \"only\" end up with an entry for version 0.0.2, this would still probably cause an issue if you try to re-install 0.0.2 since there are no diagnostics emitted - neither during installation nor during startup.\nOk there is a bug at the last step - Installing 0.0.1 shall not add 0.0.1 to the file. This bug happens only when the has no set. Can you please set the property in the and retry?\nTo verify: Formulate an extension without property in Generate a VSIX 0.0.1 with version Generate a VSIX 0.0.2 with version Install VSIX 0.0.1 and make sure 0.0.1 version is installed Install VSIX 0.0.2 and make sure 0.0.2 version is installed Again Install VSIX 0.0.1 and make sure 0.0.1 version is installed"}
{"_id":"doc-en-vscode-48d72571ea95d3a717eb7725ba11763ee2d3be6d5540f2c43a274daa52fb6fc8","title":"","text":"the Settings editor. Notice the \"Editor: Tab Size\" setting has a link. over the link. :bug: There's no underline text decoration, and the cursor doesn't become a pointer."}
{"_id":"doc-en-vscode-9442d675044fc4640365dd3aa40f98febb6765f417c5accc993c4fc2edf9e9a4","title":"","text":"Type: <bBug</bWhen I commit from the git extension, I frequently get an error message that \"Git: Extention '' CANNOT use API proposal: telemetry\". When I look at \"Running Extensions\", git reports 32 uncaught errors. I do not know if the two error counts are related. This only recently started happening (last couple of weeks). VS Code version: Code 1.85.1 (, 2023-12-13T09:49:37.021Z) OS version: WindowsNT x64 10.0. Modes: Remote OS version: Linux x64 5.15.90.1-microsoft-standard-WSL2 <details<summarySystem Info</summary </details<details<summaryExtensions (13)</summaryExtensionVersion ------ remote-containers0.327.0 remote-wsl0.81.8 rewrap1.16.3 markdown-table-prettify3.6.0 vscode-markdownlint0.53.0 git-graph1.30.0 python2023.22.1 vscode-pylance2023.12.1 cmake-tools1.16.32 cpptools1.18.5 rewrap1.16.3 cmake0.0.17 markdown-all-in-one3.6.1 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\n/gifPlease\nThanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, files are preferred as they are displayed inline on GitHub. You may find helpful as a browser-based gif recording tool. If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording ( in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue. Happy coding!\nThis issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!\nHere's an example of the ruling.\nThis bug is still active. I can't get rid of the problem."}
{"_id":"doc-en-vscode-5204d2e738c45b243637e501ce02267b5a14a0adcf22bd8ded8a3629eac76a2e","title":"","text":"My version of VSCode is: Versión: 1.85.2 (user setup) Confirmar: Fecha: 2024-01-18T06:40:10.514Z Electron: 25.9.7 ElectronBuildId: Chromium: 114.0.5735.289 18.15.0 V8: 11.4.183.29-electron.0 SO: Windows_NT x64 10.0.\nare you able to reproduce this issue every time you try to commit? When the error occurs, could you open the developer console using the \"Developer: Toggle Developer Tools\" command and share all the errors/warnings in there? Are you able to reproduce this issue with all the extensions disabled? Thanks!\nYes, every time I commit I have this problem. ! ! I only have 3 extensions, I disable them and the same problem occurs. ! Sorry for my English. I don't know if you mean this. But it's what I see when I open Toogle developer tools.\nstill getting it too. I have dozens of git repositories across multiple versions of git (development containers with different Linux versions, Windows, etc.) Happens frequently, but not always, but does seem to happen consistently on some repositories and not others.\nthank you! After you reproduce the problem, could you also please send me the contents of ? Also, are you able to reproduce this issue with all extensions disabled? The easiest way to try this is to use the \"Help: Troubleshoot Issue...\" command from the command palette.\nIt seems that way. Thank you\nOk. First i delete output of git. ! After. I disable all extensions. ! After. I can one time more to make commit. ! New commit ! After commit ! Git output complet: 2024-02-01 10:24:20.195 [info] No remotes found in the git config file."}
{"_id":"doc-en-vscode-817f379b28a77f68082ce9a31faea5ba68828e5ae0659e52c6dfbb7bad27d1ad","title":"","text":"2024-02-01 10:24:20.244 [info] git config --get commit.template [54ms] 2024-02-01 10:24:20.244 [info] git for-each-ref --format %(refname) %(objectname) %(objectname) refs/tags [49ms] 2024-02-01 10:24:20.286 [info] git status -z -uall [39ms] 2024-02-01 10:26:19.989 [info] git add -A -- . [56ms] 2024-02-01 10:26:20.264 [info] git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file - [269ms] 2024-02-01 10:26:20.308 [info] git config --get commit.template [39ms] 2024-02-01 10:26:20.317 [info] No remotes found in the git config file. 2024-02-01 10:26:20.364 [info] git config --get commit.template [49ms] 2024-02-01 10:26:20.372 [info] git for-each-ref --format %(refname) %(objectname) %(objectname) refs/tags [49ms] 2024-02-01 10:26:20.413 [info] git status -z -uall [38ms] 2024-02-01 10:26:20.480 [info] No remotes found in the git config file."}
{"_id":"doc-en-vscode-07a42db85bce26ba1db94c190c7cce204463a12bc3fa50fe7ff9eb159871ffb0","title":"","text":"2024-02-01 10:26:20.528 [info] git config --get commit.template [51ms] 2024-02-01 10:26:20.533 [info] git for-each-ref --format %(refname) %(objectname) %(*objectname) refs/tags [54ms] 2024-02-01 10:26:20.579 [info] git status -z -uall [40ms] 2024-02-01 10:26:41.809 [info] git ls-files --stage -- C:UserssriccOneDrive - ICCADocumentosAngularSergieCodecargaPaginasAppsrcappcontacto [49ms] 2024-02-01 10:26:41.859 [info] git cat-file -s [43ms] 2024-02-01 10:26:41.908 [info] git show --textconv [42ms] I hope it's everything you've asked for.\nSOLVED For me, I found out it was because I was on a detached head on Git. For some reason, reattaching to master solved it.\nThank you! I have to admit that it's not clear to me what is happening here. Let me chat with my colleagues and see if I can come up with an action plan.\n+1 for gilad905's suggestion. I was able to easily repro the problem: new repo from command line. first commit. out main and commit from git source-control panel in vscode, works. out the new head (the second commit), detached. another change and try to commit it in vs code Expected: It works correctly Actual: The commit is created in the repository, but the \"telemetry\" error message shown above appears.\nThanks Fix for this will be in Monday's VS Code Insiders release. Apologies for the inconvenience!\nthanks\nI am not, and have not been using repos. Sorry this is not the only problem occuring.\nplease share your repro steps in case you are able to reproduce with the latest VS Code Insiders release. Thanks!"}
{"_id":"doc-en-vscode-db3b4f142917ba6d9472d190411bdecf10fa62b36cabe617c697c8590e6679dc","title":"","text":"Steps that should work but don't (these will be verification steps): PowerShell for macOS if you don't have it what path was to () it as your default shell: VS Code from the dock/finder a workspace with the below task the task Actual Expected Something like: This is because we fail to get the UnixShellEnvironment. You can confirm this by looking in output, you should see:\nanother great verification step is replacing the command in the task and putting something like or . This will likely fail saying it couldn't find the command ... because the environment wasn't set up properly.\nI'm still getting the actual output instead of the expected output when I repeated the verification steps on my Mac."}
{"_id":"doc-en-vscode-9d3d93b8def2dfa2b493a6d677e96875453c8925ead5ebef1ebcd50dd3f33112","title":"","text":"<img width=\"377\" alt=\"image\" src=\"\"\nVerification step- just use a variable in a multiroot workspace, and check that you have the right blue background when it's rendered in the request.\nWorks great. Slightly related - why do we just render the blue background while I am typing the request, but do not render it blue when the request is sent. This was always the behaviour and is unrelated to MR workspace. I am just curious !\nIf it was used correctly, it will have the blue background. Did you pick the file from the picker, or just type the text?\nPicked from file picker.\nOh no!\nApparently I didn't test this as thoroughly as I should have. Some files now break the markdown link. Need to rework this in main for debt week but there is an easy fix for now.\nFor verification, we should test with Files in a multiroot workspace In single folder window Files at the top level of the workspace And under a folder\nSince the PR has been merged yesterday, this issue will be closed, for verification."}
{"_id":"doc-en-vscode-8b986d3cfb264fc2df063652240ce421a43f9f208aed7b5db460ecde0f73d11d","title":"","text":"<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --I found that once the [Activity Bar Position] is set to [Top], i can't find the activity bar at the top anymore, when i click [File-New Window] to open a new window. Therefore, i suggest display the activity bar by default when opening a new window.\n<img width=\"1068\" alt=\"\" src=\"\"As shown in the picture, the new window does not display the activity bar.\nI like this idea, I will look into it."}
{"_id":"doc-en-vscode-29f5b3eaed03e2819795028752a320eb4a80ce7f8dbff278485d9ff5a905e949","title":"","text":"Testing Just a small change. Believe the casing is off in the hover hint for the button. When going to a running cell it's \"Go To..\" and in the new error command its \"Go to...\" with the rest all caps. I believe the \"to\" should be \"To.\"\nThe convention for commands is to use \"Go to....\" lowercase \"to\". !\nGot it. I was basing it off of seeing this for the other Go to cell command. So is the bug on that text instead? <img width=\"191\" alt=\"image\" src=\"https://user-\"\nI think \"Go To\", both words capitalized, is good to match the other notebook titlebar casing (for example \"Run All\"). Using simply \"Go\" in the titlebar might be ambiguous and people would confuse it with \"Run\". The hover in the image above, should be \"Go to Running Cell\"\njust checking, but would be proper fix for this to change the casing in \"Go To Running Cell\" to \"Go to Running Cell\"?"}
{"_id":"doc-en-vscode-cccc4fc3baecd8e32ac0b736347813cd2c0ecd946f09cbe3074d39600e8f552b","title":"","text":"Testing Links to overridden settings (here is shows as Modified in User) to show as links nor are they affected by the setting. !\nAs in, they don't use the typical link color? is that intentional? Agreed that they should pick up the setting, in any case.\nHere's how it would look ! !\nI don't remember whether it was on purpose in order to not make the link stand out too much. I'm alright with changing the colour of the link and keeping the underline for improved accessibility.\nAgreed. Merged the change and we can tune it from there if needed."}
{"_id":"doc-en-vscode-0fcb06887f19aa6ebdb3a58262344b18f2c9bb9ad49c5b8ff5bb21945f6b21e0","title":"","text":"<!-- 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: 1.86.2 (system setup) OS Version: Windows 11 (Windows_NT x64 10.0.) Steps to Reproduce: the built-in extension \"CSS Language Features\", which has an identifier of settings, search for \"hex color length\" See that it says \"Hex colors must consist of three or six hex numbers.\" when it should say \"Hex colors must consist of three, four, six, or eight hex numbers.\" to accommodate the alpha channel. The extension already allows for all four lengths, but the setting description is wrong."}
{"_id":"doc-en-vscode-576555387e661c21912a1bcb8535e1fff3d178d48a68ab557f68ca851e5ff772","title":"","text":"going to keep track of examples here to see if there's a pattern <img width=\"1112\" alt=\"Screenshot 2023-01-23 at 2 12 18 PM\" src=\"https://user-\"\nfar right terminal <img width=\"1120\" alt=\"Screenshot 2023-01-23 at 3 07 17 PM\" src=\"https://user-\"\nmiddle terminal !\nfar right terminal !\nfar right terminal <img width=\"1076\" alt=\"Screenshot 2023-01-24 at 1 59 40 PM\" src=\"https://user-\"\nright terminal <img width=\"1644\" alt=\"Screenshot 2023-01-24 at 2 22 27 PM\" src=\"https://user-\"\nright terminal !\nhere are the lines when there's not a quick fix result - it contains after which we don't account for here !\nSeeing this frequently: <img width=\"726\" alt=\"image\" src=\"https://user-\"\nI think we just need to include the to fix this\nor better yet, remove and just look for the link\nok I see the issue. when lines are wrapped a lot, we need to search more lines - setting the length to 10/15 fixes it even when the terminal is quite narrow\nI see it on non-wrapped lines, I'm not sure I understand what you mean with the To?\nThe to comment above was actually wrong. What's happened in the screen shot above is we abort the search early - after looking at only 5 lines. When it's actually on line 9\nthis goes wrong when we break before reaching the content IE when line count length\nI tried pushing up a new branch using pwsh in the integrated terminal on Windows, and the lightbulb did not show. !\nyou have shell integration disabled, it won't work at all there.\nalso make sure to not move issues to the next milestone, this one was marked important\nWorking much better now, but just reproduced !\nJust happened and captured the trace log (escape sequence log would be better): <img width=\"806\" alt=\"image\" src=\"https://user-\"\nI've seen this not work twice today already for create PR !\neven though the lightbulb didn't appear here, there was a match found !"}
{"_id":"doc-en-vscode-c53bdde872a354f6e5f11c9b6a864b1dda9c48f45bd8eea0a76cbf46cf632cf1","title":"","text":"the match always happens, the lightbulb doesn't show up though until I resize the terminal\nthis happens when the have not yet been resolved by the time occurs ! !\nI think we should be calling at the end of\nhave seen the create PR not show up 3 times today. resizing doesn't cause it to show up, which means our match range is wrong/ there isn't a match\nthis says unreleased, but was merged before the current version of insider's (5 hours ago) was released. create with PR still failing !\ninsider's is based on the release branch, so I was confused\n<!-- UNABLETOLOCATECOMMITMESSAGE issue --Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting , or directly add the label if you know this has already been releaased"}
{"_id":"doc-en-vscode-c3f19d5d56397b321e3db01f87c3bad946453843cc0d8298668b3daf4280015f","title":"","text":"start inline chat in the content widget author multiple lines :bug: the widget's height doesn't change\nstill kind of running into this kinda - height changes, but the prompt layout after querying is unreadable since there's only one or 2 line height worth of space also, seems like there is a weird horizontal scroll element on the bottom left of the widget?\nI see. This is because the height of the zone is limited by the overall height of the editor. It doesn't want to take more than 42% - that's something we can tweak but you might be facing a bit of a special case having a multiturn convo and accessibility viewer enabled as well.\nThe first prompt handles a long string nicely. A long string for the follow-up prompt results in content overflow. !"}
{"_id":"doc-en-vscode-e2134771812773482f08df27b3d7f8286dde5a3204c8be02000b2689caadc6c6","title":"","text":"Testing For this issue I used a notebook with one cell that contains the following code: <details<summaryfile </summarydata= {} df = pd.DataFram(data) data= {} df = pd.DataFram(data) data= {} df = pd.DataFram(data) data= {} df = pd.DataFram(data) data= {} df = pd.DataFram(data) data= {} df = pd.DataFram(data) data= {} df = pd.DataFram(data) data= {} df = pd.DataFram(data) data= {} df = pd.DataFram(data) data= {} df = pd.DataFram(data) data= {} df = pd.DataFram(data) </details- Stage this code Make a change Open the diff view in the SCM pane Open the metadata view Type into the metadata view The metadata view closes before anything can be typed Is this expected?"}
{"_id":"doc-en-vscode-2863ea5b18199b7351b1de33b471f5bcceda4e5ca2caaf5ec9fe04157dba9342","title":"","text":"Would be great to see a tooltip on links, showing the target. Or popping it up in the status bar or elsewhere, like Chrome.\n: Could you please explain the preview functionality bit more with screenshots of Chrome? I am new to open source community and this project. I use vscode often and would love to work on this if someone can guide me a little.\nLower left corner of the Chrome window when I hover the link to your name: ! But I think a normal tooltip would be easier.\nAh yes. I understand what you are talking about now. To verify, where the link is leading to. Seems like a beginner friendly feature. I can pick it up this weekend if anyone can nudge me towards the right direction. :)\nSorry for the delayed response. It seems that tooltips are only shown if the element has a attribute, but not for links that only have a . I wasn't able to find if there is an electron setting to enable tooltips for links without . I think we may have to implement this ourselves. To get started, take a look at this PR that a similar feature to another electron app: Here's where our webview code lives: I believe you should be able to attach a handler to the webview handler. Please let me know if you have any questions about the code or want to discuss potential designs\nI m happy to receive help! :) I was facing issues while trying to build and fiddle around with the source code. Will definitely look into this PR and the code you pointed out this weekend. Thanks for taking your time to post this info. I ll post any questions or designs which I have.\nHi , I will create a PR to add attribute to every .\nFor verification: this was implemented as tooltip when you hover over links in a webview"}
{"_id":"doc-en-vscode-d87ee6f2e3fca592a7ab77b5da2be2eca2ad99db20718285a58a04f6354c2881","title":"","text":"<!-- 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: 1.72.0 OS Version: Windows 10 Pro, 21H2, build: .2075 <brCommand links inside notifications were implemented as described here, or here , i.e. This is now possible using the following syntax: Originally posted by in The feature works great when a single command link is to a notification but fails when two (or more) are present, see the sample code below (2). <brSteps to Reproduce: a new blank extension (JS/TS) the following code to your extension's main entrypoint/command: Expected behavior is to see the notification with 2 command links and their titles but the following is rendered instead: <p align=\"center\"<img src=\"https://user-\" alt=\"notification-command\"</pNote: the provided commands and should be valid and registered for the commands links to work when actually being clicked but that is irrelevant and out of scope for the issue.\nThis looks like a parsing bug to me when converting markdown to HTML.\nBug actually seems to be in since notifications don't use full markdown:\n<!-- 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!\n/verified\n<p align=\"center\"<img src=\"https://user-\"</pIt now works as expected, great job, thanks!"}
{"_id":"doc-en-vscode-135498473f59a12baedf5212853a2a6c9b5f4fa2ae11a22eab3d768290dc8508","title":"","text":"Testing Not sure if actually caused by welcome page bug In dev tools, see:\nI can't repro this on my mac. Please feel free to reopen this issue if you see this again on your machine.\nYes I still see this every time I open the welcome page. Maybe it's because of an extension I have installed that is getting parsed oddly or an experiment? The exception is thrown here:"}
{"_id":"doc-en-vscode-7015422b6a51e7a0f1cc25c4998fa9c0579d9cbe648667786e1dd0d007c60ed6","title":"","text":"VSCode Version: Code 1.18.1 (, 2017-11-16T18:32:36.023Z) OS Version: Windows_NT x64 10.0. Extensions: none Git Bash is not included in the list of defaults if Git Bash is installed as the current user. However, adding the path manually to the user settings works just fine. eg. Steps to Reproduce: sure Git Bash isn't already installed the latest version from https://git- as current user to ~AppDataLocalProgramsGit"}
{"_id":"doc-en-vscode-903a4fc65f908ce3a6c0e3e83da53dbec5cdbd433b697d440f9c5c77c95d89c9","title":"","text":"! quick search. over a file name pick item and click the button to open the file. happens :bug:"}
{"_id":"doc-en-vscode-223a4d0019f718c41ba0786a0306e3c688a510cfe1e47c543bad9dcc3925ccb8","title":"","text":"Issue Type: <bBug</bI am not sure if this was something I accidentally enabled, but it looks like it appeared with the latest VSCode version. Hovering over lines now shows a + symbol in the gutter, and it's highly distracting. Is this a bug, or can it be disabled? VS Code version: Code 1.67.0 (, 2022-05-04T12:06:02.889Z) OS version: WindowsNT x64 10.0. Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (7)</summaryExtensionVersion ------ vsc-material-theme33.2.0 vsc-material-theme-icons1.2.2 prettier-vscode9.5.0 copilot1.19.5865 gc-excelviewer4.2.54 vsliveshare1.0.5561 material-theme3.13.25 (5 theme extensions excluded) </details<!-- generated by issue reporter --\nhttps://user-\nThe \"+\" on line hover indicates that you can leave an extension comment on that line. We used to only show the \"+\" when you hovered over the gutter itself, but now we show it over the whole line so that it's easier to find. This means that you have an extension installed that let's you leave comments in files. The extension might have a way for you to disable this. I would like to add a feature to VS Code that just disables all commenting. Assigning to June to work on this.\ngreat to know, thank you. i'll see if I can figure out what the extension is and will disable it in the meantime. it's very distracting - can you consider an option that preserves the old symbol behavior where it is only displayed when hovering in the gutter? comments are useful but there is now too much distracting movement on screen. it also shows in Zen mode which I believe is counter productive.\nGood point, this should be disabled in Zen mode.\nBit more thoughts on this: Maybe a setting wouldn't be the right fit for this, since a user might forget that it set it and forget about it... or worse, it could be set at workspace level and the user never even knew it was set. Maybe runtime UI state would work best since it isn't as sticky."}
{"_id":"doc-en-vscode-9ebe12ccb5022bb6357f4e4e60a5575557caa0a1ed57957a26cd35734da41ac8","title":"","text":"Additionally, it would be great if there is some indication that comments are indeed hidden as opposed to the current file not having any comments at all. What do you think?\nHaving some indication that there are comments, they're just hidden, makes sense. We should do this. We can start with some runtime UI state and add a setting later if there's a desire for it."}
{"_id":"doc-en-vscode-479d604e789356b95017ab46a0cab1b0977cd48e198ae93e9961f044b0522010","title":"","text":"down in the button, then move outside the button and mouse up You get this border: ! Weirdly enough that's not the same border you get when tabbing onto the button: !\nWeird, by performing this gesture you get to focus the inside the button itself. Will see what the best fix is.\nIt's a bug in the as it does not happen with the \"Publish Branch\" or \"Commit\" buttons."}
{"_id":"doc-en-vscode-4863786c23ddc20424b95080f357721d23c07905dbdfac3ae4010eac8e19772e","title":"","text":"VSCode Version: 1.0 OS Version: OS X 10.11.4 I just upgraded my VSCode to 1.0 release. Since it supports Traditional Chinese now, my default language was set to so that some of comments in the newly config file is in Chinese. As you can see in the following screenshot, a Chinese character \"\", which is equivalent to the period \".\" in English, was matched as part of valid URL, and it caused VSCode direct to a incorrect URL. ! I have a working fix for this issue, the naive solution is to check if in is greater than 128, which means a non-ASCII character. Why to match only ASCII character? Because when you copy a URL from most of web browsers to clipboard, it will be automatically converted into ASCII-only string. Also, I came up with another idea to modify the to let it cache all the result of ASCII characters (0~127). In this way, we only need to modify the default case of the switch clause in the state machine. Which solution is more preferable? Please give me some advice then I can submit the patch ASAP."}
{"_id":"doc-en-vscode-800aeedcdd44be6546dc1064c6362bc9e26c51efb0b22bafa6c57860d27d17ae","title":"","text":"I don't think the state of walkthrough progress is synced between machines, so I see this on each new machine I setup: !\nAgain, we do try to sync the state but there may be a race where it's not available in time. I'll investigate more..\nFixed it by adding the context to the installation event when extensions are synced by settings sync. Walk through component shall simply ignore walk through for those extensions which are installed by settings sync (irrespective of the walk through state is synced or not)."}
{"_id":"doc-en-vscode-85865472202c21b7836d9fe52ee958f2921a9b1e590cc16d3126db4748b6074d","title":"","text":"Issue Type: <bBug</bIn VSC, load a small image, zoom in a lot, close the image. Resize the small image by 10 times. In VSC, load the resized image. VS Code version: Code 1.33.1 (, 2019-04-11T08:27:14.102Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (15)</summaryExtensionVersion ------ Bookmarks10.4.3 npm-intellisense1.3.0 vscode-eslint1.8.2 githistory0.4.6 EditorConfig0.13.0 rainbow-csv1.0.0 dotenv1.0.1 vscode-typescript-tslint-plugin1.0.0 vetur0.19.2 github-actions-vscode2.6.1 rust0.6.1 RustyCode0.19.1 vscode-hexdump1.7.2 sort-lines1.8.0 markdown-all-in-one2.3.1 (1 theme extensions excluded) </details<!-- generated by issue reporter --\nI would like to take this. I think we can store more information in . In my opinion, we can add the size or add the SHA1 value of the image? Do you have any suggestions?\ncan i work on this?\ni didn't know that already started working on this, both prs work. as far as mine considered, i'm resetting scale to 1.\nI'm sorry that I didn't reply to you immediately. Do you reset the scale every time you close the image? It makes the editor cannot remember the scale and offset even the image isn't modified.\nyes you are write. let me close mine. :+1:"}
{"_id":"doc-en-vscode-c779e2970bf17caf1103019e45625787ec0f2266a33c73c9ec6b09bb23c8cb7a","title":"","text":"VSCode Version: 1.27.1 OS Version: Windows 10 (Build ) Steps to Reproduce: a simple (build) task setting presentation.showReuseMessage to false the task a blank line where the reuse message used to show up, instead of no extra line displayed at all Does this issue occur when all extensions are disabled?: Yes I was expecting this setting to reduce the overall lines printed by running the task, but all it does is prints an empty line instead of removing the line completely.\nAble to reproduce.\nI currently set . I can't simply set it to false since this would close the terminal. Any advice how to avoid the blank line?\nI guess you want to pass in and handle it here:\nOK. I will change the code as follows: if waitOnExit is a boolean honor it and never print a message if it is a string wait and print the provided message. Is this OK for you ?"}
{"_id":"doc-en-vscode-bc4f9dc84da65b1fd80881bceea5d129533f96321a80eb6fe69e0d4e2465878d","title":"","text":"Testing !\nI just noticed that is not localized and is not meant for display. That means that \"Label\" was not a good name for that function, but we can either just remove the state or find the code that drives the state label in the callstack.\nActually, it seems that only displays , , or , which is probably not super useful to the user anyways. It seems like the info like is only available on each thread, and a debug session can have multiple threads. Perhaps we should just remove the state for now."}
{"_id":"doc-en-vscode-0d4f321ab3bd7e21b37031d1f88aaf538bffb4cc1fa4a6a584ca0c5e7144fae4","title":"","text":"Type: <bBug</ba git repository on a UNC path the folder in VS Code the repository as safe ! repositories will be shown instead of one. ! The issue is ephemeral and only one repo shows after reloading the window. ! VS Code version: Code 1.84.2 (, 2023-11-09T10:51:52.184Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (17)</summaryExtensionVersion ------ 2sxc0.0.1 vscode-tailwindcss0.10.3 dart-code3.76.1 flutter3.76.0 xml2.5.1 batch-rename-extension0.0.6 csdevkit1.0.14 csharp2.10.28 vscode-dotnet-runtime2.0.0 vscodeintellicode-csharp0.1.26 python2023.20.0 vscode-pylance2023.11.10 remote-ssh0.107.0 remote-ssh-edit0.86.0 remote-explorer0.4.1 sqltools0.28.0 postman-for-vscode0.13.1 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nare you able to reproduce the issue with the latest ? I went through the steps, but in my case only one repository is being shown. If you are able to reproduce with the latest VS Code Insiders release, could you please go through the steps up until the point where two repositories are shown and share the contents of ? Thanks!\n<!-- 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!"}
{"_id":"doc-en-vscode-fec2033e00cc1098b14beee20c8fcd70d8b14a2707d5e35deea356fab2b96503","title":"","text":"<!-- 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. --Steps to Reproduce: a vscode extension repository (e.g. ) to contributes commands (e.g. ). \"command\" and observe the tooltip <img width=\"857\" alt=\"Screen Shot 2020-09-05 at 21 07 16\" src=\"https://user-\"<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes Does this issue occur on Insider?: Yes"}
{"_id":"doc-en-vscode-96dcf093e3cdef8d6dc308f53733fe0e52f73534987c26c442df46e820eab5d7","title":"","text":"Type: <bBug</ba TS file at the language status item in the status bar Bug The bracket icon is instead rendered as a pie chart icon <img width=\"222\" alt=\"Screenshot 2023-01-18 at 1 28 37 PM\" src=\"https://user-\"VS Code version: Code - Insiders 1.75.0-insider (Universal) (, 2023-01-18T08:53:10.224Z) OS version: Darwin x64 22.2.0 Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<!-- generated by issue reporter --\nLooks like the id for got duplicated:"}
{"_id":"doc-en-vscode-56cb596936a4151ac76e243fb73d677d42db84a1fe64cc0fff09e4fe8f5aa7e7","title":"","text":"The static \"when\" clause on chat participants should be moved to the set of things that are finalized.\nwhat would happen when a participant becomes \"disabled\" after having been interacted with? Evaluating going from to and to again\nIt would just stop showing up in the suggest widget and you wouldn't be able to invoke it. But it can still show up in your conversation thread. Same as if you uninstall a chat extension.\nVerify that can be set and used on the chat participant contribution in without api proposal needed. Easiest to use the ."}
{"_id":"doc-en-vscode-42db0d76263239affccd24e6c9d9efea58be9033d629675f1cad9be8e05e7fcf","title":"","text":"Open following url Install dialog is shown asking user to install and open extension <img width=\"275\" alt=\"image\" src=\"https://user-\"- After clicking on install, following prompt is shown <img width=\"454\" alt=\"image\" src=\"https://user-\"Second prompt seems to be unnecessary. It is expected to open the URL after installing"}
{"_id":"doc-en-vscode-78054dbe91c9f8881e4322879aa3dfce03921e66e4c21044d4c221420e39e62f","title":"","text":"Don't know if this is the intention or a bug. See\nI believed this is a bug, and I've sent a PR for this. cc\nIt was indeed, thanks again"}
{"_id":"doc-en-vscode-441e9421344d9a49d5ae5314362a98c2050e067628158c7b5c5425adfc638425","title":"","text":"an explorer with a lot of elements tree horizontal scrolling covers the last element and there is no way to read nicely the content of that element I would expect the scroll is rendered below the last element, not on top of it\nCan you share a screenshot?\nIf it could help, here is it: !\nAlso here's one from the explorer !\nSeems to be a special case of combination between our scrollbar and the tree: the row is less than double the height of the scrollbar. We should add some extra pixels at the end of the view.\nHello. I want to take this issue. Could you give me a hint where should I start?\ncan i take this up? some insights will be helpful.."}
{"_id":"doc-en-vscode-95e69f0b4252405e08d683518ac5c9e3c0f24d633b031bfc44d82f3f54b72079","title":"","text":"Type: <bBug</bI suddenly started getting the following message when my terminal starts up: I did not install anything but I did update the application. VS Code version: Code - Insiders 1.80.0-insider (Universal) (, 2023-06-21T08:23:42.803Z) OS version: Darwin arm64 22.5.0 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (17)</summaryExtensionVersion ------ vscode-tailwindcss0.9.11 language-hugo-vscode1.3.1 vscode-eslint2.4.0 gitlens14.0.1 prettier-vscode9.15.0 vscode-github-actions0.25.8 vscode-graphql0.8.13 vscode-graphql-execution0.1.8 vscode-graphql-syntax1.2.0 endwise1.5.1 vscode-duplicate1.2.1 remote-containers0.296.0 code-spell-checker2.20.5 vscode-mdx1.3.0 simple-ruby-erb0.2.1 gistfs0.4.1 pretty-ts-errors0.4.1 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nI also encounter this issue!\nReproduces only when fish is installed via\nIE contains binary so hard to know what's going on here !\nany thoughts here?\nFWIW is a (if you weren't using directly, vim, maybe you were looking at it with ?) and those are binary but probably isn't. It probably isn't interesting either. As for the problem, this happens at the initial invocation of so I'd guess it runs into the branch where exists and it's trying to initialize the integration but that function isn't defined yet, and I'd guess moving that invocation from line 125 to after is defined should fix this issue.\nI think the idea that this bug is only present when using brew to install fish is not quite true, I'm seeing the issue on a Windows machine using WSL2.\nThanks that fixes the error. Shell integration still doesn't work because isn't getting run, so will investigate that\nFor this case, when installed via brew, there is a . Moving from to fixes this."}
{"_id":"doc-en-vscode-641c93047d3e0fed01f0a37a6f601e5d09d0e58cb428900758f2ffbe9966e676","title":"","text":"So the repro is to have a\n<!-- 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!\nshould I be able to repro this just by installing fish with brew and using shell integration there or is there other custom fish config required?\nYep that is how I reproduced it\nI have fish installed via are and have shell integration enabled and I am not seeing any errors neither in stable nor in insiders. Is there a step I am missing here to verify?\nReproduced in 1.80.0-insiders Verified fixed in"}
{"_id":"doc-en-vscode-850587d1785a24b948b514ca839a7abb77b91a0d482bbad812a06dd0ddb85384","title":"","text":"Issue Type: <bBug</bRepro settings editor, search for Bugs <img width=\"588\" alt=\"Screen Shot 2020-03-16 at 10 04 28 PM\" src=\"https://user-\"In the settings UI: If I don't know what ligatures are, the description is not useful. Maybe link to our documentation? The description also does not explain the font features part. Maybe have an example? I have to use the settings json editor to actually change this setting. I suspect the most common use of this setting is turning it on or off In the settings json editor: It was not clear to me at first how to configure the font features (for a while, I thought it was supposed to be an object instead of a string) If you have and hover over the string, the description of what this string does is very generic VS Code version: Code - Insiders 1.44.0-insider (, 2020-03-16T07:10:59.884Z) OS version: Darwin x64 19.3.0 <details<summarySystem Info</summary </details<!-- generated by issue reporter --\n<!-- -96bd-47a8-a0e8- --This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our . Happy Coding!\nI'm moving this to backlog since this is more of debt/polish item (it's not one we'd expect users to search out and vote for)"}
{"_id":"doc-en-vscode-01a1567f15e0913849335ef6428dd29c135615d993d22857cfa6446cebf9675d","title":"","text":"Issue Type: <bBug</bAfter upgrading to 1.68, text selection in the integrated terminal does not show selected text. This is purely a visual glitch, as I can still copy what I had selected on the terminal. My colleague has the same version but does not have this issue, so I'm wondering if it's an issue introduced through my update. VS Code version: Code 1.68.1 (, 2022-06-14T12:48:58.283Z) OS version: WindowsNT x64 10.0. Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (42)</summaryExtensionVersion ------ project-manager12.6.0 github-markdown-preview0.3.0 markdown-checkbox0.3.2 markdown-emoji0.2.1 markdown-footnotes0.0.7 markdown-mermaid1.14.0 markdown-preview-github-styles1.0.1 markdown-yaml-preamble0.1.0 keymapceditor-vsc0.7.7 gitignore0.7.0 doxdocgen1.4.0 transformer1.12.1 git-extension-pack0.1.3 githistory0.6.19 gitlens12.1.1 EditorConfig0.16.4 align-mode0.0.21 better-cpp-syntax1.15.18 cmake-language-support-vscode0.0.4 theme-karyfoundation-themes26.2.1 vscode-docker1.22.0 vscode-dotnet-runtime1.5.0 python2022.8.0 vscode-pylance2022.6.20 jupyter2022.5."}
{"_id":"doc-en-vscode-516df2ea603e5fe763de4a3eee64ef4d6bdf20061a703642b02f44d92d8c1239","title":"","text":"jupyter-keymap1.0.0 jupyter-renderers1.0.8 remote-containers0.238.2 remote-ssh0.82.1 remote-ssh-edit0.80.0 remote-wsl0.66.3 vscode-remote-extensionpack0.21.0 cmake-tools1.11.26 cpptools1.10.7 cpptools-extension-pack1.2.0 makefile-tools0.5.0 indent-rainbow8.3.1 vscode-pbtxt0.0.4 cmake0.0.17 vim1.22.2 clang-format1.9.0 vscode-open-in-github1.3.6 (5 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nSame issue, I'm using theme. When I switch to a different theme the selection is visible. Looks like a theme issue.\nCan you reproduce the issue in Insider's? I see selection in Insider's when using solarized light, but it does seem pretty light !\nI believe we're implementing solarized light correctly here and that's how it's meant to work. If you're not a fan of the low contrast selection you can change it with this setting: Otherwise change to a theme that you prefer. Let me know if I misunderstood and the selection is actually not visible (not just subtle).\nI was using the theme for a while and I was used to the low contrast on selection. It was quite ok on my screen TBH. Now there's no visible selection. Here I've selected \"Counting objects\". I've actually pasted it from the terminal instead of typing to be sure. ! I don't think this issue is ready for closing.\nDo you have any settings set and does changing help?\nI strive to work on defaults. No settings in Setting to true causes selected letters to become slightly lighter, but no background. \"si\" selected ! Not sure if it has anything to do with it, but the issue seems to have started after the recent update (via PPA on an ubuntu flavor). After updating I didn't restart immediately, but attempted to open an image and everything crashed. Restarted after that and noticed selection not working a bit later.\nSome more things to try: Does closing all windows and running fix it?"}
{"_id":"doc-en-vscode-850bda91d3e305a6b568eb934d300ac7ce45f007a45863fef6f49dcb1792197c","title":"","text":"If not, can you share your full file? Running the Generate color theme from current settings command will let us see if there's something weird going on with the theme\nConfirming this is only happening in Solarized Light\nDisabling GPU doesn't help <details</summary{ \"window.menuBarVisibility\": \"toggle\", \"editor.minimap.enabled\": false, \"[javascript]\": { \"editor.defaultFormatter\": \"vscode.typescript-language-features\" }, \"javascript.updateImportsOnFileMove.enabled\": \"always\", \"[json]\": { \"editor.defaultFormatter\": \"\" }, \"[typescript]\": { \"editor.defaultFormatter\": \"vscode.typescript-language-features\" }, \"\": \"stuff=\", \"explorer.confirmDelete\": false, \"explorer.confirmDragAndDrop\": false, \"[html]\": { \"editor.defaultFormatter\": \"\" }, \"[jsonc]\": { \"editor.defaultFormatter\": \"\" }, \"workbench.colorTheme\": \"Solarized Light\", \"editor.inlineSuggest.enabled\": true, \"editor.renderWhitespace\": \"none\", \"[css]\": { \"editor.defaultFormatter\": \"esbenp.prettier-vscode\" } } </details<details<summarycolor theme from current settings</summary</details\nI can't reproduce based on those settings so I'm a bit stumped on what to do with this one\nSo I checked the terminal background on the screenshot and it's which is exactly the same color as the default selection color. the dump I pasted above had in it, which seems odd. But since you didn't raise it, I'm assuming it's supposed to mean the actual background is the one of the panel inside which the terminal is working. What I also noticed about the terminal panel is it's no longer giving me the option to move it to the bottom of the window, which is odd, but most of all when I right-click, it no longer says \"move terminal right\" as an option, but \"move sidebar\". I checked, and means I will no longer see my selection. Conclusion is what ends up being the color behind terminal text. The theme should probably set terminal background or change the selection color as a fix. I wonder what else breaks because terminal is now a sidebar not something else.\nAh ok, thanks for looking into it. Because of this, setting the terminal background explicitly is a good solution for now."}
{"_id":"doc-en-vscode-332866d567eaee62744fb85e83135062fbaa7a7e3b1cccef8051a6780f93f4e4","title":"","text":"I doubt it happens in many other themes since contrast is usually pretty high but I'll check Solarized Dark as well when fixing."}
{"_id":"doc-en-vscode-e2772efe9f07ea900cafe15f3a2638ec4d842bf2537786c5118887e6d4302902","title":"","text":"The : This doesn't currently work in VSCode. It does support a very wide range of formats and I don't recall ever seeing this format before (even from GNU tools) so I suspect nobody else uses it. Nonetheless it's easy to add support in VSCode. See\nDoesn't seem to work, see <img width=\"825\" alt=\"Screenshot 2023-08-29 at 14 41 05\" src=\"\"\nThe PR intentionally left that out: But it should be easy to add so will leave this open."}
{"_id":"doc-en-vscode-0863a817d6fa75b923bc630a9251b262c17364708b13531cc34f6304f62ac4c8","title":"","text":"<!-- 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: 1.73.0 (Universal) OS Version: 13.0 Steps to Reproduce: open (cmd+p) file The UI button for from quick open works. The shortcut also works for file selection in the explorer My settings: Related to\nThanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.73.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!\nSetting aside your Ctrl+Enter issue, did you know that Ctrl+RightArrow will already do what you want? It intentionally leaves the quickpick open so you can open another of the matches, but it's easy enough to close by pressing Esc.\nctrl+enter appears to be working for me even with your settings. What is it doing for you?\nThis issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!\nsorry for the late reply. has the same effect as for me, it opens the file in the current tab. this also opens the file in the current tab for me, leaving quickopen open\nif you remove these keybinding settings, does anything change? I'd also love to see what settings you have in your user settings to see if maybe something is up there.\nThanks for reaching back. I commented all keyboard shortcuts and disabled all extensions. Indeed I got it to work when I commented all config of . Then I got to pinpoint it to this setting: which apparently needs to be ."}
{"_id":"doc-en-vscode-dcc25bc78627cec2d000d16958cc74204ab98facae06cc51f586b32fce44540f","title":"","text":"Thanks for your help!\nThat's interesting. is there are scenario where we can open to the side but as a preview? I wonder if this is why this setting affects the behavior.\nThis is driven by this line: I can only speculate that when I re-implemented quick open, I took this behaviour over from our first version. If I had to guess, then we had this rule back then: always opens to the side opens an editor as non-preview when preview editors are enabled opens an editor to the side when preview editors are disabled So I would argue that -click is the key to use here, same as for the explorer for example. And has special semantics depending on your settings. But we can certainly revisit this and make it consistent if there is inconsistency.\nThanks. That is the behavior I see. Maybe we update the setting description to make this more clear? Current: Maybe we add: \"non-preview\" or whatever jargon we use. Thoughts Not entirely sure we need to define Preview editor here too.\nYeah I like the idea of updating settings, feel free to do that!\nverification: read the docs for the settings. Does the use of there make sense (knowing that we don't want to change the behavior)"}
{"_id":"doc-en-vscode-6aaa7028c6955e64a880d8ac265d98af7fec6e2ca34a888b4f7d25d46c061d78","title":"","text":"Visual Studio's Output window has a \"Toggle Word Wrap\" button, but VS Code has word wrapping always (?) enabled. For certain scenarious like the pending \"C/C++ References\" output it is desirable for word wrapping to be disabled for the results to be more easily read. There is a \"View: Toggle Word Wrap\" command, but it applies to the active document only (and not the Output panel, even if it's active). And/or if the OutputChannel interface could add a toggleWordWrap capability, that would allow extensions to set an appropriate default for their particular Output channel. This seems like a pretty basic feature that other Output channel providers would want, but I couldn't find an existing feature request on this.\nThis describes the same issue and led to adding a config option but it doesn't seem to work or the feature request was misunderstood?\nThanks a lot -- I can use that [Log] setting as a workaround (by setting it in our configurationDefaults); however, the result is still not ideal because it will apply to all Output windows and our C/C++ extension would prefer to isolate the behavior to a specific one. (And a button in the UI would make it easier for users to figure out how to overwrite our \"no wrap\" default).\nCurrently, one workaround is to set:\nYes, that is the same workaround I was describing (which our C/C++ extension uses), but it applies to all the output panes, and we'd prefer to isolate the change to a particular output pane (e.g. \"C/C++\" or \"C/C++ References\" and not \"Git\", etc.).\nthat's a nice to have feature.\nFor log files, I had the word wrap button visible & after a few moments it just disappeared\nIt looks like the 'editor.wordWrap' setting no longer works for [Log]. Was it removed intentionally or it is a bug?\nThat setting is working for me with non-Insiders VS Code with our C/C++ output window, but I see certain output panes like \"Window\" ignoring the setting somehow (i.e. it always wraps).\nAh, it's working for me now. It looks like it requires a Reload Window after it is set.\ncommand is now also supported for Output Channels."}
{"_id":"doc-en-vscode-c786d4380e1e093b5ed832bae33c3098eb1e3f06af522bdc15e587e6c146dae0","title":"","text":"Testing Linux some commands in your terminal 1 Terminal Clear Command History 1 Terminal run recent commands the commands are still there, nothing got cleared !\nThis is by design as clearing history only clears the previous session commands. We don't discard the current session as they're all in the active terminal marked by decorations. It does however clear the active terminal's current session history from the previous session history (which hides by default as they would duplicate the content).\nI find this very counterintuitive... As no other clear command in VS Code behaves that way.\nI cleared recently opened and the active windows still show up, this is essentially the same thing the terminal history is doing: !\nOn macOS, i run , and when i run again, i can see all the commands, including those from the previous session. <img width=\"802\" alt=\"Screen Shot 2022-02-24 at 11 07 24 AM\" src=\"https://user-\"\nI agree that it's a little confusing. Perhaps we should say instead?\nI now get the clear command history and a clear previous session command history command. Neither command seems to be clearing the command history. I'm on Windows with pwsh. !\nthe change you made was to the quickaccess code, this is nothing to do with the terminal so we need to revert that\ncan you help with verification steps for this one. Since I do not see the \"Clear Command History\" in quick pick. Does this only appear on Linux?\nthe title of the command is\nthanks. After running that commend I still see the recent commands. So the command history is not cleared. Is this expected?\nI still see previous session history commands given to the terminal after running the command.\nis the group called or is it or something similar? Only the first is expected to be cleared. This worked fine for me just now."}
{"_id":"doc-en-vscode-a2c2c5a84340dab02d8b6b2137e1005eb7e8e9d9d94df50a190f294f687f5f4e","title":"","text":"Testing ! !\ndoesn't reproduce in the panel chat\nI somehow suffer from this change which explicitly targets some monaco tokens...\nThis isn't nice but there's actually no other way to override the foreground color of an editor- because typically you have syntax highlighting. We do this for all the other \"input box\"-style editors. I think I opened a feature request when I did this. We should align this rule with your rule for coloring the decoration so that it can override it properly.\nlabeling so it gets verified\nThanks\nin the latest insider's, still seeing this ! !\nThere is two separate issues with different steps. There is a difference between rendering of slash command and normal prompt text. the only useful/visible information in the original issue description is slash commands (please use words and not images to describe issues!). For verification you have not used slash commands but normal prompt text which is a different case. Please file a separate issue, use words/steps and don't rely on screen captures with just white on white text\nSteps to reproduce/verify use HC light and dark theme open inline chat and type a slash command, e.d make sure the command is readable when selecting its text"}
{"_id":"doc-en-vscode-6cb6daf5d7074d513290a7e14bc3a8bbabf76fbab5588361a263e99a778845ac","title":"","text":"<!-- 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: 1.71.0 (user setup) OS Version: Windows_NT x64 10.0. Git Version: 2.30.2 (Windows) Steps to Reproduce: a new directory a new Git repository a new file and append some text on the first lines this file to the staging the line with text An OS native dialog box error pops up with the title of this issue as text. In the console output for Git: I have had this problem for a long time, 2 years I would say. I thought someone would have reported it but it seems not.\nI'm having a similar issue on macOS 12.6 (21G115). If you have deleted lines at the top of a file and click the little arrow to undo the change, the error pops up. Notably, it still completes the undo. <img width=\"396\" alt=\"image\" src=\"https://user-\"\napologies for not getting back to you on this. I used the repro steps above but I was unable to reproduce the problem with the latest VS Code Insiders (1.75) release. Could you please do me a favour and see if you are still able to reproduce the issue? If so, could you please share a recording using so that I can further investigate the issue? Thanks!\nIssue is still present in the latest insider release on macOS. !"}
{"_id":"doc-en-vscode-3ff2fd5887a667817cecfbd91316ed91f163912473583fffcc2698030d395289","title":"","text":"VSCode info: Version: 1.75.0-insider Commit: Date: 2022-12-19T05:35:41.089Z (10 hrs ago) Electron: 19.1.8 Chromium: 102.0.5005.167 16.14.2 V8: 10.2.154.15-electron.0 OS: Darwin arm64 21.6.0 Sandboxed: Yes"}
{"_id":"doc-en-vscode-7968e33d67cf90c3b0a845d794b37065dc83f9fff6d95e41d5b262899d1d337b","title":"","text":"There is no drop hover feedback in the Explorer, for example, when in Light+ theme.\nBroken by:"}
{"_id":"doc-en-vscode-ca197bcb65a18fcb1c2d44a19ac3d9c307fae31c5c8c0881303f8cab3829fecc","title":"","text":"<!-- 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: 1.75.0-insider OS Version: Linux Hello, IMHO, the block cursor could use a different background. Default Dark+ Experimental (v2): ! ! Default Dark+: ! ! Default Dark+ Experimental (v2): with some cursor background color. For ex: ! ! ! ! Edit (one more option) (with color set to 's value, giving inverted cursor effect) ! ! Thanks"}
{"_id":"doc-en-vscode-a8be4aba3d27aa5d4d4a90db87aa14f6eb6d630bae4e9dfc247f4fe9a33d3434","title":"","text":"Presumably related to . Adding breakpoints to lines with gutter icons causes the icon to be stretched and cropped: ! I don't know if related, but I'm using :\nThe problem is that we set each decoration 's width to be the width of the entire gutter (which is sized to fit potentially multiple decorations, so sets which ends up stretching the decoration to fit the entire gutter instead of just its lane.\nFix looks good, thanks! /verified"}
{"_id":"doc-en-vscode-c981e06165cf60c416b9fcd2e2ae39ea4f9b187182cf48239832153439ee7046","title":"","text":"type at the end of line have ghost text accept it word by word when reaching the end of the viewport accepted words aren't revealed https://user-\nfyi that I have pushed as a fix for this\nThank you! Sorry for not fixing this, I thought the fix was more complicated.\nAccepting single word seems to move the horizontal scroll, but tabbing to accept the whole line does not scroll. Is that expected?\nMarking as verified as word by word works."}
{"_id":"doc-en-vscode-9dfcaa4e314d3b4b49c724ac3a6c588de7c6af6f6cc17f330bf5712a577f5b63","title":"","text":"Error while turning off settings sync ! Might happen when turning off settings sync while a sync is happening\nCan't repro this anymore."}
{"_id":"doc-en-vscode-fae7c06e4f037da30fc28d84d4c74b47207c5f09133ea4e9ef82b92c76629fb7","title":"","text":"Under some circumstances, the Code Action button won't go away and will still run its assign command (incorrectly) Steps to Reproduce: an error with 'Quick Fix' available ! the cursor on the same line and press to bring up the quickfix ! to cancel ! the code action button ! the button again ! again ! ! at step 4. the button should disappear, but it does not I found this bug while adding Code Actions to my personal extension VS Code Version: 1.88.1 OS Version: Windows 11"}
{"_id":"doc-en-vscode-6ad960da9b638fd44420c2d09a444fe4ca4df982ce0bd1c3e03dc4cd87c9a38c","title":"","text":"Perhaps we forgot to update the distro json files (for stable, insiders, oss)?\n!\nit was to distro weeks and many commits ago. I'm not seeing the same error, even when that API is used in insiders/pre-release. - Do you know if I forgot a step for enabling this?\nI think there's a typo, in of distro you have `\"NotebookCellExecution\", and in jupyter extension you have , notice the casing of the first char"}
{"_id":"doc-en-vscode-118c9864bc812c5c5285b356b7660030ed475985d6c6b8f2b88f33fd1be6273b","title":"","text":"Steps to Reproduce: a notebook with the jupyter extension installed context keys the context key contains the entire contents of the file for that extension:"}
{"_id":"doc-en-vscode-ce69298da8e7d2d89aae8081747e5dce2117e8e0b34961c30643617a8d716124","title":"","text":"Testing the steps in the test plan item to create an interactive window I get a notification saying there are extensions on the marketplace that can handle . I feel like this is unnecessary noise\nWhich extension is it recommending?\nThe marketplace query is ext:interactive when I click on Search Marketplace !\nI forgot that we had this but we automatically query show this when there are extensions in the marketplace that match the query . I'm curious about how this works, it seems overly sensitive since these extensions don't use that file extension, seems that it just matches based on keywords? I think the only way to avoid it here is to change the extension that the interactive window uses, which is probably fine.\nDiscussed with and even if we picked an extension that isn't yet in use, we can't prevent extensions from introducing collisions later. What about the following (essentially, parse the notebook URI from the cell URI, and check if it's an untitled://, file:// or vscode-remote:// URI based on the notebook URI instead)?\nWhat will the interactive window be? It won't pass that check?\nIs the motive here is to not show any recommendations for this resource?\nYeah we don't want to show the '.interactive' file recommendation because it's not actually a file on disk. The interactive notebook schema is 'interactive'.\nThen we shall be filtering out in our recommendations logic as you recommended above."}
{"_id":"doc-en-vscode-46132d860968da281ae7fdc3821107276c125692848abd4b9dc93713978a8ed8","title":"","text":"<!-- 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: --Pasting the below into a markdown file will cause a cpu thread to be pinned at 100% because of catastrophic backtracking. fixes it.\n(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.947 --<!-- potentialduplicatescomment --\nThis bug has been fixed in to the latest release of ! you can help us out by confirming things are working as expected in the latest Insiders release. If things look good, please leave a comment with the text to let us know. If not, 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!\n/verified"}
{"_id":"doc-en-vscode-8287704902da9f4413eb8393db60b0b031e85c002daa73b0ef0d54d919946dbe","title":"","text":"WebView width is limited to 780px. ! It shrinks all images included what makes them barely readable. What's the point of this limit? It should be set to either 100% or more reasonable 1200px, but would be best to manage it through <!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.43 OS Version: Windows 10 Steps to Reproduce: any extension page including images in VSCode or hit Help -Release notes <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes and with all themes\nVery long lines of text are not readable You can view the web release notes (or the ones on GitHub) if you want a different layout\nseriously? Someone having problems with reading lines longer than 780px is the reason for this!? Do you even realise how ridiculous it is? And what exactly is a design problem here that it can't be managed by user settings like almost everything else? Please, reopen this issue.\nYou are welcome to submit a PR that makes images larger (while keeping the max text line length the same). However even the images should likely have a max width. See how GitHub and many other sites render readmes\nMy point exactly! GitHub's limit for content width is 882px and I believe it was also like that for VSCode few versions ago. Why it was lowered to 780px is inexplicable. Plus on GitHub you can actually click the image for full size. That's why even Microsoft often adds images 2000px+ width in readmes.\nIt is now 100px wider :)\nBaby steps I'd rather make it 1200px or 100%, but I doubt it would be approved. Maybe someday it will be managed through settings for everyone's content... Thanks"}
{"_id":"doc-en-vscode-d7caf179666101115447648888c8ae283865d540080aeb6daaf2bc72dccab44b","title":"","text":"a command that yields an error in the terminal the quick fix, in the terminal, -` in panel chat !\nI'm unable to repro this. However, I do see an issue with additional unnecessary contexts being invoked. See attached issue for more info. Not a issue.\nI cannot reproduce this behavior when coming from the terminal quick fix !\nBut the very first time I attempt submitting the query, I see that is not picked up by VS Code, cc !\nActually, I now repro not being picked up 100% of the time. We have two s and we're picking the first one, then dropping it because it's not available in panel chat\nToday, I'm not seeing the copilot quick fix in the terminal at all !\nWorks for me on Windows with Powershell, latest Insiders + prerelease :shrug:"}
{"_id":"doc-en-vscode-879a2501e7d34bfd52f867c72e6ada447a0d88bd37ac1b9bfae0730666b8d9ea","title":"","text":"Testing <img width=\"290\" alt=\"image\" src=\"\"I feel like this context menu should not show up in this case - and in fact, it doesn't if you right click on the commit message to the right... it just repros when you right click on the graph part (the dots, or the lines)"}
{"_id":"doc-en-vscode-90aaea065604739f6b5b69e24126b23bce868728d58c9cb8db336a99ecce7954","title":"","text":"<!-- 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: 1.79.0 OS Version: Windows 10, 22H2 Steps to Reproduce: a remote location (e.g. a WSL window) or something else that leads to the simple open file dialog being used a dotfile (e.g. ) an open file dialog with , you can use e.g. the \"Create project from ST project\" action from the embedded tools extension that the file is not available for selection (it can only be manually entered) Note: I originally reported this to the embedded-tools extension (see ), where the \"Create project from ST project\" dialog doesn't allow you to select the required files when working on WSL. They have however redirected me here.\nThanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.78.2. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!\nJust to clarify: I have tested this with both the latest stable release, as well as with the latest insider version. Both exhibit the same broken behavior\nI think this is you because it talks about the simple file picker.\nI think you own . It looks like it doesn't recognize a file named as having an extension of . For now, I will just make the fix in the simple file picker, but should this change actually be made in ?"}
{"_id":"doc-en-vscode-1f90303c64f30e0b19fea8701836013282baf91b0f53e5234782594f82935b42","title":"","text":"Since profiles are removed, the jupyter extension will show their \"run above/below\" commands unless we put them back in the cell toolbar by default, so we should just disable this setting until we have a jupyter profile available that disables it"}
{"_id":"doc-en-vscode-2b729f3b406e8a5e6e56d49143c944703337fff12b5efdb219afabd20037e107","title":"","text":"<!-- 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. --- Version: 1.59.0-insider Commit: Date: 2021-07-31T00:42:32.346Z Electron: 13.1.7 Chrome: 91.0.4472.124 14.16.0 V8: 9.1.269.36-electron.0 OS: Linux x64 5.13.5 Steps to Reproduce: a project directory that is hooked up with tasks via v2. The file must define one of the tasks as being the default. you have bound to a shortcut (mine is ctrl+shift+b) the key combination to trigger the build picker combobox to choose a task appears instead of the default task being executed as used to happen before.\nI'm not able to reproduce this issue. Do you have a repository I can test with? I tried with: If there is more than one default build task, then we have always shown the picker. If there is only one default build task, then we run it.\nI'm experiencing this with internal company code which cannot be shared. I can share the file. It should work with any c# based project.\nHas the schema for changed at all in the past month?\nI've replicated this on other similar projects, even those that have just one task defined.\nThanks for the additional details and for reporting this issue!"}
{"_id":"doc-en-vscode-d8470ef404e48e1c6da369389a73a3cf7c24cc6c1f33063d5d4671d5d151a027","title":"","text":"Type: <bBug</bIssue Reporter, e.g. from off Command Palette. the first dropdown to VS Code version: Code - Insiders 1.92.0-insider (, 2024-07-24T07:50:18.385Z) OS version: Windows_NT x64 10.0. Modes: <!-- generated by issue reporter --\ngood catch, thanks! looks like an issue with the refactor"}
{"_id":"doc-en-vscode-79975b2f202c575840312c4ad7e9dcc43dfcf5af2212e3548a94368adbe3aebf","title":"","text":"a TS file, use the keyboard and type out a syntax error. The scrollbar error marker doesn't show up. the text cursor to another location using the mouse. The scrollbar error marker shows up then. says:\nVery likely a regression from"}
{"_id":"doc-en-vscode-56926236e2ff478ac1bda76c1146e1b2eb5032208e70e0784150e21a56cef01d","title":"","text":"VSCode Version: 1.47 insiders OS Version: Windows Steps to Reproduce: on the \"Add item\" button in and press enter. ! Does this issue occur when all extensions are disabled?: Yes"}
{"_id":"doc-en-vscode-8be6baad17349a47c1a84286144986e591f5f05c4b502eade9f731e089840f9f","title":"","text":"Issue Type: <bBug</bWhile doing some experimentation with Bootstrap and the corresponding scss files, I encountered an issue while changing hexcolor codes. I was able to reproduce it on a different Windows machine (Windows 11 in that case) as well as on macOS (Monterey). Steps to reproduce: Open a large scss file. In my case, I used from the Bootstrap framework. Start changing a color by typing a different hex value. The issue only happened when changing at least two of the six digits and sometimes only after making a couple of changes. It did not happen when using the color picker. will become unresponsive eventually. For example the color pickers do not show up anymore, saving a file takes multiple seconds and the git integration stops working entirely. When the builtin SCSS extension is disabled, everything works fine. Therefore I would assume that this extension is causing the issue. VS Code version: Code 1.63.2 (, 2021-12-15T09:40:02.816Z) OS version: WindowsNT x64 10.0. Restricted Mode: No <details<summarySystem Info</summary </detailsExtensions: none<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nI can reproduce open a scss file with on the end of line 15, add a character . Note that diagnostics appear, Remove the character, diagnostics disappear (all good) on the end of line 15, add a character . Nothing happens. Hover over a symbol, hover computes forever: Extension host is blocked remove the letter, reload the window disable the emmet extension repeat the steps, now all is working When profiling, the emmet extension is busy in The bug got introduced in 1.53\nThere are 3 conditions that must be met to trigger this issue: must return one of , , , , or (so that in returns true). File must be longer than 1000 lines (so that is called as noted above). The first must begin with The culprit is from When trying to skip over blocks, this function attempts to peak back 1 character when it encounters to check for a (1)()` is then called to move the position back to where it was at the start of the function, but in this case moves it back to position 1:2."}
{"_id":"doc-en-vscode-14eda707ad1f8a06b816d99f1fd86287cc25404cfca9a55f5fa76ba2159a95c3","title":"","text":"This causes the loop that calls to loop infinitely, as the exit condition (position being to , in this case the start of the file) never occurs. Pull Request Resolves this by checking if the character being \"peaked\" at is a and breaking out of before is called. An alternative solution would be to not call if is within 3 characters of (as there is not enough space remaining to contain .\nThanks for the explanation I'll comment on the PR."}
{"_id":"doc-en-vscode-7db26f2e792506f6f05c2c5c974018280f6d7459a6d1eefa3e1a1adf954afbdf","title":"","text":"<!-- Do Not Delete This! bugreporttemplate --Issue Type: <bBug</bWhen trying to run with a markdown-code which contains a picture, a is thrown: My extension uses the vscode-parser for converting markdown-files to pdf, so my extension depends on the vscode-parser and needs it to work. Steps to Reproduce: a new extension to the -file following code to the extension: VS Code version: Code - Insiders 1.54.0-insider (, 2021-02-18T05:14:01.684Z) OS version: WindowsNT x64 10.0."}
{"_id":"doc-en-vscode-fcd0879d6a4b9b5b843daf7922f295d6bc97fbf70af003ecf99142152aa78fbe","title":"","text":"<details<summarySystem Info</summary </details<details<summaryExtensions (41)</summaryExtensionVersion ------ silverstripe1.0.6 ts-loader-problem-matcher0.3.0 markdown-emoji0.0.9 markdown-mermaid1.9.2 better-toml0.3.2 arm1.5.0 javascript-ejs-support1.3.1 vscode-reveal4.0.3 php-debug1.14.9 php-intellisense2.3.14 php-pack1.0.2 cshtml-tm1.0.0 coldfusion1.0.1 reg1.0.2 vscode-edit-csv0.5.4 vscode-peacock3.9.1 languague-renpy1.0.6 eslint-language-service1.0.8 rainbow-csv1.8.1 git-graph1.28.0 vscode-apache1.2.0 csharp1.23.9 remote-containers0.160.0 remote-ssh0.64.0 remote-ssh-edit0.64.0 remote-wsl0.54.0 vscode-remote-extensionpack0.20.0 hexeditor1.4.0 powershell2020.6.0 vscode-typescript-tslint-plugin1.3.3 vsliveshare1.0.3784 debugger-for-chrome4.12.12 php-docblocker2.1.0 material-icon-theme4.5.0 ejs-language-support0.0.1 ruby0.28.1 vscode-yaml0.15.0 vbsvscode1.2.0 vscodeintellicode1.2.11 vscode-ruby0.28.0 markdown-all-in-one3.4.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nWe'd take a PR. However this looks specific to how your extension is using the markdown extension point in an unsupported way so this is not something we'll prioritize fixing\nThanks a lot for your rapid answer. I found myself able to refactor the package to make rendering work again out of the box. I'll open up a PR asap.\n/verified"}
{"_id":"doc-en-vscode-742468c8ba115a13289fe235c5a58211da6ff3e65698b544cf6f1acac7e7a574","title":"","text":"Tracks updating the TS 5.4.4. recovery build\nActually may wait for TS 5.4.5 with a fix for auto imports\nMerging 5.4.4 for now"}
{"_id":"doc-en-vscode-e29a17a0df9d5d3158e20571118e61380067274645dea2644abefbc3da533ffd","title":"","text":"White on gray is not readable. I think the explorer tree has a different behavior here. !\nWhich theme is this?\nDefault Light+"}
{"_id":"doc-en-vscode-f2d8eb2b0bce96aaf7e429c9c24afa3efb80f7c355f13e81ffea1ff0b5093e8c","title":"","text":"Does this issue occur when all extensions are disabled?: Yes VS Code Version: OS Version: Steps to Reproduce: a terminal window within vscode and run this command: vscode hangs indefinitely, using 100% CPU on one core. It would be nice if that didn't happen.\nThanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.78.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!\nI'm using web version (Vscode Server) and this code snippet cause the entirely browser tab to crash: ! Wanted to provide profiling info but profiler hanged too\nI can reproduce\nNice find\nUpstream:"}
{"_id":"doc-en-vscode-89b8312ad9c487a77dd159bef5af0ed47361b8cf3a96e89acca57a3efeda4987","title":"","text":"found testing for a cell to get output ctrl+down to focus the output :bug: visually, it looks like the cell container is focused.\nin the insiders build of 1.83.0, NVDA 2023.2 does read the output but like said it doesn't visually focus it. Unlike NVDA JAWS 2023.2307 doesn't even read the output. And even pressing alt+F2 while using JAWS, accessible view is not even pulled up/JAWS doesn't do anything. While output focus issue is not found in version 1.81.1 with JAWS 2023.2307. Seems like VS Code bug.\nSo this worked but with the keybindings on Mac. Not sure if the keybinding you mentioned is the keybinding on another platform like windows?\nyes sorry, didn't notice that mac keybinding was different"}
{"_id":"doc-en-vscode-2355b87ce2d03c3efc8c95d3f1aa237f8c235dee473b495defdc8ab8ff5dce82","title":"","text":"Testing Version: 1.75.0-insider Commit: Date: 2023-01-24T05:22:50.699Z Electron: 19.1.9 Chromium: 102.0.5005.194 16.14.2 V8: 10.2.154.23-electron.0 OS: Linux x64 5.15.0-56-generic Sandboxed: Yes Export a profile to a file Confirmation dialog shows a question mark, but there's no question here !\nIt's better on Windows: !\nWe can change all dialogs from to use instead of type. This only seems to have an impact on Linux and changes the icon to an info icon."}
{"_id":"doc-en-vscode-fe359104b51a6f6567d65313496de8c249a3c858940d4f6ef3b351119e76ea75","title":"","text":"I see this telemetry event getting sent when toggling the screen reader on whilst vscode is open, however if a screenreader is already on when the editor is opened, the telemetry event doesn't get fired as it's only triggered by Electron's event. This probably isn't the desired implementation here.\nI can take this.\nThanks for catching and fixing this"}
{"_id":"doc-en-vscode-b7d93fb6c87ee39f649aec4b3a3e1c8df2ab17c34fdc55eea86b540c6f2a11aa","title":"","text":"cursor is rendered on top of it <img width=\"400\" src=\"https://user-\"Version: 1.78.0 Commit: Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.78.0 Chrome/108.0.5359.215 Electron/22.4.8 Safari/537.36\nHi thank you for filing the issue. I tried to reproduce this issue, but it seems to work fine on my computer. Could you please try spawning a color picker in the latest VS Code Insiders (). If you continue seeing this issue, could you please try to run VS Code Insiders without any extensions and reproduce this error? It so happens sometimes that extensions cause errors. If you still see this issue, do you think you could copy paste below a minimally reproducible example of the contents of the editor where this happens?\n<details</summary</details! Maybe it only reproduces with zoom? Should it render like that with markers? !\nHi, thanks for the reply, could you post here a copy of your settings file. I am thinking this error could be happening in relation to one of your settings.\nHmmm, it's a 2000 line-long file, not sure how useful it would be. It looks like I can reproduce it on the web with browser zoom and . On desktop that would be:"}
{"_id":"doc-en-vscode-b9358f74d1dc445c28527efa4d7eb2a7e3c5f1970797693e790a6b017dd6a89b","title":"","text":"Problem: A popup opens, displaying: \"The 'Remote - WSL' extension is recommended for opening a terminal in WSL.\" It has a 'Dont Show Again' and an 'Install' option. Clicking Don't Show Again has no effect. Expected Behaviour: Once I click Don't Show Again, this popup doesn't appear every single time I open the WSL terminal in VS Code. VSCode Version: 1.38.1 (user setup) OS Version: Windows_NT x64 10.0. Steps to Reproduce: WSL Ubuntu installed on Windows. the WSL integrated terminal on VS Code. Does this issue occur when all extensions are disabled?: No.\n(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.614 --- <!-- score: 0.559 --- <!-- score: 0.549 --- <!-- score: 0.54 --- <!-- score: 0.52 --<!-- potentialduplicatescomment --\nI wanna take a shot at this!\nDoes this happen on different workspaces or on the same workspace? Edit: I have checked and this only happens when you open different workspaces (Different project folders with VSCode) I personally think that this should not be the case and should be global so I will make a pull request for it.\nSorry for the late reply. I see you've already pushed a fix for this, so thanks a lot :)\nShould I close the issue now?"}
{"_id":"doc-en-vscode-5ef982bc93634d3e312088210012d86c520fb2f08356a9606797c6e056435308","title":"","text":"Testing open search viewlet drag explorer (activity icon) into search pane all explorer views are now in the search pane it is not possible to drag the file/folder view back into the explorer https://user-\nverified since the empty explorer is gone"}
{"_id":"doc-en-vscode-7cea5538de366b50ffbed225d86acdb960f0ceb68e95311592cd5f8601e5678a","title":"","text":"Testing have search view open drag the explorer icon onto it the explorer (and npm script) views show the explorer icon stays in the activity bar, the view is empty https://user-"}
{"_id":"doc-en-vscode-1965c2f93385360ac9fadc946acad04489a243d0c90d92e453bbd6d16b7c5e20","title":"","text":"Notice how in the step was stuck in the following line for at around 2 hours: This could either be from or from . Maybe we should put a log between those. In any case, my bets go against the former... which can be resolved with the  option. WDYT? cc\nYou're a PowerShell pro now!"}
{"_id":"doc-en-vscode-6f4e91727aca2826d9ad6e3e5056d6999c4c9db0511027e22b97e2f6cf5a04c7","title":"","text":"Type: <bBug</bDev Container with default or the prefered profile a new profile from Current Profile Settings After reloading the window you get a message to install the remote containers extension and when opening the profile in a local workspace you can see that no extensions and no settings where copied from the old profile. VS Code version: Code - Insiders 1.70.0-insider (, 2022-07-08T05:20:13.606Z) OS version: WindowsNT x64 10.0. Modes: Restricted Connection to 'vscode-remote' could not be established No remote extension installed to resolve dev-container. <details<summarySystem Info</summary Connection to 'vscode-remote' could not be established No remote extension installed to resolve dev-container. </detailsExtensions: none <!-- generated by issue reporter --"}
{"_id":"doc-en-vscode-7f0cac480fde702b5b09b9805a9cd3831e356014f07199595fa8c42b86d187da","title":"","text":"Splitting from Clone mock-debug Run the tests Resize the window so the debug console has lots of wrapping Run the tests again After a few tests run, the Debug Console will stop scrolling down automatically and just remain part-way through. <img width=\"838\" alt=\"Screenshot 2021-02-25 at 12 08 28\" src=\"https://user-\"\nthanks for steps I can reproduce this. here I am hitting the limitation of what the tree gives me. Currently I use the following heurisitc to figure out if the last element is visible in the tree However that does not give the correct result when elements are wrapped and take additional lines. So I could either somehow update that check, or I could use the . I would just care if there are elements after the last visible element, but I could not figure out any tree api to get next neighbour of the last visible element. Might I be missing something? Let me know what you think, thanks.\nWhat 3 values does it return in that case?\nIn this step we are good: In the next step we are no longer good:\nand me investigated into this and it seems to be related to how async code is handled on the list side. Thus assigning this to on-deck and once finds time he can look into a fix or recommend a workaround for me on the Debug Console side.\nAny progress on this issue? Would be great to not have to manually scroll down during the debug session.\nNot to my knowledge. I've been told a small trick though In the debug console, hit Shift+Tab to move focus from the input box to the output list. Now you can just hit End once to move to the end of the list.\nthanks for the tip, but going through all that hassle every single time I type in a command in the debug console or try to inspect a variable by printing out its type is simply not worth it. are there any viable workarounds to this? I believe it makes the debug console pretty much impossible to use for the average python developer.\nWorkaround is As for progress, we plan to fix this however not sure when. did an initial investigation and it proved more complex than anticipated.\nThanks for your valuable feedback. This works for me. I should probably add that should be to the and not the Just out of curiosity, doesn't that basically solve the problem?"}
{"_id":"doc-en-vscode-159bcccec3e97585b3ea79b60c40bd616f16c2af51294da30ca15e65e66f3142","title":"","text":"What else is there to fix?\nSetting wordWrap to false will not display all output. The line before print(True) is only partially visible. !\nSetting to false also hide the last line (image). It happens when an exception is thrown (e.g., ) Please fix this! !\nany update?\nThat () was a super annoying bug, but today i found this thread and turned off (turned on by default) and it scrolls down automatically!\nPlease god if you exists, please re-create the universe except this terrible bug. The bug makes us sad every minutes in Flutter-based development...\nI want to have auto-scroll with word wrap functionality. This is very annoying bug.\nMaybe this got worse recently, but I am seeing it happen with no wrapping involved, just the simplest single-line output. I think I have a fix. Basically add an item, call updateChildren list renders the item off screen. getHeight returns an estimate that is off by 1px dynamic height is not probed because it is offscreen in tries to scroll to the bottom, but using a scrollHeight measurement that is off by 1px item is rendered, dynamic height is probed, size is fixed, but that means the list is no longer scrolled all the way down, so stops autoscrolling I have an easy workaround to watch for content height change events from the list and update the scroll at this point. I think only Debug Console needs this feature - if it's ever needed anywhere else, we should implement it inside the List.\nThe issue still occurs. I have to manually scroll down to see the newest logs.\nYep, me too. I've turned off wordWrap and smartScrollin my and I still have to scroll down in the interactive console whenever I run code :( - specifcally, when I run code from the interactive console 'Type python code here and press Enter to run' line, as opposed to when I use a keyboard shortcut to send a selection of code to the interactive console (that seems to scroll okay, unless it is a long output - then it doesn't scroll either way). Print(5) for me, run directly from the interactive console, doesn't auto-scroll enough to see the output, even with these settings here:\ncan you share a code snippet that reproduces the issue? I don't see an issue."}
{"_id":"doc-en-vscode-9c43cd8b2822645fd9259ef479ba2de8a273df4c93cee65b99b88d35c5eada8f","title":"","text":"it sounds like you might be using the interactive window which is not what this issue is about. If so, that is\nI'm debugging Flutter apps with option which sometimes outputs a lot of lines of logs at once. I suspect that breaks it. When the log density is normal, it works.\nHow can the fix be tested? Do we need to build from source or is it in the Insiders version?\nIt went out in the latest stable update. If you're still seeing the issue I can reopen it and investigate a little more\nI set up a flutter app and tried debugging it in verbose mode, but it doesn't do anything unusual and I don't see an issue. Also tried some other cases with different types of log messages printed very quickly. are you able to share the app? Or if not, a screen recording of the console, or screenshot of the point where it stops scrolling might help\nSo, basically wrapped lines considered as single line, therefore it miscalculating how many lines to scroll by?\nI'm not seeing an issue with wrapped lines anymore\nI'm not sure this is particularly helpful information (besides maybe helping confirm there's still an issue), but I was just able to reproduce this with a Flutter project (on current stable), but have been unable to repro again while recording. It happened while Flutter was doing checks (it prints a lot of very verbose output with all the HTTP requests to the Pub API). I've tried clearing my Pub cache and modifying my pubspec (with so Flutter would re-check Pub packages when the debug session starts), but have been unable to trigger it again (nor could I repro with the original steps using mock-debug above).\nOh, perhaps noteworthy, when it did happen (sorry I didn't take screenshot, I thought it would be easy to repro!), the last few lines printed were a very long line (a large JSON payload) followed by 1 or 2 short (unwrapped) lines.\nIssue is still happening. I can't find a good pattern to suspect and reproduce it. All I remember is I had disabled the content wrap setting to give it a shot on my wide screen. Reverting it later did not help. I was doing Flutter development on VSCode for 3 years, and from that day, I'm getting this very annoying bug."}
{"_id":"doc-en-vscode-72825cd5e394a2d19a0ae866c944bcdef82aee49efa8e7bad0c25f4c4f7e7ce0","title":"","text":"Can you share the project, or the exact log text that causes it so I can try to reproduce it?\nI have a fix which I think only affects the case when wordwrap is disabled. From this thread, I'm not sure whether anyone was still seeing an issue with wordwrap enabled. It got a lot easier to repro after my fix for fixed an issue with sizing.\nHere's the code I was using to repro the issue: and\nI can't repro now, but I saw this again a few days ago, but I do not have wordWrap set, it's on the default (). If I see it again, is there any useful info I can get from it (other than a shareable repro ofc, assuming I can't make one)."}
{"_id":"doc-en-vscode-c42f6685ad3c939ec8d18740db909caa1e6b198c20bd70d869ca1021bd62c381","title":"","text":"<!-- 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: 1.76.0 OS Version: Windows 10 The most recent VS Code update broke bracket colorization for PHP files, when you close a PHP tag then open it again before using a closing bracket. Steps to Reproduce: a PHP file a PHP open tag , open a bracket with , use an end tag , step 2, but with a closed bracket show as red, and the coloured line that joins the brackets doesn't show. Note: The red brackets are normally only used for errors, so it makes it look like there's errors in the file Screenshot: !\nSame problem here on Unbutu! Could you fix it please?\nSame error on ubuntu Ubuntu 22.04.2 LTS\nAlso happens if you just have the opening tag but no closing tag at the end: !\nHello, thank you to open this topic. I have the same issue while writing PHP code on VSC. It would be great if could be fixed. Have a nice day !!\nSame issue here on Mac OS 13.2.1\nSame here\nFor anyone who needs this fix before the next update: Add this to your settings JSON (fix via PR )\nI have a similar issue using math equations in markdown, the image on the left is version 1.76 and the one on the right is 1.75.1, both of them with the same settings (by sharing them). The fix suggested by did not resolve my problem. Should I open a new issue since it is a different language and context? !"}
{"_id":"doc-en-vscode-a6dc1d7047c96e2d5ed5a47e9eb5289b44bd9bcb7ce6f0147e5cc157c6b74159","title":"","text":"Possibly related on Stack Overflow:\nRelated: :\nSame issue with me\nYou should scope it to language, otherwise the bracket setting applys to all languages\nThe update and modified settings as suggested by didn't solve the issue I mentioned in . Might be related to . Below is the today's insiders version w/o any extensions with the same issue despite even scoping the brackets as suggested by above. !\nomh same here lol.."}
{"_id":"doc-en-vscode-8424e64f7f04e5a3e167a53e1a531440b3b0cfd3347cf5a8e7351413cf3108e4","title":"","text":"open test explorer notice that the input has the wrong background color, e.g it has two background colors <img width=\"455\" alt=\"Screenshot 2023-11-15 at 14 29 05\" src=\"\"\nWhat theme are you using? I can see the slight difference in your screenshot, but inspecting things I'm not seeing any backgrounds being applied to that action / menu bar\nLike, any light theme?\nStill confused on the latest Insiders for me in e.g. solarized light: <img width=\"725\" alt=\"image\" src=\"\"Does it reproduce on a fresh user-data-dir for you? If so, are you able to do a quick devtools inspect and give a hint as to what styling is being applied that makes monaco input have a different background color?\nI see. It doesn't show with an empty profile but I also don't have any setting that screams test explorer background color\nCould you bisect your user settings or share them so I can play around?\nThis seems to be because I have the test explorer in the secondary sidebar. There is some settings that controls this but I have no clue which one it is <img width=\"2188\" alt=\"Screenshot 2023-12-12 at 18 02 53\" src=\"\"\nCSS is fun"}
{"_id":"doc-en-vscode-816c581136f77ec9fc9ab96d22ccaf1aa6791ee5bed4891d7c1ae02a3ec4b2e4","title":"","text":"<img width=\"603\" alt=\"image\" src=\"https://user-\"\n!"}
{"_id":"doc-en-vscode-dffe5656b92fa4c6edbec5018fa2c4dcd4942735b8e045e4a9628d13807094ef","title":"","text":"Testing Ctrl+[RightLeft] Ctrl+Up &mdash; put the cell in edit mode and focused the editor, I expected it to move the focus to the preview cell without changing the selection (like Windows Explorer) Ctrl+Down &mdash; seems to scroll down slowly. Again I expected it to move the focus to the next cell without changing the selection\nIt seems the ctrl+arrows are already being used by actions.\nMeaning expand/collapse headers? Why? If I understand correctly, this is basically what arrow up/down by themselves are already doing, right? ctrl+up/down are matching the editor by scrolling without moving focus. Except that they are double-booked with focus in/out of output, which maybe should only happen when focus is in the editor\nI think the only thing to fix here is that ctrl+up invokes when focus is not in the output, and focuses the editor."}
{"_id":"doc-en-vscode-bd8d00989b70c08f82779744d742bc9bc608e007d4d3ff82b04173d496af9f11","title":"","text":"VSCode Version: 1.41.1 OS Version: irrelevant Steps to Reproduce: : type Declaration: line 2316 [location links][#LocationLink] -(#LocationLink) Does this issue occur when all extensions are disabled?: Yes\nPlease remove it immediately and make it your top priority. To me this is almost equally offensive as a swastika.\nHe think it's funny to imitate ."}
{"_id":"doc-en-vscode-5b47cda2fde76f7cf19026288950264ec2e591608991f78be653e7f98445747d","title":"","text":"Issue Type: <bBug</bSee the , which provides two tasks and and a README with these steps. the task the task again. that each failed in its own terminal, despite what the message in the terminal said. the terminal and press a key to close it. the task . the task again. that both failed in the same terminal, again not shared with the task. closing the terminal, run the task again. that the task reuses the terminal now, but doesn't fail. Instead it just produces no output at all, and doesn't seem to signal that it's finished. The task doesn't hang, it just fails. Its terminal gets reused like the one from . Ideally both tasks would emit the exact same sequence events, including both and so the listener can determine that the task failed. VS Code version: Code - Insiders 1.63.0-insider (, 2021-11-29T08:08:44.056Z) OS version: Linux x64 5.15.4-201.fc35.x8664 Restricted Mode: No <details<summarySystem Info</summary </detailsExtensions disabled<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nor I think the cause of the problem is that doesn't fire when a process task exits with an error like this. I don't think there's anything suspicious in the shell launch configs: ! Would you expect to fire if the process errors out early like this (the command to run doesn't exist)?\nWhen the call to create/start the process fails, like when doesn't exist, it should fire the event here:\nIt does do that, but it seems that something is still not cleaned up somewhere as process tasks run in a re-used terminal don't output the message at all.\nIf you have this repro set up could you also log these? This is where the output happens:\nIn a non-reused terminal: is set to undefined there. is set to the expected message. gets run and gets hit. In a re-used terminal: None of those lines are hit. When I kill the terminal manually they are all hit, but all those values are undefined.\nThis looks much better than before! However, I still see the task's terminal have an . Is this expected?"}
{"_id":"doc-en-vscode-ffbaafb4bf87c45970ff2cf987810ee3e8a068b8efb5411ae5e445baea593549","title":"","text":"Tasks expects the exit code to not be in this case because it indicates that the terminal is being disposed and cannot be reused: Because of this, tasks doesn't keep the terminal around in the task system for re-using, so subsequent tasks will get a new terminal, which is unexpected.\nI think undefined for is expected here because a process never launches, instead it fails because the executable is missing before we try to launch the process. This is different to which would run something like and that would exit.\nis there a way I can tell on the tasks side if a terminal is being disposed vs. just had the above situation happen? I'd like to reuse it if it's not being disposed so that the user experience is consistent. Just iterate though the and see if the instance with the same ID is still there?\nInternally we use to differentiate these: I guess we could just expose that as a type in too, looks like tasks is still the only consumer that uses the value on the event I believe. If you want to try this, change this line: To this or similar:\nI'll make the tasks changes in February:"}
{"_id":"doc-en-vscode-b3ebc5c7962086057349db6216f4b02f2c4a63117f8dfd28a2e9d0448d2d9c23","title":"","text":"I'm using the on a keybinding to quickly switch between different components in a project. A slightly frustrating behavior is that the window list appears in the same order in both windows. This means that when you do , the first window in the list is always selected. So, if you have 2 windows open and you're switching back and forth between them, you have to remember two key combinations, one for each window you're in: Switching from Window 1 to Window 2: Switching from Window 2 to Window 1: only I propose defaulting the selection to be the first entry that is not the current window. That way, it is a \"quick switch\" indeed. :) Thoughts? I will implement this when I have time if there is no objection.\n(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.612 --<!-- potentialduplicatescomment --\nDon't believe this is a duplicate - the other issues think this unexpected behavior is a bug, while this issue proposes a way to make the behavior closer to what the user expects.\nAnother way this could work is to by default, select the window after the current window in the window switcher. So you can quickly flip through 3 or more windows."}
{"_id":"doc-en-vscode-01f110d904b87fa24a14760ad22a3ec6f0060311558d4d44b9520be632b8280a","title":"","text":"<!-- 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: 1.82.3 OS Version: Ventura 13.6 This one was tricky to investigate and is impacting the and & scenario. In that scenario, VS Code is started from one application using the macOS command. This reproduces without requiring Unity and with no extension installed. This seems to be a macOS only issue. When opening either from the macOS Finder or through , the VS Code application will expand the PATH of its subprocess so that extensions that depend on something in the path of the terminal will find it. So in my case, if I start VS Code from the Finder, the processes will look like this: This is expected and good. Extensions can find in the PATH. The issue is that now, if I want to open another workspace in the same instance (but launched from another application), the PATH doesn't get expanded in the second workspace and I get: So in my second workspace, will not be found in the PATH."}
{"_id":"doc-en-vscode-8cd3308a676f6c1676941dbe8b8d4596f85b7b437b87349d73daa372d26a2910","title":"","text":"For this to happen, VS Code must be started from an application launched from the Finder (and not from the Terminal, otherwise it will inherit the PATH of the Terminal) Steps to Reproduce: Xcode, create a new SwiftUI project (I mean, it doesn't have to be a SwiftUI project, you can re-create the issue with anything that is able to output a macOS .app but for this particular repro I used SwiftUI) the Sandbox for the project: <img width=\"562\" alt=\"Screenshot 2023-10-03 at 10 33 02 AM\" src=\"\"the look like this: the variables and to point to 2 different workspaces. the project, I personally use in command line. all VS Code instances. the .app from the Finder, it will be in if you built from the command line by default. the button As you can see from the code, the .app will: set the PATH with a marker open a new VS Code workspace on workspace1 wait a bit open a new VS Code workspace on workspace2 activity monitor, find the child process ID: <img width=\"1045\" alt=\"Screenshot 2023-10-03 at 10 40 50 AM\" src=\"\"the terminal, look at their path: (Your pid may vary) that the second child process doesn't have its PATH expanded, and only inherited the PATH from the .app:\nI think you're best equip to handle this issue? but feel free to reassign to whoever.\nI can't repro this. To know more, please do the following: Quit VS Code From a Terminal, run , this should open VS Code In that window, run and set it to . Then, from a Terminal, run , this should open the second window On the second window, reveal the Output panel and the Window logs. Search for , what do you find?\nthe entire point of long repro is to not start VS Code from the terminal, but from an app launched from macOS. As I said in the bug:\nUsing is the same as launching from Finder. Let me know the result."}
{"_id":"doc-en-vscode-d20146bb1e41e3465be2aee12d62340ba7c4ee987c0385a99bdb3fbbb79e7427","title":"","text":"I'm afraid it's not exactly the same as it exhibits a different behavior as it appears the second instance of the process will simply inherit the PATH of the process that started it, instead of expanding the PATH to be like a terminal Using twice will work as expected from the Terminal as the second instance of the process will inherit the PATH of the Terminal. Using the repro steps to create an app that will call on Visual Studio Code twice won't work as expected. If I close all VSC instances, and do twice on two different workspaces, I get: Things are visibility different as the main Code process seems to inherits the PATH from the Terminal. Whereas if I launch Code manually from the Finder, I get: So there is a difference.\nThanks for testing! Very interesting, I was unaware of differences here. Last I saw this (when I did the macOS integration years ago), did not propagate environments. It seems like it does now. Can you try just once more with: , replacing with the path to the workspace? Thanks, I really appreciate it!\nVersion: 1.84.0-insider Commit: With from the Terminal I get the same behavior as :\nHi we're seeing a growing number of customer reports on this. I think I've provided all the info that was needed including a way to create a self-contained repro. How could we get this looked at? Thanks!\nSame here guys. Just installed unity + vscode and have this message about missing net sdk. I came from here.\nI came here from microsoft/vscode-dotnettools as well – and I'm glad I did! I've been banging my head against the \" isn't on the PATH\" issue (and related!) for quite a long while and with insight from the fantastic writeup for this issue was able to get it to work again. For me, the break comes down to how I open my Unity project in VS Code. I generally open my Unity Projects is with the following: the project in Unity. \"Open C# Project\" from the Assets menu. <img width=\"253\" alt=\"image\" src=\"\"If the project isn't already open, Visual Studio Code will open up a new window and load the project. When this happens, I get all the \"I can't find !\" issues. a new VS Code window (keyboard shortcut/menu/palette/whatever)."}
{"_id":"doc-en-vscode-82162bb1d99ac98c681e55e085af19d21e57c3e8b18daa134dab74deceb06a72","title":"","text":"the project from within VS Code. In my case, I do this via the \"Open Recent...\" menu as what I'm looking for is usually listed there. Regardless, if I open the project in VS Code in this manner, everything works as expected.\nsorry for the silence here. Let's try to figure this one out. First of all, I can't get your Swift sample to work. It launches VS Code but fails to open each workspace properly, even after triple checking that I've changed both workspace paths to something that exists. I really couldn't figure out why... In any case, can I ask you for one more piece of info? from Finder (main process regular PATH, Code Helper with sourced PATH) a Terminal, call the command with the path to the second workspace. What's the of that second Code Helper process that comes up? Resolved?\nHey thanks for bumping this, happy new year, looking forward to having a resolution for this. That happened to me before I turned the sandbox off. See step 2 of the repro? We could also try the real world scenario with Unity, but it's going to be a slightly longer setup, I'd encourage you to reach out to my email at work to help get you setup. In that case: The main Visual Studio App inherits the PATH of the Finder (so just /usr/bin:/bin) The first process gets a PATH expended. The second process inherits the PATH of the Terminal, verified by doing: Just before calling in the Terminal.\nSorry about that. It runs correctly now! And I can repro! Funny: it seems to only affect the variable. If, say, one adds to , that gets properly propagated to both extension hosts (). Interesting, digging more...\nNice! Good luck :)\nGot it!\n<!-- 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!\n/verified"}
{"_id":"doc-en-vscode-8896b4f82ccf5aec05ff505bceb2c067b8001d814ff543e38c4f9e8659176fee","title":"","text":"Issue Type: <bBug The following does not indicate that this is from the universal Mac build: VS Code version: Code - Insiders 1.53.0-insider (, 2021-01-26T05:12:23.287Z) OS version: Darwin x64 19.6.0 Remote OS version: Linux x64 5.4.39-linuxkit <details<summarySystem Info</summary </details<details<summaryExtensions (35)</summaryExtensionVersion ------ unique-lines1.0.0 persona0.0.3 regex0.2.0 vscode-eslint2.1.14 ghlink1.2.0 remotehub0.5.0 tsl-problem-matcher0.3.1 EditorConfig0.16.4 vscode-npm-script0.3.13 codespaces0.6.0 vscode-pull-request-github0.22.0 vscode-mocha-test-adapter2.9.1 vscode-test-explorer2.19.5 rest-client0.24.4 graphql-for-vscode1.15.3 template-string-converter0.4.7 git-graph1.28.0 vscode-azureappservice0.20.0 vscode-docker1.9.1 vscode-kubernetes-tools1.2.3 remote-containers0.156.0 remote-ssh0.63.0 remote-ssh-edit0.63.0 remote-wsl0.53.1 azure-account0.9.4 azurecli0.5.0 hexeditor1.3.0 vscode-github-issue-notebooks0.0.60 debugger-for-chrome4.12.11 vscode-versionlens1.0.9 vscode-yaml0.14.0 music-time2.1.0 vscode-open-in-github1.14.0 vscodeintellicode1.2.10 vscode-test-resolver0.0.1 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nTo verify. check if the universal apps version information in about dialog as well as issue reporter details have it like <img width=\"564\" alt=\"Screen Shot 2021-01-27 at 8 32 54 PM\" src=\"https://user-\""}
{"_id":"doc-en-vscode-067966accdde69a221a242943413f234d83bfe3e59d5b557f5735e20c51b8bde","title":"","text":"I have a setting in my settings. Everytime I reload, I see a setting being . This keeps on happening, the old setting is never removed. ! Not sure if this should be a candidate. does this code look right to you? Or does migration also need to remove the old setting?\nIf you want to remove the old setting you should explicitly mention that in the migration like below\nCan the migration function be made in a way that people do not forget this?"}
{"_id":"doc-en-vscode-9655d798b063d15254843359fdf12a6073b46d207e826689789221ff211b3ba5","title":"","text":"<!-- 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: Relatively niche but: refactor menu (action widget) over a disabled action either arrow keys or typing filter to select an item. that the disabled action becomes highlighted !"}
{"_id":"doc-en-vscode-e8993629810bc8a2c8274bb7c2c70dd95f3a8d69c1581c8f11d46b3aba6aa29f","title":"","text":"Type: <bBug</bI use the shell: When I start VS Code not from the terminal, I see a popup with the error: I know why this issue occurs - it's because VS Code is assuming bash semantics for launching the user's shell in order to solicit environment variables. I encountered the . In that report, I reached out to the xonsh project (xonsh/xonsh) to see if the shell might be able to support bash syntax for this purpose, but after some consideration, they rejected the idea, instead asking editors to honor the shell. Here I'm making the same request to VS Code, namely that if the shell is xonsh (\"xonsh\" appears in the user's shell path), to use a syntax specialized for xonsh to extract the user's environment, namely: If direct support for xonsh can't be , would you consider adding a configuration variable such that a user of xonsh could customize VS Code to honor xonsh as the default shell? VS Code version: Code 1.85.0 (Universal) (, 2023-12-06T18:18:04.614Z) OS version: Darwin arm64 23.1.0 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (7)</summaryExtensionVersion ------ copilot1.141.0 copilot-chat0.11.0 black-formatter2023.6.0 isort2023.10.1 python2023.22.0 vscode-pylance2023.11.10 sublime-keybindings4.0.10 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --\nI acknowledge that starting VSCode from the CLI does work around the issue, but even then only for that launch. If I launch VS Code from the CLI, then it has to restart (such as due to an update), it once again is unable to resolve settings and the error appears.\nI believe this is or ?\n<!-- -96bd-47a8-a0e8- --This feature request is now a candidate for our backlog. The community has 60 days to the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our . Happy Coding!"}
{"_id":"doc-en-vscode-9075f15cf29323428959c8a8a86be535a708f3bfe89d9eb3946fdeb3729ad2ff","title":"","text":"This is a backlog candidate but still PRs are welcome. Here's where explicit xonsh support would need to be :\nthis is being in with minimal testing, could you track any comments/issues with it while I'm out in January? We mainly just need author verification\n<!-- 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!\nVerified by installing and starting insiders from the terminal. I didn't see the error mentioned above. would be good if you'd confirm this.\nI can confirm, with 1.86.0-insider, the error is gone. I was unable to test on the original machine, but I've tested on a new, similarly configured machine (and confirmed that the default shell is configured for xonsh, same as reported above). I'm so delighted that it's fixed and that I was able to help. Thanks for the guidance and support. /verified"}
{"_id":"doc-en-vscode-82aa3309c0bc73041ea29e6c109710b4328562fcc548e9220ef175caefeba3af","title":"","text":"https://user- <img width=\"801\" alt=\"image\" src=\"https://user-\"\nI see the same, but figured it was down to the selected VS Code profile being enabled for that workspace?"}
{"_id":"doc-en-vscode-969ab7edf92a785f27642df945e72f5c4a023ee3fb6a2236e7ee2f894b5f8358","title":"","text":"Testing have a file that is empty run type the file is dirty close the window run !\nThis is tricky: on the main side we open one window as instructed from the command line with the file and we also open another window to restore backups. Since we do not actually know the files to restore on the main side (we just rely on the renderer side to do this), we are opening 2 windows without knowing that the same file ends up being opened 2 times. Imho what should happen is this: if we know that we are restoring empty windows with backups, we just add all the files (as instructed from the command line) to one of those empty windows to avoid that we open multiple windows. This should happen in method ideally. We do the same if we are about to open a window with a folder: all other files to open (or create) end up being opened in that window of the folder.\nI have a PR up for this via though I am not sure this is the best fix :). Basically what it does is to see if upon startup we have windows opening with hot-exit files to restore (either folder or untitled). If we find any such window to open, we open files to open files to create files to diff inside the first of these windows that upon as a matter of restoring hot-exit data. So instead of getting an extra window opened for the files to open, they would open into the first window that is being opened as a matter of hot-exit restore. what do you think?\nI think this is a pretty good fix. It seems to align with how the CLI works when windows are opened as well; instead of opening the files in the last active window, the first window to be restored is selected.\nOk, merged."}
{"_id":"doc-en-vscode-bac13877f68786cbb8ee5f74b4b0009a882116bbc1f1b435b79cc2668a936512","title":"","text":"Type: <bBug</bWelcome - Learn the Fyndamentals Safely browse and edit code Workspace Trust Link 404 - page not found VS Code version: Code 1.91.1 (, 2024-07-09T22:06:49.809Z) OS version: Windows_NT x64 10.0. Modes: Restricted <!-- generated by issue reporter --\ncould you please provide a screenshot of where this broken link is? Thanks!\nGot it - issue is in the walkthrough. Fix incoming. Thanks for signaling this\nIs this a candidate? The change has been merged to the main branch but not the release branch, and so the fix is not in the latest Insiders.\nIMO, it can go with the next one.\n<!-- UNABLETOLOCATECOMMITMESSAGE repo --Issue marked as unreleased but unable to locate closing commit in repo history. If this was closed in a separate repo you can add the label directly, or comment .\n<!-- UNABLETOLOCATECOMMITMESSAGE --Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting , or directly add the label if you know this has already been releaased"}
{"_id":"doc-en-vscode-d3dba2b04f6953aff3bbaf59383d2be216fd774de07e104010fcb93f99bf513e","title":"","text":"<!-- 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.47.0 OS Version: macOS Catalina 10.15.5 Steps to Reproduce: Every time when I click File -New File, vscode always asks to select an Editor, but in the list, there is only one Built-in Text editor. it's just a very annoying unnecessary click. I don't know since when this has been , I believe it's a recent change. Tried to remove all the User settings and start without extensions, didn't help. See the screenshot. <img width=\"1086\" alt=\"Screen Shot 2020-07-12 at 9 35 03 pm\" src=\"https://user-\"<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No Yes\nHi, I would like to work on this issue if no one else is.\nSorry I did't claim before starting, I have fixed it, please correct me if the solution is not ok.\nI removed all the User settings and extensions, useless\nNo worries. Go ahead"}
{"_id":"doc-en-vscode-1a0510cb700aa618e0a0a7b891f50c107a37d41dca829fe4c4b39440d1e23f22","title":"","text":"VS Code Version: 1.60.2 OS Version: Windows 10 Home 20H2 64bit Steps to Reproduce: the VS Code to 1.60.2. the cursor to the training process area, and watch the information. Actually I have completed 2 steps and there are 4 steps, but the information shows that there are 2 steps and I have completed 4 steps. !"}
{"_id":"doc-en-vscode-e3b0976725ad9843216f7f3382a84679d6dd66406418c27cca8db0c72aea7d5b","title":"","text":"Checkout the screen capture below which shows totally broken views. Notice the view title in the bottom panel and the missing icon the secondary sidebar (in my setup the secondary sidebar is left, the primary is right). I suspect this is due to setting/view sync because I have connected a windows VM <img width=\"1494\" alt=\"Screenshot 2024-01-23 at 12 10 56\" src=\"\"\nHave you tried clicking on those broken views and found out what those views are?\nAnalysed the data provided by and this is what happened Windows machine has some obsolete custom view containers state (in pane composite bar) which we are not cleaning up . When sync started, this machine has pushed this state, for eg:Mac machine has accepted this state and started rendering this obsolete view container even though this does not exist. This seems to be a bug in pane composite bar that render view containers - it is rendering obsolete view containers placeholders even though they do not exists in the model.\nverified by code review"}
{"_id":"doc-en-vscode-e66a69b1433c459b9b1df5f2e18b973995382ada184895860c97f882ffae6829","title":"","text":"<!-- 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: --Same issue as , just on a different version. <!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.48 OS Version: Windows 10 <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes Edit Possible reason: In , is missing. imports this script but it is not there. This might explain why the submit action does nothing. Edit 2 Thanks, for the workaround:  it in\n(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.803 --- <!-- score: 0.503 --- <!-- score: 0.499 --- <!-- score: 0.459 --- <!-- score: 0.449 --<!-- potentialduplicatescomment --\nFYI, I was able to get it working by downloading and placing the following file.\nConfirm, an old bug returned.\nWhere to place it?\nNot exactly an old bug. It's more like the devs team forgot to bundle the 1 single script. See my edit of the OP.\nI think the easiest workaround is to install the downgraded VSCode from the following link.\nsame on MacOS. Makes the whole tool useless as you can't click anything than force quit the application.\nlooks like this file needs to be explicitly listed somewhere here to be included in the build (I think the does not exist anymore and can be removed):\nSorry about the breakage. Thanks for narrowing down the issue.\nSteps to verify: Clone cd basic-auth && open code-insiders Settings Proxy http://127.0.0.1:3129 Open developer tools fetch('') or perform any network request play with the auth dialog verify the auth dialog can be opened again once proxy config is changed"}
{"_id":"doc-en-vscode-56f0c166bab049bc4f9a72a7166073a99d6e5fd04fcddbef9664ba3ed3c92984","title":"","text":"On Windows: clone open workspace look at the workspace settings: all files are associated with schema . Note that this is a relative path to the workspace file open both files and check that code completion gives back property . You can also click on the JSON language selector ( next to JSON in the status bar) to see the schema that is associated :bug: No code code completion or schema association\n76 candidate PR:"}
{"_id":"doc-en-vscode-a15446441b01ab719f6a4ed33f43ab48fbf396813d67dc686e087612aea0c24d","title":"","text":"VSCode Version: Code 1.13.1 (, 2017-06-14T18:21:47.485Z) OS Version: Windows_NT ia32 10.0. Extensions: ; Steps to Reproduce: color theme \"Quiet Light\" F something !\nWhat is the expected color? Is the color wrong for the text, the buttons?\nI would expect that the color with the current status gets a little bit more contrast...\nWhat do you mean by 'current status'? The box around the 'case sensitive' button?\nYou actually do not see it, 'cause its contrast is that bad :D ! I see that on a very old monitor, I'm curious it has more contrast than yours. :O\nSame issue here. Confirm that the bug exists. It should be instead of Can I send a PR for this? EDIT - Looking at other light theme it should be more of a red color than a gray one. Example - Light( Visual Studio ) has"}
{"_id":"doc-en-vscode-03ad48957ea842367db6674833931abf75ba0f87e11b2c83bdbfece78186856b","title":"","text":"Testing Scenario: Have a webview editor extension installed that contributes for .txt. Create a new file. Enter something in it so it isn't empty. Save it as What should happen next? Currently, nothing happens. It stays in the default VS Code editor. It might make sense to have the choose editor quick pick open.\nFixing this was more challenging than expected, pushing to November\nIt looks like renaming works and opens in the custom editor per my preferences, but if I save an untitled file as in the issue, nothing happens.\nMarking for April Custom editors use to open a custom editor in place of the default editor. When a untitled editor is saved, is called but this goes directly to which bypasses the . Let me know if there's some other event we can listen to to detect when an untitled editor is saved. I couldn't find anything while debugging through the code\nI guess this needs to be wired in, PR welcome.\nI believe this will also apply to notebooks. I'll let you know what I come up with\nAssigning you since this seems like something we should think about for all editor types, including notebooks\nI discussed this issue a bit with Kai and it doesn't sound like we will be fixing this any time soon. The main drive is for notebooks where you see \"Hey this is a .ipnyb file, install the jupyter extension\" and then the user clicks install but there ipnyb is still plain JSON. The goal for that is to allow rendering of those files without execution if no extension is installed. For the other cases it's not nearly as important as most files have a usable text editor type. We want to reduce the number of notifications as much as possible and switching the file for the user could be extremely jarring.\nSince I just came across the relevant code, we have a way to replace an editor when it is saved (to a different path or when saving untitled): This code does not go through any override but rather takes the typed editor input as it was returned from the implementation. If we were to change that logic, we probably would have to ask method to return an untyped input without override, or at least make sure the text based editors don't set the override.\nI think that there needs to be better UX if we were to implement this as a saveAs causing an editor type switch can be jarring."}
{"_id":"doc-en-vscode-b81a97ef2600e738aa2d3cff91c3a969e44ba2a69c44d105dafb98a7406b7b4b","title":"","text":"I don't love the notification approach but maybe something along those lines. User gets prompted that there is an ew editor type for this resource -user can choose to switch or set automatic switching -editor switches. If automatic switching enabled we no longer prompt and just switch anyways for that resource type\nYup agreed, didn't mean to ask to solve this now, just wanted to keep track of the location in code where this is currently decided\nTo verify: an untitled file it as jupyter notebook should be created your setting to have the entry steps 1 and 2 with a different file name shouldn't switch to a notebook, it should stay as a text\nI tried above steps with the GitHub issue notebook extension instead and when I come to step 5. and save an untitled editor as \"\", that editor actually closes.\nMy settings: My extensions: Video: !"}
{"_id":"doc-en-vscode-0c84edbaeb2e8f321aa4dd6f966cb1a1dd559773fd2f8287ac78d05c6b455595","title":"","text":"Issue Type: <bBug</bThe cursor after pasting, I'd expect it to be at the end of the pasted text: ! VS Code version: Code - Insiders 1.26.0-insider (, 2018-08-02T05:12:16.245Z) OS version: Darwin x64 17.7.0 <details<summarySystem Info</summary </details<details<summaryExtensions (4)</summaryExtensionVersion ------ 999-pack10.12.6 ssh0.0.4 github-issues-prs0.9.0 vscode-open-in-github1.7.0 </details<!-- generated by issue reporter --"}
{"_id":"doc-en-vscode-4850559a9c06b8d87eb29db1b65715e375094346c1f929906d3fe8289829016b","title":"","text":"<!-- 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: Cloud Changes on the button: <img width=\"713\" alt=\"image\" src=\"https://user-\"appears but no changes are made locally at least my change doesn't go away. Logs don't indicate anything interesting\nI encountered this issue myself because I had branches that had the same name locally, but their upstream branches were set differently. My local workaround was to to get Cloud Changes to do the right thing, but the only way I figured this out was by looking at logs. It would be nice for Cloud Changes to at the very least show an error message or something when I click \"Resume Working Changes\" but it intentionally no-ops.\nsorry, misclicked a label"}
{"_id":"doc-en-vscode-4c0479c9d7434cfaebb5d7d0782df895642d1796aa3384c992c69176af06808a","title":"","text":"While verifying I noticed that if I click on the warning I'm not taken to the size limit setting which I would've expected to be taken to. ! Version: 1.68.0-insider (Universal) Commit: Date: 2022-06-02T05:16:30.515Z Electron: 17.4.6 Chromium: 98.0.4758.141 16.13.0 V8: 9.8.177.13-electron.0 OS: Darwin x64 21.5.0 Jupyter Extension version (available under the Extensions sidebar): v2022.5. Python Extension version (available under the Extensions sidebar): v2022.7.\nThis link is specified in core code.\nThe issue doesn't seem to be fixed in the latest insiders. Reopening\nThe issue is now fixed for me in the latest Insiders, at least on Windows 11."}
{"_id":"doc-en-vscode-7236b711cc61dd3ffd1044d448c845aab0ed7ecda3fe9dcaeb05feab2a20ee33","title":"","text":"Type: <bBug from Marketplace which is a packaged version of fsprovider-sample Panel, switch to Output tab and choose Tasks channel. no folder or workspace open, run the command. the \"Workspace folder was undefined\" message. The message come from here: I think the task system is trying to do something (an onFolderOpen task?) for the memfs scheme before the task system for that scheme has been registered. As a minimum change I think the message should become \"Task system for ${} is unavailable\". Better, the message could be suppressed. Best, the sequencing could be revised so the task system registration for the FSP's scheme happens before it is first used. Further observation is that running does not produce the message again. VS Code version: Code 1.82.0 (, 2023-09-06T22:07:07.438Z) OS version: Windows_NT x64 10.0. Modes: <!-- generated by issue reporter --\nNote, this is not a new 1.82 problem. It also happened in 1.81.1.\nI started looking at fixing this, but didn't find a path that calls for any schemes other than and . Should it also be getting called for schemes that s implement?\nThe \"Workspace folder was undefined\" message was introduced by Pinging and about what should happen for a scheme contributed by a FSP.\nScratch that - I believe I have answered my own question in the PR I just submitted."}
{"_id":"doc-en-vscode-d667caaad0ff8df8692f4e85c55051902a21ad011224e0a768ba1edf17bef10e","title":"","text":"Does this issue occur when all extensions are disabled?: I dont know VS Code Version: 1.88.0-insider OS Version: Windows 10 - 10.0. Build Steps to Reproduce: Start debugging python script. It creates a new \"debugging terminal\". This should work stop debugging debugging. If you look at the debugging terminal, you will see a input (generated by VS Code) then command for debugging the selected file. path of the is somehow truncated, hence cannot find the file. debugging is however starting: you will be prompted with the message: Timed out waiting for launcher to connect. As seen on the gif below: Path 1st time: (Correct path) Path 2nd time: (truncated path) !\nI'm getting similar behaviour when using Git Bash as default profile. First time debugging the Python Debug Console opens and the application runs without issue: the subsequent times I sometimes get: ... which does in fact executes the code, but then I also sometimes get: I don't know what the call to comes from (possible the end of the directory name, but in in the last instance is not called. This inevitable gives this error. ! Which then starts a new Python Debug Console. Similar to what is above. I don't see this behaviour when using PowerShell or Cmd. IMO There's some weird truncation happening. Version: 1.88.0 (user setup) Commit: Date: 2024-04-03T13:26:18.741Z 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.\nThank you for adding details! This is the exact same problem that I experience: I didn't try with another terminal (Powershell or Cmd). I will see if that can fix my problem temporary using .\nAs mentionned by This issue is not here using . However, this is still adding extra command that could be the explanation behind it: ! The first run it is only using: On the second run, it : before the command."}
{"_id":"doc-en-vscode-0a168954dab5202de393bcc4d59348e5ca0e9b6ccc1fcfba05ff514b6a17053b","title":"","text":"There is still the before this line though (2nd blank line)\nI am seeing the problem when I set my default terminal profile to any of the following and run my debug launch script twice. Each shell will fail on the second launch with the same mangled command line. bash command prompt powershell Work around: revert back to vs code 1.87.\nI am having a similar problem launching Python from VS.Code with or without debugging (both cmd and wt as terminal.external.windowsExec). If the path to the Python executable contains space as in default I end up with and an error message in the launched terminal window: Yet this works fine if I pick a Python interpreter from venv or somewhere else such that there is no space in path e.g. Curiously - the internal terminal and internal console work with either path\nit seems sending the ctrl+c in a separate is not sufficient -- any suggestions?\nIf you want to execute something again we have a helper on the render process side , this conditionally sends a ^C and may wait for a shell integration prompt. That might work?\nIt looks like that does the same thing with a 100ms delay. I'll adopt the delay as well, see if that fixes it\nplease could you confirm when this will be released? It doesn't seem to have gone out in the latest April release. I've tried the insiders version and can't debug anything so it's even worse.\nThis is available on Insiders. Please open another issue with the details for not being able to debug anything; that's probably not related to this fix...\nCan any of you verify that this is fixed in the newest version of VS Code Insiders? Thanks!\n<!-- 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!\nThe external terminal launch is working with space in pythonInterpreter path () using both and as Windows Terminal in current: 1.89.1 and insiders 1.90.0 /verified\nRunning on version 1.90.0 I can not longer observe the truncation."}
{"_id":"doc-en-vscode-ee25859906b0305f2b1638862ecf75fe5a5d9b777914695cfb793e21607e53a8","title":"","text":"The execution command looks intact even after multiple runs. ! There's an extraneous whenever you start a run but I guess that's intentional.\nI am experiencing this issue using Python Debugger: Current File with Arguments. I am using ver VSCode ver 1.9"}
{"_id":"doc-en-vscode-e503d5e0222590a9e8dad681fd06f799478511632246100949bfc9cbc0786d43","title":"","text":"Summary: The sign-in link for Github in VSCode running through serve-web rotates ports in the 54xxx range, breaking any pre-set port forwarding for users connecting via SSH. This occurs regardless of any port option set with --port (taken from my comment in ) Does this issue occur when all extensions are disabled?: Yes VS Code Version: Insiders 1.82.0 OS Version: Mac OS 13.3 Steps to Reproduce: to the device hosting code via SSH, with local port forwarding for port 8000 enabled the remote device, launch serve-web with a browser window and navigate to the URL given by serve-web on settings sync, showing a github sign-in URL. Note the port is different than the default, requiring you to reconnect and add a new forwarded port Expected behavior: Setting the port with --port should (a) also determine the port used for sign-in, or (b) be a separate option so that SSH port forwarding does not require updating SSH config and reconnecting each time you need to sign in\nis the github sign-in URL in step 4 coming from you?\nThis flow shouldn't actually happen in the remote case and instead the user should get the device code flow. Fixed this by disabling the local server flow in\nVerification: turn on Settings Sync using GitHub when you go through the auth flow, you should get the Device Code Flow first"}
{"_id":"doc-en-vscode-ad6278848028642ea5c3a2ea0cf97e65da9d11f412755ba02b539b799cbcc545","title":"","text":"Testing This is sort of unrelated to the TPI, but when I inspect context keys on my terminal area, I notice that it has , even when the active terminal isn't using git bash. Here are my repro steps (not sure if this can be simplified): a terminal profile using an extension and launch the extension. git bash, then close it and open the extension-provided terminal profile. context keys on the extension-provided terminal instance. :bug:\nI would like to solve this problem, if it is still an issue. Do you mind if I start?\nsure!\nAfter scanning some source, there seems no good way to solve this. Because is no way for extension to specify terminal type when (AFAIK) extension register a terminal profile ( ), and Windows, shell type is determined by some heuristic logic, based on executable string, and default to return . (For WSL, the shell type is always \"undefined\" in my quick experiment.) When terminal service try to update context key, it fallback to NOP if the shell type is , that's the behavior noticed at first place. See: For this issue to be solved, probably there should be a way for builtin terminal profile to specify shell type (so it works for all bultin profile in all platform), and for extension provided terminal profiles, maybe we can add more optional fields to or method to . As for the wierd behavior noticed currently, maybe we can set to \"unknown\", to make this state less confusing. But since that this behavior is already state in , I wonder this can be changed.\nI think the problem is here: It should check if first, then set it even if it's undefined if\ndo you want to submit a PR since you investigated and found the problem?\nYes, I can submit a PR for this. But, before doing this, I need to confirm some detail. The current behavior is From A. If new terminal instance is created, and shell type of the new terminal istance is defined, update From B. If active terminal instance change, and shell type of the new terminal istance is defined, update C. If there is no terminal instance, reset D. otherwise, do nothing so the editor keeps last known when shell type is undefined during new terminal creation or active terminal change. If so, what value should be set on this case? should we set it to or just call ?"}
{"_id":"doc-en-vscode-7448e191a84532c3bcba858bfb203d8ba9f454445a1a5b7fd795c05ee0ef86ad","title":"","text":"like Can you provide the extension that open extension-provided terminal and trigger this issue?\nSome commits about the comment/design history of this context key"}
{"_id":"doc-en-vscode-1fdbe27551eff97d1cd18f62f95e051f0f1cdfa08c40d78861b04926e3c2eaa4","title":"","text":"<!-- 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"}
{"_id":"doc-en-vscode-ffbd48af4e4c205220d15f0d26aacbd9cabdb53bb145accc919803891de17d42","title":"","text":"<!-- 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. !\nTo 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"}
{"_id":"doc-en-vscode-c6a90c650c71c8e900d114c6440efba91fcc643c40431b3cd6ff2b32647d06a8","title":"","text":"<!-- 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\nI 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?\nWhat 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?\nI 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).\nAnother 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.\nI 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\nQuick pick is removed and by default we show the contents view now."}
{"_id":"doc-en-vscode-2753d3d14807d054db698c6902a0900ff7cfd77b599b533c8acb315ab4dd137b","title":"","text":"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. !\nThis 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?\nthis 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?\nHello, 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\nthanks 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.\nCould just be in the default setting for ?"}
{"_id":"doc-en-vscode-28f5b35c241c86f8149c78399570bab5d8b207fd5ae0e02e19da15e95e16a913","title":"","text":"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\nthe 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.\nOk, 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"}
{"_id":"doc-en-vscode-299961525cb9282b2805ea2a45bc8f02e761644dbba0da334ad5b12e7372538d","title":"","text":"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."}
{"_id":"doc-en-vscode-e4653cfb3d292a5c98435668f114d057560731bd12632b0146b36b1e2033bda1","title":"","text":"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."}
{"_id":"doc-en-vscode-285f682800f2eb27763438365f41b19042ce6c7f0d25caf448335fe92f3821f3","title":"","text":"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 --\nI 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? ! !\nhere's where is returned\nthis is a breaking issue for screen reader users. Any thoughts would be appreciated."}
{"_id":"doc-en-vscode-5ca78c21740cd24ff87b684ec98f0a259b77922a836d08daacf7c97686c2ecbb","title":"","text":"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.\n, looking into this :)"}
{"_id":"doc-en-vscode-56c7cda0c048a2c6c40379bbb0134f1d24d277df130f4183c354f10accefba25","title":"","text":"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<!-- generated by issue reporter --\nSeems NPM org is taken by someone :( I'm now forking mocha to update to fix security alert Wondering what I should do :one: Publish it under :two: Make depends on octref/mocha on GitHub :three: We should create a NPM org for these kind of packages What do you think?\ncan't we just update to mocha 5 or 6 in the vscode module?\nwill talk to you in chat\nAh, I thought Mocha 5/6 would have breaking changes so we can't really upgrade easily. Turns out Mocha 5 only had : Drop IE9/10 support. It shouldn't affect us. Meanwhile if someone really needs Mocha 4. He can use and manually depends on it. Will upgrade to Mocha 5.\nThanks"}
{"_id":"doc-en-vscode-4944307aa6feb5077c21296d9a96270428e18dd3529c13502b997f7923a53677","title":"","text":"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\n/verified It prefers the user name over comment now."}
{"_id":"doc-en-vscode-06531e7ca3b638e0edba022da8fb6eb2dc8cedd6e09ec6d0d2b9d2adcc8ea8e3","title":"","text":"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 --\nAssigning 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"}
{"_id":"doc-en-vscode-0e759eb404a0fce577633863a1764c6fc5f856653a390101d66355eefd44c377","title":"","text":"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.\nVerified 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-\"\nwho should add the built-in command?"}
{"_id":"doc-en-vscode-193581ee44dd55f9d7993319ed57aae1695b5e72bb475a9a8e8f3d01ec5c7c35","title":"","text":"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 --\nCode pointer\ndoes it mean that this is the expected behavior?\nI m on it.\nit 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.\nit does not seem to restore the full expansion state, only the first level is that true?\nyes, only the first level. could improve the PR and try to restore more.\nYes, i can do that.\ngreat, tree should have api to get the exapnsion state. And once the pr is ready just ping me on it.\nShould i make a new method to return all the expanded children as array on treeModel?\nIs this ready for verification?\nben already verified and can add a verified label. There are some limitation which will tackle in a pr for next milestone"}
{"_id":"doc-en-vscode-1aa69f1ee389f32a77767e72117c119bf43b69b5510c72d2eb25d5416ea11497","title":"","text":"<!-- 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.\nCan you see if is assigned as keybinding? I assume this goes through our global window close handler that has not yet adopted aux windows.\nI have default keybindings { \"key\": \"alt+f4\", \"command\": \"\" },"}
{"_id":"doc-en-vscode-dab2990d66b60010d97127afaa62cab7cf1d1596aff64418d5b0132ef0acee6d","title":"","text":"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.\n/verified"}
{"_id":"doc-en-vscode-59aafdee5f23c1f1c845462efb1645a8c0eb25403af970fc98a0d78ad4915302","title":"","text":"When I run all tests, the label resets back to after all tests were run. This is very confusing. !\nThis 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."}
{"_id":"doc-en-vscode-93a58c53578167af594e6993298696fb8c272552aef29c0c03c7303e7ff0b49f","title":"","text":"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 --\ncc\nI just checked our telemetry for the most popular combinations of VS Code version and Vue extension version and here's what I see."}
{"_id":"doc-en-vscode-a7ba7f545017bff805fb17be46e7ea174b48cb76b551cbce7be699017a0be9ff","title":"","text":"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 !\nUpdate is not detected automatically. It is detected only when user is searching for the extension.\nSorry about this inconvenience caused. Fixed it - We will now detect the update automatically.\n<!-- 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!\nI just tested it and confirmed it's fixed in the latest insiders version, thanks a lot!\nAdding label based on above comment"}
{"_id":"doc-en-vscode-ddac83ff0f4af7e612370606dcc7b3e8ad1ca3e2e89b682885ef5696225615ef","title":"","text":"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)."}
{"_id":"doc-en-vscode-c10998ad7fd410fe7d72939e335858b122765cdc7e8ec05096c96876270f01e8","title":"","text":"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-)\nWould you mind sharing your Remote SSH logs as well? And if you have any gifs or videos of what you're seeing?\n! ! 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...\nYour 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\nThis 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.\nSame issue happends to me.\nI 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.\nCan you please try our latest insiders and see if you can reproduce this issue still?\nThis issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!\nSorry, 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.\nWere you using any remote set up when this happened again? Are you still able to repro it?\nYeah, it's exactly the same setup, just updated (yesterday's) insider build."}
{"_id":"doc-en-vscode-ae46cead928dc80a5fca644286910b1fc4e2bb8ce8e379fb4a9ced79ad034f12","title":"","text":"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.\nSorry 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?\nSo, 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.\nThanks 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"}
{"_id":"doc-en-vscode-2148931527d2b3e8719e0a42da40240e2f542a5ce321c23410e5ae59cda8dd8b","title":"","text":"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 --\nJust 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)\nFunny enough - clicking on the \"Discard All Changes\" icon reports the correct number of files (2 files in the scenario above).\nI 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\n1 sounds great!"}
{"_id":"doc-en-vscode-8e8a23e279cdaec001d22e1bb718bb3197cb23ec78438e4c4f6c80b3d3c799a9","title":"","text":"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.\nThis 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!\nI think the ask here is that we improve our handler to display the call stack of the unhandled error...\nYeah, I got that. I have for that (thanks to"}
{"_id":"doc-en-vscode-3fde077fbe2a28f9f6b15e860d54b9e0e7e45362924fac3212c8828f73f99fc0","title":"","text":"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\n(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 --\nOh yeah. Good catch. Want to submit a fix? Problem is\nHey, I am a new contributor here. I want to give a try on this issue.\nGreat. Go ahead."}
{"_id":"doc-en-vscode-6c885d6767e8766bffa9b0c62cb256f38d0cc9e844e489f771d4f2f91cc5b721","title":"","text":"<!-- 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:"}
{"_id":"doc-en-vscode-9fed7581ad6a414a2775dc3f1d08d2f5b4dfc0af6a83248dc2d33bd67bc2d8ca","title":"","text":"sure the File Explorer is visible temporary profile window Welcome editor fails to open. cc\nDue to:\nand I also reproduced this when testing out her walkthrough changes:"}
{"_id":"doc-en-vscode-aa95c725e23eaf4365ca89e27a4fd9a25a54508c5cc0cec8e5c16ce2e48811d5","title":"","text":"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:\nI'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:\nSame 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.\ncould 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!\nTested with OpenVSCode-server insiders, which is rebased on top of commit (\"Sanity Bounds for \"window.zoomLevel\" ( ()\") [1]. The issue still exists."}
{"_id":"doc-en-vscode-cd78deef3e34c3821294391bdb490779a11c6437e5b9f933a0e13b384db02d67","title":"","text":"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]:\nif 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!\nThank 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]\nthanks 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?\nYes. 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."}
{"_id":"doc-en-vscode-8dbb775bb7741a7bb70893f1995b9a8320738779d73044ebdb240b4bd63fb04f","title":"","text":"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,"}
{"_id":"doc-en-vscode-f67f145033d780dab774652c6a041b46194c296f2bf5c1e3748762b1e1c88eaf","title":"","text":"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."}
{"_id":"doc-en-vscode-0c1ea59935426ffe253e585ef75e7b4591f7495a6a6906c8a4fa9f488374b206","title":"","text":"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."}
{"_id":"doc-en-vscode-78e17bce41dee5c3b81d0410f2ecbc6c68b548b741e595b6ed2f716aadcc1afc","title":"","text":"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"}
{"_id":"doc-en-vscode-11d52f54d243a5d9a68a23db0a2bc53f4c8b9280b1585c86dda390644c9633c7","title":"","text":"<!-- 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.52.1 OS Version: Windows 10 1909 Steps to Reproduce: then press to run extension any folder with some code. 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?\nI believe this is expected behavior, however forwarding to so he can close\nYes. what tooltip to you expect when hovering over a code lens?\nAs , show maybe suitable I think.\nAh, I see. That actually makes sense and would be a simple change\nCan I take a look at this issue and try to work on this?\nThis is where the dom-nodes for codelens are created: Using the title attribute on them should do the job\nIs the native tooltip sufficient for the fix? Windows & MacOS :-------------------------: <img src=\"https://user-\" width=\"400\"Windows | MacOS :-------------------------:|:-------------------------: <img src=\"https://user-\" width=\"400\"| <img src=\"https://user-\" width=\"400\""}
{"_id":"doc-en-vscode-7fd0f2313d1d0c61c4912928ed15a9b046a64574a6822ff0f6da92145b8fd001","title":"","text":"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:"}
{"_id":"doc-en-vscode-00580e244a13ee47f1b9bf4d4e53481522ed7709f69d0d11e7357f6403ee8be3","title":"","text":"]- 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. !\nVerified 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=\"\"\nThe 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."}
{"_id":"doc-en-vscode-4c7176d776dec2a5a4086051ceebf55528ace476ec6785dd5dd5abd3a4d8f690","title":"","text":"! 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.\nHi - 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.\nJust realized this is a regression from previously stable.\nNOT Resolved in the latest stable version of code.\nNot 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.\nAfter 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.\nHi, this is still not resolved after today's release to Version: 1.67.1 Below my current version details.\ncan you try again on VS Code Insiders? Otherwise, you'll have to wait for version 1.68.\nGreat its working in the Insider version. Thanks."}
{"_id":"doc-en-vscode-6ceec1010dc22af9c170a3ec845a2dd6199f44b76ddc988b5947196501c36fbc","title":"","text":"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 --\nwhich 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).\nThe npm install task is the one in\nSorry, seemed to close the issue by mistake while trying to paste a snippet from { \"type\": \"npm\", \"script\": \"install\", \"problemMatcher\": [] }\nAnd this is in \"scripts\": { \"test\": \"echo \"Error: no test specified\" && exit 1\", \"random\": \"do something else\" },\nThank 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?\nI just thought it should do similar to the scripts in the and show the script field?\nI see, so it should just show \"install\" as the detail.\nUpcoming behavior: !"}
{"_id":"doc-en-vscode-b988c13716b28c21ccf84c63dff98413c5e07f9780026a2dd9bbd345ec7a2ebb","title":"","text":"<!-- 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 !\nSorry can you clarify what you mean?\nAs, 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.\nI see space between the badge and the active indicator,\nI think it's too small.\nI 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.\nShould be fixed now thanks to <img width=\"127\" src=\"https://user-\""}
{"_id":"doc-en-vscode-578db502bf20f19bbe3c5766f7bad010f094a7a275b05398bc5c6bd57ad3db47","title":"","text":"I would expect a \"...\" overflow behaviour here: !\nFixed in , please review"}
{"_id":"doc-en-vscode-9631f8492b6048a8f350d19b5b6ac991b790708e654b9c34f9a95674c1dfed87","title":"","text":"<img width=\"584\" alt=\"image\" src=\"https://user-\"//cc for views\nI assume this is nothing to do with the views instead its about how entires are rendered in list/tree. CC\nTree row contents are outside of the tree's jurisdiction, but are in fact responsibility of the widget user.\nTimeline doesn't use the extension tree view and instead does it's own thing. I think works on timeline.\ncurious, do we have an understanding what caused this? it seems relatively recent?\nMight be related to . any ideas here?\nIt 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-\"\nit 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.\n<!-- UNABLETOLOCATECOMMITMESSAGE issue --Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting , or directly add the label if you know this has already been releaased"}
{"_id":"doc-en-vscode-cd9e4a0b652be0012e185804ca28629bd6d5e5b757a99eeaa6e97c50699d5b1e","title":"","text":"VSCode Version: 1.2.0 OS Version: all Steps to Reproduce: from the command palette while not debugging a error: !"}
{"_id":"doc-en-vscode-c3e235cc49f4c910cda7e51c185dbc49ac2ccfdb3f9e4f3236a044db65d711f6","title":"","text":"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.\nPR welcome.\nCan anyone explain a bit about it ? Thanks"}
{"_id":"doc-en-vscode-b71944add8c13263974a0fa587438f74af68a0b44ef201e34f3012e2c9d18d37","title":"","text":"<!-- 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.\nThanks 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 !\nIt looks like I was missing sending an so the same debug session was being reused after restart.\nI 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.\nSimply 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.\ndid you verify that this works with the latest VS Code insiders as expected?"}
{"_id":"doc-en-vscode-5c86805aace2f1985bf481d6fb3424d43cff626084bd7c92abae32d844403df2","title":"","text":"<!-- 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. --"}
{"_id":"doc-en-vscode-cc61cc93b01329e54f94a5c0238790dcea4fc17c37138ac2ee7cf9745289697e","title":"","text":"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\nThe 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-\"\nI upgraded to node-pty which may improve the problem, if not I'd guess this is related towinpty is not terminating the processes correctly.\nI retested this and it is still happening under Insider today.\nterminalProcess stalls on this native call: , meaning this function never returns Not sure why a or native exception isn't happening.\nThis has the same root cause as\nMoving to September as this is a more involved change than I anticipated. More testing in Insiders would be ideal.\nany news on this. Do I need to adopt something here ?\nNo progress, I moved this to September before I knew that I would be out for 2 weeks in September.\nIt does look like it affects Windows only.\nHmm, 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 .\nWas this never solved?"}
{"_id":"doc-en-vscode-5ffd3ff9469f7ccfe06b85d7dc8ea37c1b4a46885ba771272aaab090b0012bbd","title":"","text":"when I last tested this I had the impression that this is still a bug and the terminal hangs (doesn't signal on exit).\nYes, this is still an issue.\nIs this in line to be fixed btw?\nThis 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.\ndoes this sound like something that will be fixed by conpty?\nit 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.\nThere'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.`"}
{"_id":"doc-en-vscode-15f1f091dd307b09c7941055e9f5af50df50cc953b4d0f80c5c011de60976025","title":"","text":"<!-- 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."}
{"_id":"doc-en-vscode-cdeff085f70ba84f5274a6c79200a628b4e3791ce09f33709e29f5c9a9ea0a77","title":"","text":"<!-- 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 !\nThat looks grid related to me.\nWeb 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.\nfyi, not sure if anything within the keybindings editor could have caused this other than adopting the table widget.\nCan also be reproduced by focusing the search input and then tabbing until the table is focused Created a PR fixing this.\nTagged 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"}
{"_id":"doc-en-vscode-520ff015a9d9f860089bc7cb7cfc85f1c4ef3d3b0d77502017427c752df5106f","title":"","text":"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\nAssigning 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.\ncan 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\nI just ran that, and yes I get\nverification: this: vscode insiders in to an account/open the account menu It shouldn't throw the error above."}
{"_id":"doc-en-vscode-4fd92faaa9141c81aef61f3fb4cf1cb8de4a6658377a5c4f5ceb15dd150fd56f","title":"","text":"<!-- 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\nI have a feeling we've seen this before?\nyes I remember something was not right with our argv lib (minimist?) with regards to handling numbers?\nHi, 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"}
{"_id":"doc-en-vscode-b430f59e151b94bedd9d0b54bacb10db3979df1244b919573fcd587ba07a1e48","title":"","text":"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-\""}
{"_id":"doc-en-vscode-15a6f6f1bacc36caf041a44ecb9d89d82890060088a1dfb15dfe71f52e6e6029","title":"","text":"I'm seeing the following message in Insiders: The setting is also not in the user tab of the Settings editor with profiles enabled.\nFixed in commit, github just didn't close this issue :("}
{"_id":"doc-en-vscode-e8e68a90dbad30364b12beb2328ad296c16f1040f036801bc4afba016d6ec6e9","title":"","text":"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\nimpacts microsoft/vscode-jupyter since we're not getting the correct suggestion\nI think this is a regression. please could you verify this works as expected in stable.\nyes, the kernelspec updates in stable as expected\nThis is actually a bug in the new metadata API. Transferring to vscode core.\nThis 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.\nOh my bad... this was released already in ... My mistake.\nBut 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 ?\nI 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\nThanks!"}
{"_id":"doc-en-vscode-ab6599d21cf1f4411f3dbfa510cabfbed67c923393419cd66a039033d60b9a78","title":"","text":"<!-- 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. !"}
{"_id":"doc-en-vscode-f67a6af4836e3c26bdb5df175aa4108d0bc6c9e324b0f98e309ef88e3bb5407b","title":"","text":"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.\nI 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. : )\nYes, PR is welcome!"}
{"_id":"doc-en-vscode-8393a643afe4021ea87478f96de36c7c367e0f14caa1916d9dcac54de6e90769","title":"","text":"<!-- 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 )"}
{"_id":"doc-en-vscode-3a54e7d0b1412298527f40d337670b825ff172b65118653bfd7370cb35b29fa5","title":"","text":"<!-- 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.\ncan I work on this issue?\nAre you able to locate where that text is coming from?\nbeen searching the text source for some time but not able to find it. Did you find anything?"}
{"_id":"doc-en-vscode-d773b09bc5d54331112baf5967fb18b0fd15003ace5d0c5fbbad4228c7bf5f4c","title":"","text":"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.\nI was just searching some beginner friendly issue to solve to start my open source journey."}