jiebi/CodeConvo huggingface dataset:
Also there is , but I suspect the issue on MacOS is different. Jae
The bottom line: Only while using Workspaces, the first or default terminal is properly run in WSL2. However, any subsequent new terminals are being recognized as a Windows environment, not Linux. Somehow the combination of Workspace+WSL is messing up the terminal environment.
I just discovered there is a command called "Create new Integrated terminal (In Active Workspace)"; where as the default "New Terminal" calls "Create new Integrated terminal". This is another possible workaround. However, you have to make sure the active file is where you want the new terminal to be created. You lose the ability to select which folder to create the new terminal in, unfortunately.
Can repro: ! multi-root workspace in WSL +shift+ +shift+5
Ah this is happening because we're getting a instead of a here:
I'm also getting this issue when using inherited for workspaces and remote ssh from a windows to a linux host. If I reload the window I am able to split the terminal for terminals that were created before the reload. Version: 1.58.2 (system setup) Commit: Date: 2021-07-14T22:10:15.214Z Electron: 12.0.13 Chrome: 89.0.4389.128 14.16.0 V8: 8.9.255.25-electron.0 OS: Windows_NT x64 10.0.
Same here.
As a workaround for this issue in version 1.58, I was using this setting: But now in version 1.59.0, the issue happens with any values .
Awesome! Just got the fix in insiders! Thank you!
Verified fixed in
<!-- 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.75.0 (Universal) Commit: Date: 2023-02-01T15:24:42.903Z Electron: 19.1.9 Chromium: 102.0.5005.194 16.14.2 V8: 10.2.154.23-electron.0 OS: Darwin arm64 22.3.0 Sandboxed: No Steps to Reproduce: SCM tab at the left side at the border of the Commit & Push combo box The inconsistency is more visible in non-default themes like "Bearded Theme Monokai Reversed" <img width="717" alt="vscodescmcp1" src="https://user-"but also slightly in the "Default Dark+ Experimental" for example <img width="656" alt="vscodescmcp2" src="https://user-"
Type: <bBug</bCC (alt+F9) does not stop at the last comment. It cycles back to the first comment once it reaches the end. This is especially confusing for screen reader users because pressing alt+F9 multiple times does not always guarantee the last comment position. Please make stop at the last comment position. Of course, (alt+shift+F9) has the same issue. ! VS Code version: Code - Insiders 1.93.0-insider (, 2024-08-20T08:04:15.567Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (128)</summaryExtensionVersion ------ vscode-openapi4.28.1 zotenote1.0.1 android-dev-ext1.4.0 aiprm-lang0.0.2 Bookmarks13.5.0 openscad1.2.2 spellright3.0.136 zoterolatex0.4.1 mermaid-markdown-syntax-highlighting1.6.0 external-pdf1.2.0 doxdocgen1.4.0 vscode-markdownlint0.53.0 vscode-eslint3.0.10 vscode-quick-select0.2.9 vscode-deno3.38.2 gitlens14.6.1 EditorConfig0.16.4 prettier-vscode10.1.0 figma-vscode-extension0.3.5 vscode-firefox-debug2.9.10 shell-format7.2.5 vscode-google-translate1.4.13 codespaces1.17.2 copilot1.223.1058 copilot-chat0.20. remotehub0.62.0 vscode-github-actions0.26.2 vscode-pull-request-github0.95.
cloudcode2.16.4 overleaf-workshop0.13.2 cslpreview0.2.2 path-autocomplete1.25.0 latex-workshop10.1.0 lilypond-syntax0.1.1 scheme0.2.0 better-cpp-syntax1.17.2 commitlint2.6.0 language-julia1.109.1 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 language-matlab1.2.5 zotero0.1.11 git-graph1.30.0 azure-dev0.8.3 vscode-azureappservice0.25.2 vscode-azurecontainerapps0.6.1 vscode-azurefunctions1.15.2 vscode-azureresourcegroups0.8.3 vscode-azurestaticwebapps0.12.2 vscode-azurestorage0.16.0 vscode-azurevirtualmachines0.6.5 vscode-cosmosdb0.22.0 vscode-docker1.29.2 vscode-edge-devtools2.1.5 black-formatter2024.3. debugpy2024.11. flake82023.13. isort2023.13. python2024.13. vscode-pylance2024.8.101 jupyter2024.8. jupyter-keymap1.1.2 jupyter-renderers1.0.19 vscode-jupyter-cell-tags0.1.8 vscode-jupyter-slideshow0.1.5 remote-containers0.381.0 remote-ssh0.114. remote-ssh-edit0.86.0 remote-wsl0.81.8 vscode-remote-extensionpack0.25.0 azure-account0.12.0 azure-repos0.38.0 cmake-tools1.18.44 cpptools1.21.6 cpptools-extension-pack1.3.0 js-debug-nightly2024.8.1517 powershell2024.3.2 remote-explorer0.5. remote-repositories0.40.0 remote-server1.6.
vscode-github-issue-notebooks0.0.130 vscode-node-azure-pack1.2.0 vscode-selfhost-test-provider0.3.25 vscode-serial-monitor0.12.0 vscode-speech0.10.0 vscode-speech-language-pack-en-ca0.4.0 vscode-speech-language-pack-en-gb0.4.0 vscode-speech-language-pack-ko-kr0.4.0 vsliveshare1.0.5936 windows-ai-studio0.4.0 autodocstring0.6.1 pandocciter0.10.4 publisher1.1.5 shiny1.0.0 shinyuieditor0.5.0 quarto1.114.0 r-debugger0.5.4 java1.33.0 vscode-xml0.27.1 vscode-yaml1.14.0 r2.8.4 multi-command1.6.0 AudioQ0.0.2 vscode-deepl1.1.1 abc-music0.4.0 lua3.10.5 latex-utilities0.4.14 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-conventional-commits1.25.0 vscode-arduino0.7.0 vscode-gradle3.16.4 vscode-java-debug0.58.0 vscode-java-dependency0.24.0 vscode-java-pack0.29.0 vscode-java-test0.42.0 vscode-maven0.44.0 zotero-cite0.8.6 markdown-all-in-one3.6.2 grammarly0.25.0 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
i'm wondering if we were to announce "comment 1 of 3, 2 of 3, 3 of 3" etc., that would be a sufficient workaround?
-- Adding the index number would be really helpful! However, that is a separate feature enhancement and I would prefer not to wrap once it reaches the end. At least, a simple bell sound needs to be played when it wraps.
Steps: begin with multi tabs showing open an editor hide tab bar actions move to the top close editor open same editor actions are not visible anymore, there is just a "..." <img width="1348" alt="image" src=""
When creating the editor actions we rely on the event to tell us when actions change. However, this event is not set when there is no active pane. In that case we should have a different event trigger the onDidChange event such as onDidChangeActiveEditor for example
<!-- 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.69.0-insider OS Version: Windows 10 Steps to Reproduce: Two split terminals + one standalone terminal, select them all then join. !
this works now, must've been fixed
I tried it in the latest insider build, still fails. Instead of selecting the terminal tabs one by one, can you try to select all, then join them? If you can reproduce, please reopen it.
(originally reported in ) Extensions that are enabled both in the show the text . This text can be confusing. asked me to open an issue Te proposal is thus to remove the text. To be honest though, I am unsure what the text even means. Look at this image: ! That extension is clearly installed locally. But I do not find it installed in on the remote. It is not there in the remote part of the Extensions sidebar. VS Code version: Code 1.88.1 (, 2024-04-10T17:41:02.734Z) OS version: WindowsNT x64 10.0.
Modes: Remote OS version: Linux x64 5.4.0-177-generic <details<summarySystem Info</summary </details<details<summaryExtensions (40)</summaryExtensionVersion ------ yang0.1.3 jupyter-keymap1.1.2 remote-containers0.354.0 remote-ssh0.110.1 remote-ssh-edit0.86.0 remote-wsl0.88.0 vscode-remote-extensionpack0.25.0 remote-explorer0.4.3 remote-server1.5.1 vscode-openapi4.25.3 lit-html1.11.1 markdown-preview-github-styles2.0.4 vscode-fish1.0.38 ruff2024.20.0 vale-vscode0.19.0 vscode-markdownlint0.55.0 vscode-eslint2.4.4 gitlens14.9.1 prettier-vscode10.4.0 code-runner0.12.2 go0.41.4 path-autocomplete1.25.0 restructuredtext190.3.0 vscode-azureresourcegroups0.8.6 vscode-cosmosdb0.21.0 vscode-docker1.29.0 vscode-kubernetes-tools1.3.16 debugpy2024.4.0 python2024.4.1 vscode-pylance2024.4.1 azure-account0.11.6 vscode-thunder-client2.21.15 vscode-yaml1.14.0 vscode-direnv0.0.2 code-spell-checker3.0.1 vscode-stylelint1.4.0 even-better-toml0.19.2 shellcheck0.37.1 simple-rst1.5.4 vscode-proto30.5.5 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Type: <bBug</bIt's a UI fault in the merge editor. I have written the steps to reproduce it and also attached a screen recording for better understanding. Note: What I mean by , and in this issue ! First things first i) Need a code base which have conflicts You can clone this repository with both & branches and merge branch into to produce merge conflict. ii) Open the conflicted file in the Merge Editor And then: (Please watch the video for better understanding) in the Result tab, place the conflicted code block's widget aligned with 'Complete Merge' button in bottom-right corner in a way that the conflict actions bar is intersecting with the button (as shown in the video below). code from any stream, incoming or current doesn't matter. try to hover over same straight horizontal line as conflict actions bar towards the 'Complete Merge' button, You will notice that the cursor does not become a pointer, and you cannot even click the button. Now, If you reload the window, the issue will be fixed. However, as soon as you select any action from the actions bar, such as 'remove incoming/current', the issue will occur again. From my understanding, what is happening here is that after we select any action from the actions bar, the actions bar is overlapping the 'Complete Merge' button in the z-index's stacking context. I have tried to fix this on my local setup, and I believe I have solved the issue. If the maintainers want, I can raise a PR! VS Code version: Code 1.78.2 (, 2023-05-10T14:39:26.248Z) OS version: WindowsNT x64 10.0.
Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<details<summaryExtensions (26)</summaryExtensionVersion ------ vscode-tailwindcss0.9.11 vscode-eslint2.4.0 docs-markdown1.0.1 docs-preview1.0.1 es7-react-js-snippets4.4.3 auto-rename-tag0.1.10 live-sass6.0.5 githd2.3.3 vscode-text-pastry1.3.1 vscode-peacock4.2.2 vscode-selfhost-test-provider0.3.15 material-icon-theme4.28.0 vscode-react-refactor1.1.3 prisma4.15.0 vscode-thunder-client2.7.5 reactree1.0.8 LiveServer5.7.9 mongo-snippets-for-node-js1.3.12 svg-preview2.8.3 vscode-fileutils3.10.1 vscode-wakatime24.0.11 console-ninja0.0.141 vscode-import-cost3.3.0 JavaScriptSnippets1.8.0 pretty-ts-errors0.4.1 html-css-class-completion1.20.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Thanks for this detailed bug report! That would be awesome!
Hey I have raised the PR
Was verifying an issue Disabled settings sync Reenabled it but on the Stable service Changed profiles a few times Disabled Settings sync Got an error poupup, here is the stack from the window log
Do you have settings sync views enabled?
Turn on Settings Sync Open Synced Data views (F1 Show Synced Data) Turn off Settings Sync Above error is shown It is a regression and after looking at the root cause, it seems this can also impact other settings sync scenarios. Hence tagging this as candidate.
Can you please verify this on latest insiders?
Sometimes inlay hints are off for a short amount of time: ! It happens randomly and fixes itself quickly: ! I cannot reproduce it in isolation or in the monaco editor playground, but I see it very often when working in the VS Code repo. I think this is what happens: I type somewhere to trigger a delayed update I wait until the delay completes and the provider is asked I add new lines The provider comes back, but does not consider the edits in between The inlay hints are off I'm not sure if this is an issue of the inlay hints feature or typescripts implementation.
/duplicate of
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for . See also our . Happy Coding!
I still do think is buggy behavior and not a problem of delays. The initial screenshot should not be observed, regardless of delays. I'm not sure though if this is a typescript bug or inlay hint bug. And I can still reproduce it by doing random edits (took me some minutes though): !
this is still a duplicate of
Repro steps: Wait for 4 seconds, notice the inlay hint afer Press enter in line 1 Wait for 1 second Press enter in line 1 every 100 ms Notice that after 3 seconds there are invalid inline suggestions ! Validation: In the playground, click on "Compare with latest dev" Verify that there are no invalid inline suggestions after doing the steps again
<!-- Do you have a question? Please ask it on --<!-- Use Help Report Issue to prefill these. --- VSCode Version: OS Version: Steps to Reproduce: a new file with a name starting with a space (using MacOS Finder) to rename the file by removing the space at the beginning of the file name (using the VS Code explorer). <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No
Confirmed on Windows too.. Edit: problem is . trims file names, but (in this case? in all cases?) should only remove trailing spaces.
We have received feedback that inlay hints blend in with the code too much. We aren't eager to tackle that with changing font sizes because that can "harm" readability. Instead we should tweak the colors, esp for our default themes
Looking at a combination of slight color changes and some minor padding/border radius tweaks to make them look like a visibly different element and less like highlighted regular code. An example for dark+: <img width="337" alt="CleanShot 2022-07-22 at 13 45 31 src="https://user-"And for light+: <img width="280" alt="CleanShot 2022-07-22 at 13 48 40 src="https://user-"
Adding to the list to make sure we look at the current line highlight color in relation to the inlay hints: !
Did you push these changes or are these changes anywhere to be applied for August? Otherwise I'll move this to September
Moved to September—I have the draft PR but I didn't consider the compact settings yet.
ping
Made changes to all four base theme types. The most noticeable changes will be in the high contrast and light themes. The dark had decent contrast already but I tweaked it a bit. Let me know what you think.
Issue Type: <bBug</bTesting . 1) Start creating a new folder in the explorer 2) Type 'folder1/' -once the '/' is in the input box every keystroke afterwards causes a full flicker of the information widget shown below the input box. This also happens on other platforms. VS Code version: Code - Insiders 1.21.0-insider (, 2018-02-27T06:17:53.785Z) OS version: Linux x64 4.4.0-59-generic Reproduces without extensions <!-- generated by issue reporter --
We need to debounce
Fixed by via
Issue Type: <bBug</bAssume If a FileSystemProvider extension implements more than one scheme, and if a file is opened using a scheme that is not used by the root folder(s) of the workspace, then when focus is switched to that file a call is issued on a folder resource that cannot possibly contain the file resource (because the scheme is different). In some scenarios a stat() call on a root folder can be costly, meaning it is important not to do it unnecessarily. This is not a new 1.37 issue. I will add information about how to demonstrate the issue using a variant of fsprovider-sample, and I am also willing to supply a PR to fix it. VS Code version: Code 1.37.0 (, 2019-08-08T02:33:50.993Z) OS version: Windows_NT x64 10.0.
Steps to reproduce: Use 1.38.0-insider, or a 1.37 build that contains the fix for branch at fsprovider-sample in VS Code a logpoint in the stat() method of (line 58) with the following message: that the 'Launch Extension' debug configuration. the Extension Development Host window appears, run the following commands in it: MemFS: Setup Workspace MemFS: Add Second Root MemFS: Create Files to Explorer view. on under the second root (MemFS2 - Different Scheme) the first root doubleclick on at least two files. the Debug Console of your initial VS Code instance, observe the stat messages as you switch between file tabs on the EDH, e.g. context menu of second root (MemFS2) to Remove Folder from Workspace. between tabs of the files and observe how when you click on the opened from memfs2 there is an additional stat of the first root (memfs)
Fixed via can you just let us know tomorrow once the new insiders is out if the issue is indeed fixed for you. Thank you
confirmed good in today's Insider. Thanks!
Thanks, adding verified label.
Testing on run continue on clone locally I see a browser-native dialog to open desktop I see a custom message that just reads "We tried opening Visual Studio Code - Insiders on your computer." which is confusing Unsure if we have to show the message or not but its wording needs to be improved. I mean tried and succeed in opening desktop so don't confusing me with this message. If we cannot prevent it I'd suggest to rephrase it and assume that it worked and give me a close option. Today, there this only covers the "didn't work cases" despite success https://user-
We cannot tell from the browser whether opening the protocol url succeeded, and the current wording for this dialog is based on a similar dialog from Office which also unconditionally appears in the browser: Maybe renaming 'Continue here' to 'Cancel' or 'Close' would help? Some other ideas for wording--when you launch a Zoom meeting from a browser in the desktop client, it says !
I can accept that but the wording should be positive/happy. Like: "This session now continues in VS Code Desktop. You can close this window, all your changes have been carried along. Try again if VS Code Desktop didn't start yet."
<!-- 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 am not happy with ctrl-shift-f. My steps: hit ctrl-shift-f enter the search term see several search results. want to go to the first match : There is no easy way to get to the first search result. After that I want to use up/down keys to go through the search results. The focus should not be in the source code. Screenshot of state of Step 5: ! Goal: Up to now I use the mouse and click on the first search result. If I use the mouse, I am at this state: ! After thinking about this some days, I think the best solution would be to map the ENTER to "Go to first search result". But not like F4, since F4 moves the cursor to the file, and not to the search result list. The ENTER should give the first item in the search result the focus. Then I can navigate to the matching result, and the next ENTER will bring me to the source code line. This would be great for all people who can't or don't want to use a mouse. Related:
Hi again! I'm just a bit confused on this part: For me, F4 moves to the first match, not the first file. Is this not what you're seeing? !
I think right now this might be the best you can do: is a better command to consider than what you were using. The problem is that <kbdEnter</kbdis used to re-run the search if you make any changes to the inputs. But the above keybinding does focus the first result without moving the cursor, and then <kbdEnter</kbddoes move the cursor.
thank you very much. If I add they keybinding via "Open Keyboard Shortcuts (JSON)", it works. But not always. After alt+enter I would like to use the up/down arrow keys and see the preview in the files. The strange thing: sometimes up/down shows me the places in the files (and the current entry in the result list is highlighted in blue color), and sometimes up/down does not show me the preview in the files.
We are on the right track, but not there yet. Thank you very much for your kind support.
For me, F4 moves to the first match. If I press up/down keys, the cursor moves in the file. But I would like to move up/down in the search result list and see the preview on the right side (in the window of the source code editor).
Hmm, that's interesting, I'm also seeing that the files aren't previewing after using . will look into this more.
I think I can get reproducible steps to the state where the file doesn't open when you have it highlighted in the tree view a long search it is searching, run using the up/down arrows to browse the search results, the file preview isn't triggering :bug: tree node is focused, but not selected :bug: This bug might be related to This is weird in that it only happens sometimes.
Look after is merged in Dark Modern: !
I see that it's currently using via Changing it to works, but I'm wondering what exactly broke this and why it was using in the first place?
It might have just always been out of sync which is common between the editor and simple find widget
! left : version 81 right : insiders Maybe it's related to background-color ?
! test, --vscode-panelInput-border color effect
hi , I don't know if it's some new issues.
is the find bg color meant to look like that?
Yes—changes made in to make editor widget and quick input backgrounds lighter to more easily distinguish against the editor background.
Yes, it's normal.Terminal simple find widget just not synchronized with the editor.
Issue Type: <bBug</bwhen clicking the percentage at the bottom-right of the state bar,zooming function won't work, and the aspect ratio changes to abnormal value. VS Code version: Code 1.28.1 (, 2018-10-11T18:13:53.910Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (9)</summaryExtensionVersion ------ intellij-idea-keybindings0.2.27 vscode-language-pack-zh-hans1.28.2 mssql1.4.0 java0.32.0 vscode-java-debug0.14.0 vscode-java-pack0.4.0 vscode-java-test0.10.0 vscode-maven0.11.1 markdown-all-in-one1.6.2 </details<!-- generated by issue reporter --
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.47 --<!-- potentialduplicatescomment --
The issue is that when I resize the page to see it along with other content, I can see some text over the scroll page area. I think it wasn't supposed to work like this, that's why i'm reporting it here. ! ! .
The scrollbar is intentionally transparent. We have a color that is used only when the minimap is enabled. We could potentially use it always if set to allow defining opaque scrollbars.
Oh. Thank you for explaining :) In this case, sorry for bothering! Best, Alvaro
To verify, configure the color and that will be applied and will make the overview ruler opaque. e.g.