Issue id
stringlengths 1
6
| Summary
stringlengths 1
277
| Created
stringdate 2015-11-13 16:34:23
2024-07-25 14:34:59
| Resolved
stringlengths 0
25
| Description
stringlengths 1
3.82k
| Resolution
stringclasses 4
values | Description_all
stringlengths 3
3.9k
| token_count
int16 6
1k
|
|---|---|---|---|---|---|---|---|
221818
|
Reveal in explorer throws
|
2024-07-16 15:07:54+00:00
|
2024-07-16 15:19:08+00:00
|
Seeing this when I run the command:
|
completed
|
Reveal in explorer throws Seeing this when I run the command:
| 61 |
221801
|
Terminal completions are often not loaded on start up
|
2024-07-16 11:22:20+00:00
|
2024-07-16 19:47:56+00:00
|
Repro:
1. `"terminal.integrated.suggest.enabled": true`
2. Create terminals and type `Get-`, ๐ it seems like more often than not right now the completions aren't being loaded
|
completed
|
Terminal completions are often not loaded on start up Repro:
1. `"terminal.integrated.suggest.enabled": true`
2. Create terminals and type `Get-`, ๐ it seems like more often than not right now the completions aren't being loaded
| 122 |
221798
|
Terminal sticky scroll goes to bottom of viewport when resized in the background
|
2024-07-16 10:49:07+00:00
|
2024-07-16 14:13:51+00:00
|
Repro:
1. Open vscode codebase
2. Ctrl+shift+b, verify sticky scroll is on top
3. Create a new terminal
4. Resize it horizontally
5. Go back to the tasks, ๐ sticky scroll header is on the bottom
|
completed
|
Terminal sticky scroll goes to bottom of viewport when resized in the background Repro:
1. Open vscode codebase
2. Ctrl+shift+b, verify sticky scroll is on top
3. Create a new terminal
4. Resize it horizontally
5. Go back to the tasks, ๐ sticky scroll header is on the bottom
| 129 |
221735
|
Run recent command doesn't work in remote windows
|
2024-07-15 17:24:22+00:00
|
2024-07-16 19:49:38+00:00
|
Repro:
1. Windows -> Windows tunnel
2. Focus terminal
3. Run recent command (ctrl+alt+r)
|
completed
|
Run recent command doesn't work in remote windows Repro:
1. Windows -> Windows tunnel
2. Focus terminal
3. Run recent command (ctrl+alt+r)
| 80 |
221724
|
Monaco overview ruler border is not drawn as expected
|
2024-07-15 15:31:48+00:00
|
2024-07-15 17:57:07+00:00
|
Problems:
1. Top-left most pixel is drawn to 3x times
2. Left border is drawn to 2x times
Setting `"workbench.colorCustomizations": { "editorOverviewRuler.border": "#f008" }`:
|
completed
|
Monaco overview ruler border is not drawn as expected Problems:
1. Top-left most pixel is drawn to 3x times
2. Left border is drawn to 2x times
Setting `"workbench.colorCustomizations": { "editorOverviewRuler.border": "#f008" }`:
| 250 |
221723
|
Terminal should have a border at the top of the overview ruler
|
2024-07-15 15:19:35+00:00
|
2024-07-16 14:13:05+00:00
|
Editor:
Terminal:
|
completed
|
Terminal should have a border at the top of the overview ruler Editor:
Terminal:
| 102 |
221718
|
1.91.1 Debian `sudo` in terminal no longer works
|
2024-07-15 14:05:43+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.1 f1e16e1e6214d7c44d078b1f0607b2388f29d729 x64
- OS Version: Debian GNU/Linux 12 (bookworm) 6.1.0-22-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.94-1 (2024-06-21) x86_64 GNU/Linux
Steps to Reproduce:
1. Start VSCode
2. Open terminal
3. Run `sudo echo`
Expected:
Password prompt for `sudo`
Actual:
> sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
> sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
It seems similar to #160380, however that was in an extension, and this is in a terminal.
I saw that people suggest running `code` with the `--no-sandbox` flag on [this ask Ubuntu](https://askubuntu.com/questions/1430521/unable-to-run-sudo-in-vs-code-terminal) however there are some issues with that:
- The option doesn't seem to exist, and does nothing when passed
- I absolutely don't want to disable the sandbox.
- I still want my self-created terminal to be `sudo` capable (but I don't want an extension to hijack it)
|
1.91.1 Debian `sudo` in terminal no longer works <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.1 f1e16e1e6214d7c44d078b1f0607b2388f29d729 x64
- OS Version: Debian GNU/Linux 12 (bookworm) 6.1.0-22-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.94-1 (2024-06-21) x86_64 GNU/Linux
Steps to Reproduce:
1. Start VSCode
2. Open terminal
3. Run `sudo echo`
Expected:
Password prompt for `sudo`
Actual:
> sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
> sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
It seems similar to #160380, however that was in an extension, and this is in a terminal.
I saw that people suggest running `code` with the `--no-sandbox` flag on [this ask Ubuntu](https://askubuntu.com/questions/1430521/unable-to-run-sudo-in-vs-code-terminal) however there are some issues with that:
- The option doesn't seem to exist, and does nothing when passed
- I absolutely don't want to disable the sandbox.
- I still want my self-created terminal to be `sudo` capable (but I don't want an extension to hijack it)
| 630 |
||
221685
|
[VSC-Web] "renameFile" may conflict soft-keyboard
|
2024-07-15 03:29:37+00:00
|
ย ย With a lengthy Files Explorer list, renaming files near the lower part of screen:
ย ย May cause the on-screen soft-keyboard to repeatedly show/hide.
ย ย .
ย ย Effectively rendering the function unusable.
ย ย Reproducible with: https://github.dev/FFmpeg/FFmpeg ("libavcodec")
ย ย Affects touch input mostly. (not necessarily mobile browsers exclusive)
ย ย Other alike text inputs are also susceptible. (e.g. those in "Settings")
----
Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
User Agent: Firefox 129
Embedder: github.dev
<!-- generated by web issue reporter -->
|
[VSC-Web] "renameFile" may conflict soft-keyboard ย ย With a lengthy Files Explorer list, renaming files near the lower part of screen:
ย ย May cause the on-screen soft-keyboard to repeatedly show/hide.
ย ย .
ย ย Effectively rendering the function unusable.
ย ย Reproducible with: https://github.dev/FFmpeg/FFmpeg ("libavcodec")
ย ย Affects touch input mostly. (not necessarily mobile browsers exclusive)
ย ย Other alike text inputs are also susceptible. (e.g. those in "Settings")
----
Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
User Agent: Firefox 129
Embedder: github.dev
<!-- generated by web issue reporter -->
| 196 |
||
221583
|
[File Watcher (node.js)] Error: ENAMETOOLONG: name too long
|
2024-07-12 15:39:11+00:00
|
See this in the console of insiders.. Looks like some ad-hoc chat model is ending up being file watched
```
ERR [File Watcher (node.js)] Error: ENAMETOOLONG: name too long, stat '/^/vscode-copilot-chat-code-block/4b3e2ea8-fd64-4d09-b875-d9770d5e94d4/response_0/0#{"references":[{"uri":{"$mid":1,"fsPath":"/Users/jrieken/Code/vscode/src/vs/workbench/contrib/inlineChat/browser/inlineChatNotebook.ts","external":"file:/Users/jrieken/Code/vscode/src/vs/workbench/contrib/inlineChat/browser/inlineChatNotebook.ts","path":"/Users/jrieken/Code/vscode/src/vs/workbench/contrib/inlineChat/browser/inlineChatNotebook.ts","scheme":"file"},"range":{"startLineNumber":21,"startColumn":3,"endLineNumber":21,"endColumn":72}},{"uri":{"$mid":1,"fsPath":"/Users/jrieken/Code/vscode/src/vs/workbench/api/browser/mainThreadWorkspace.ts","external":"file:/Users/jrieken/Code/vscode/src/vs/workbench/api/browser/mainThreadWorkspace.ts","path":"/Users/jrieken/Code/vscode/src/vs/workbench/api/browser/mainThreadWorkspace.ts","scheme":"file"},"range":{"startLineNumber":1,"startColumn":1,"endLineNumber":297,"endColumn":1}},{"uri":{"$mid":1,"fsPath":"/Users/jrieken/Code/vscode/src/vs/workbench/api/common/extHostWorkspace.ts","external":"file:/Users/jrieken/Code/vscode/src/vs/workbench/api/common/extHostWorkspace.ts","path":"/Users/jrieken/Code/vscode/src/vs/workbench/api/common/extHostWorkspace.ts","scheme":"file"},"range":{"startLineNumber":238,"startColumn":1,"endLineNumber":250,"endColumn":3}},{"uri":{"$mid":1,"fsPath":"/Users/jrieken/Code/vscode/src/vs/workbench/browser/web.main.ts","external":"file:/Users/jrieken/Code/vscode/src/vs/workbench/browser/web.main.ts","path":"/Users/jrieken/Code/vscode/src/vs/workbench/browser/path/to/inlineChatSessionService'
```
|
[File Watcher (node.js)] Error: ENAMETOOLONG: name too long See this in the console of insiders.. Looks like some ad-hoc chat model is ending up being file watched
```
ERR [File Watcher (node.js)] Error: ENAMETOOLONG: name too long, stat '/^/vscode-copilot-chat-code-block/4b3e2ea8-fd64-4d09-b875-d9770d5e94d4/response_0/0#{"references":[{"uri":{"$mid":1,"fsPath":"/Users/jrieken/Code/vscode/src/vs/workbench/contrib/inlineChat/browser/inlineChatNotebook.ts","external":"file:/Users/jrieken/Code/vscode/src/vs/workbench/contrib/inlineChat/browser/inlineChatNotebook.ts","path":"/Users/jrieken/Code/vscode/src/vs/workbench/contrib/inlineChat/browser/inlineChatNotebook.ts","scheme":"file"},"range":{"startLineNumber":21,"startColumn":3,"endLineNumber":21,"endColumn":72}},{"uri":{"$mid":1,"fsPath":"/Users/jrieken/Code/vscode/src/vs/workbench/api/browser/mainThreadWorkspace.ts","external":"file:/Users/jrieken/Code/vscode/src/vs/workbench/api/browser/mainThreadWorkspace.ts","path":"/Users/jrieken/Code/vscode/src/vs/workbench/api/browser/mainThreadWorkspace.ts","scheme":"file"},"range":{"startLineNumber":1,"startColumn":1,"endLineNumber":297,"endColumn":1}},{"uri":{"$mid":1,"fsPath":"/Users/jrieken/Code/vscode/src/vs/workbench/api/common/extHostWorkspace.ts","external":"file:/Users/jrieken/Code/vscode/src/vs/workbench/api/common/extHostWorkspace.ts","path":"/Users/jrieken/Code/vscode/src/vs/workbench/api/common/extHostWorkspace.ts","scheme":"file"},"range":{"startLineNumber":238,"startColumn":1,"endLineNumber":250,"endColumn":3}},{"uri":{"$mid":1,"fsPath":"/Users/jrieken/Code/vscode/src/vs/workbench/browser/web.main.ts","external":"file:/Users/jrieken/Code/vscode/src/vs/workbench/browser/web.main.ts","path":"/Users/jrieken/Code/vscode/src/vs/workbench/browser/path/to/inlineChatSessionService'
```
| 855 |
||
221581
|
`yarn run gulp vscode-darwin-arm64` fails when run in the debug terminal
|
2024-07-12 15:24:05+00:00
|
* open debug terminal
* run ` yarn run gulp vscode-darwin-arm64` (you might wanna disable mangling in build/gulpfile.compile.js#L19)
* the task fails (see error below)
* the task succeeds in a normal terminal
```
[17:19:10] Starting compile-extension-media-build ...
[17:19:10] Finished esbuilding extension media /Users/jrieken/Code/vscode/extensions/ipynb/esbuild.js with 0 errors.
[17:19:10] 'vscode-darwin-arm64' errored after 34 min
[17:19:10] Error: Promise rejected without Error
at onError (/Users/jrieken/Code/vscode/node_modules/async-done/index.js:49:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Waiting for the debugger to disconnect...
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Waiting for the debugger to disconnect...
```
|
`yarn run gulp vscode-darwin-arm64` fails when run in the debug terminal * open debug terminal
* run ` yarn run gulp vscode-darwin-arm64` (you might wanna disable mangling in build/gulpfile.compile.js#L19)
* the task fails (see error below)
* the task succeeds in a normal terminal
```
[17:19:10] Starting compile-extension-media-build ...
[17:19:10] Finished esbuilding extension media /Users/jrieken/Code/vscode/extensions/ipynb/esbuild.js with 0 errors.
[17:19:10] 'vscode-darwin-arm64' errored after 34 min
[17:19:10] Error: Promise rejected without Error
at onError (/Users/jrieken/Code/vscode/node_modules/async-done/index.js:49:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Waiting for the debugger to disconnect...
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Waiting for the debugger to disconnect...
```
| 307 |
||
221580
|
Initial terminal dimensions are reload are incorrect
|
2024-07-12 15:15:49+00:00
|
2024-07-12 16:22:23+00:00
|
Repro:
1. Open a terminal
2. Reload window
3. Select some rows in terminal, ๐ the selection should show columns reaching to near the scroll bar
|
completed
|
Initial terminal dimensions are reload are incorrect Repro:
1. Open a terminal
2. Reload window
3. Select some rows in terminal, ๐ the selection should show columns reaching to near the scroll bar
| 91 |
221575
|
Time to update active terminal is delayed
|
2024-07-12 14:14:59+00:00
|
2024-07-12 14:40:32+00:00
|
Repro:
1. Set `"terminal.integrated.tabs.showActiveTerminal": "always"`
2. Open 2 different shells in the terminal (they need different titles)
3. Click between the 2 tabs, ๐ notice that the "single inline tab" in the panel's update is delayed ~100ms, it should be instant.
|
completed
|
Time to update active terminal is delayed Repro:
1. Set `"terminal.integrated.tabs.showActiveTerminal": "always"`
2. Open 2 different shells in the terminal (they need different titles)
3. Click between the 2 tabs, ๐ notice that the "single inline tab" in the panel's update is delayed ~100ms, it should be instant.
| 148 |
221574
|
Copy paste indent
|
2024-07-12 14:03:08+00:00
|
Type: <b>Feature Request</b>
Copy pasting code breaks the indentation. Every time I have to copy and paste a block, I'm spending precious flow-breaking moments reformatting the pasted code, because VSCode cannot retain the correct indentation. Take a look at how Sublime does it. I can focus on work, not hitting tab and backspace a bunch of times just because the editor cannot do it.
VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:06:49.809Z)
OS version: Windows_NT x64 10.0.19045
Modes:
<!-- generated by issue reporter -->
|
Copy paste indent
Type: <b>Feature Request</b>
Copy pasting code breaks the indentation. Every time I have to copy and paste a block, I'm spending precious flow-breaking moments reformatting the pasted code, because VSCode cannot retain the correct indentation. Take a look at how Sublime does it. I can focus on work, not hitting tab and backspace a bunch of times just because the editor cannot do it.
VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:06:49.809Z)
OS version: Windows_NT x64 10.0.19045
Modes:
<!-- generated by issue reporter -->
| 181 |
||
221572
|
Terminal overview ruler should look and hide just like the editor one
|
2024-07-12 13:54:59+00:00
|
2024-07-12 14:39:50+00:00
|
To verify check all combinations of these and make sure it's color and whether it's visible makes sense:
- Themes
- `terminal.integrated.shellIntegration.decorationsEnabled`
|
completed
|
Terminal overview ruler should look and hide just like the editor one 
To verify check all combinations of these and make sure it's color and whether it's visible makes sense:
- Themes
- `terminal.integrated.shellIntegration.decorationsEnabled`
| 112 |
221571
|
Wrong syntax coloring in PHP with string 'AND ['
|
2024-07-12 13:34:47+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.92.0-insider (user setup)
Commit: a35380d6f0ff65f7c35345baafcf1c3f8a378d38
Date: 2024-07-12T05:08:08.550Z
Electron: 30.1.2
ElectronBuildId: 9759760
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
- OS Version: Windows_NT x64 10.0.22631
Steps to Reproduce:
1. I use insider build fresh installed, no changes
2. Use this code
```
<?php
$value = ' ANDRE [' . $test . ']';
echo 'abc';
$value = ' AND [' . $test;
$value = ' AND [' . $test . ']';
$value = ' AND [' . $test[1] . ']';
$value = ' ANDRE [' . $test . ']';
```
Shows in VSCode Inside and v1.91.1 this:
php sandbox
In vscode is a issue with string "AND ["?
EDIT: For clarification; Its "AND" with "[" in a string. This also applies to something like this:
" AND abc [ abc"
but this line shows correct coloring, if something comes before "AND"
"abc AND abc [ abc"
|
Wrong syntax coloring in PHP with string 'AND [' <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.92.0-insider (user setup)
Commit: a35380d6f0ff65f7c35345baafcf1c3f8a378d38
Date: 2024-07-12T05:08:08.550Z
Electron: 30.1.2
ElectronBuildId: 9759760
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
- OS Version: Windows_NT x64 10.0.22631
Steps to Reproduce:
1. I use insider build fresh installed, no changes
2. Use this code
```
<?php
$value = ' ANDRE [' . $test . ']';
echo 'abc';
$value = ' AND [' . $test;
$value = ' AND [' . $test . ']';
$value = ' AND [' . $test[1] . ']';
$value = ' ANDRE [' . $test . ']';
```
Shows in VSCode Inside and v1.91.1 this:
php sandbox
In vscode is a issue with string "AND ["?
EDIT: For clarification; Its "AND" with "[" in a string. This also applies to something like this:
" AND abc [ abc"
but this line shows correct coloring, if something comes before "AND"
"abc AND abc [ abc"
| 720 |
||
221565
|
Voiceover is not announcing Number of suggestions were found while searching any key in "keyboard shortcut edit field": A11y_Visual Studio Code Client_Customizations and settings_Keyboard Shortcuts_Screen Reader.
|
2024-07-12 12:36:16+00:00
|
### GIT Hub Tags:
#A11yWCAG2.1; #A11yTCS; #A11ySev2; #Visual Studio Code Client; #BM_Visual Studio Code Client_MAC_JULY2024; #DesktopApp; #WCAG4.1.3; #FTP; #A11yMAS; #Status Message;
### Environment and OS details:
MAC Book Pro
MAC OS Sonoma Version 14.5
Visual Studio code Insider version 1.92.0
### Reproduction Steps:
1. Open Visual Studio Code Insiders editor
2. Tab Navigate to setting icon.
3. Select "Keyboard shortcuts options" and press enter or Press keyboard shortcut as command K, Command S
4. Keyboard shortcut table gets opened.
5. Tab till "Keyboard Shortcut Edit field".
6. Type any Text or Key and Observe that Voiceover is not announcing Number of suggestions were found while searching any key in "keyboard shortcut edit field".
### Actual behavior:
Voiceover is not announcing Number of suggestions were found while searching any key in "keyboard shortcut edit field".
### Expected behavior:
Voiceover should be announcing Number of suggestions were found while searching any key in "keyboard shortcut edit field".
### User Impact:
Screen reader users will face difficulty if Voiceover is not announcing Number of suggestions were found while searching any key in "keyboard shortcut edit field".
### Attachments:
https://github.com/user-attachments/assets/00b8d197-5447-4c44-ab81-f814ad889caa
|
Voiceover is not announcing Number of suggestions were found while searching any key in "keyboard shortcut edit field": A11y_Visual Studio Code Client_Customizations and settings_Keyboard Shortcuts_Screen Reader. ### GIT Hub Tags:
#A11yWCAG2.1; #A11yTCS; #A11ySev2; #Visual Studio Code Client; #BM_Visual Studio Code Client_MAC_JULY2024; #DesktopApp; #WCAG4.1.3; #FTP; #A11yMAS; #Status Message;
### Environment and OS details:
MAC Book Pro
MAC OS Sonoma Version 14.5
Visual Studio code Insider version 1.92.0
### Reproduction Steps:
1. Open Visual Studio Code Insiders editor
2. Tab Navigate to setting icon.
3. Select "Keyboard shortcuts options" and press enter or Press keyboard shortcut as command K, Command S
4. Keyboard shortcut table gets opened.
5. Tab till "Keyboard Shortcut Edit field".
6. Type any Text or Key and Observe that Voiceover is not announcing Number of suggestions were found while searching any key in "keyboard shortcut edit field".
### Actual behavior:
Voiceover is not announcing Number of suggestions were found while searching any key in "keyboard shortcut edit field".
### Expected behavior:
Voiceover should be announcing Number of suggestions were found while searching any key in "keyboard shortcut edit field".
### User Impact:
Screen reader users will face difficulty if Voiceover is not announcing Number of suggestions were found while searching any key in "keyboard shortcut edit field".
### Attachments:
https://github.com/user-attachments/assets/00b8d197-5447-4c44-ab81-f814ad889caa
| 413 |
||
221553
|
Source Control is not showing the badge in this new version
|
2024-07-12 11:44:29+00:00
|
2024-07-15 18:48:49+00:00
|
Type: <b>Bug</b>
After updating for this new version, the Source Control tab is not showing the badge even with the option "Show badge" activated.
VS Code version: Code 1.91.0 (Universal) (ea1445cc7016315d0f5728f8e8b12a45dc0a7286, 2024-07-01T18:54:18.541Z)
OS version: Darwin arm64 23.4.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M1 Pro (10 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|3, 3, 2|
|Memory (System)|16.00GB (0.07GB free)|
|Process Argv|--crash-reporter-id 29c218b2-4989-4747-86ba-5ab2a2179e7e|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (16)</summary>
Extension|Author (truncated)|Version
---|---|---
flutter-snippets|ale|3.0.0
dart-code|Dar|3.92.0
flutter|Dar|3.92.0
flutter-find-unused-assets-and-dart-files|ese|1.0.2
bloc|Fel|6.6.6
flutter-coverage|flu|0.0.4
kotlin|fwc|0.2.34
copilot|Git|1.212.0
copilot-chat|Git|0.17.1
todo-tree|Gru|0.0.226
live-server|ms-|0.4.14
material-icon-theme|PKi|5.4.2
vscode-coverage-gutters|rya|2.11.1
lcov-lang|Ser|1.0.1
vscode-conventional-commits|viv|1.25.0
vscode-icons|vsc|12.8.0
(2 theme extensions excluded)
</details><details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
chatpanelt:31048053
dsvsc021:30996838
bdiig495:31013172
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupyter:31046869
legacy_priority:31082724
pythonrstrctxt:31093869
```
</details>
<!-- generated by issue reporter -->
|
completed
|
Source Control is not showing the badge in this new version
Type: <b>Bug</b>
After updating for this new version, the Source Control tab is not showing the badge even with the option "Show badge" activated.
VS Code version: Code 1.91.0 (Universal) (ea1445cc7016315d0f5728f8e8b12a45dc0a7286, 2024-07-01T18:54:18.541Z)
OS version: Darwin arm64 23.4.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M1 Pro (10 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|3, 3, 2|
|Memory (System)|16.00GB (0.07GB free)|
|Process Argv|--crash-reporter-id 29c218b2-4989-4747-86ba-5ab2a2179e7e|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (16)</summary>
Extension|Author (truncated)|Version
---|---|---
flutter-snippets|ale|3.0.0
dart-code|Dar|3.92.0
flutter|Dar|3.92.0
flutter-find-unused-assets-and-dart-files|ese|1.0.2
bloc|Fel|6.6.6
flutter-coverage|flu|0.0.4
kotlin|fwc|0.2.34
copilot|Git|1.212.0
copilot-chat|Git|0.17.1
todo-tree|Gru|0.0.226
live-server|ms-|0.4.14
material-icon-theme|PKi|5.4.2
vscode-coverage-gutters|rya|2.11.1
lcov-lang|Ser|1.0.1
vscode-conventional-commits|viv|1.25.0
vscode-icons|vsc|12.8.0
(2 theme extensions excluded)
</details><details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
chatpanelt:31048053
dsvsc021:30996838
bdiig495:31013172
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupyter:31046869
legacy_priority:31082724
pythonrstrctxt:31093869
```
</details>
<!-- generated by issue reporter -->
| 999 |
221535
|
Sorting in settings editor seems random
|
2024-07-12 07:42:52+00:00
|
* open settings UI
* search for `sticky scroll`
* :bug: note how settings for notebook, tree, editor, and terminal scroll are all interleaving and not sorted by "scope"
I expect all editor sticky scroll settings in one bucket, than all tree one, etc pp
|
Sorting in settings editor seems random * open settings UI
* search for `sticky scroll`
* :bug: note how settings for notebook, tree, editor, and terminal scroll are all interleaving and not sorted by "scope"
I expect all editor sticky scroll settings in one bucket, than all tree one, etc pp
| 116 |
||
221531
|
How to close the annoying terminal status window, which show information about PID, etc.?
|
2024-07-12 05:54:54+00:00
|
2024-07-15 17:51:15+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! feature_request_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Describe the feature you'd like. -->
I use Visual Studio Code to edit code on my MacOS. I often utilize VSCode Remote to run some Python code on a server. I usually open multiple terminal windows to conveniently view different code results. However, I frequently encounter the issue of being unable to select a specific terminal from the terminal tabs because that annoying terminal status windows always appears under my cursor when I move my mouse over a terminal, blocking my selection of the corresponding window. This fucking window moves very quickly, and I often find myself in the awkward situation of being unable to select the terminal. I wish I could completely disable this utterly useless prompt window.
<img width="523" alt="image" src="https://github.com/user-attachments/assets/122b5db6-12ab-4167-ba50-c3ff610a7bdd">
|
completed
|
How to close the annoying terminal status window, which show information about PID, etc.? <!-- โ ๏ธโ ๏ธ Do Not Delete This! feature_request_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Describe the feature you'd like. -->
I use Visual Studio Code to edit code on my MacOS. I often utilize VSCode Remote to run some Python code on a server. I usually open multiple terminal windows to conveniently view different code results. However, I frequently encounter the issue of being unable to select a specific terminal from the terminal tabs because that annoying terminal status windows always appears under my cursor when I move my mouse over a terminal, blocking my selection of the corresponding window. This fucking window moves very quickly, and I often find myself in the awkward situation of being unable to select the terminal. I wish I could completely disable this utterly useless prompt window.
<img width="523" alt="image" src="https://github.com/user-attachments/assets/122b5db6-12ab-4167-ba50-c3ff610a7bdd">
| 302 |
221521
|
go to next/previous in accessible view for inline completions doesn't work
|
2024-07-11 23:05:58+00:00
|
2024-07-12 18:20:08+00:00
|
I noticed this when working on #221497, which has a different cause I am currently fixing. Wanted to note that it doesn't work _before_ my changes here ๐
https://github.com/user-attachments/assets/2777805a-2dff-4751-a5be-3da51a7e2194
|
completed
|
go to next/previous in accessible view for inline completions doesn't work I noticed this when working on #221497, which has a different cause I am currently fixing. Wanted to note that it doesn't work _before_ my changes here ๐
https://github.com/user-attachments/assets/2777805a-2dff-4751-a5be-3da51a7e2194
| 97 |
221497
|
go to next/previous in the accessible view no longer work
|
2024-07-11 18:31:43+00:00
|
2024-07-12 18:20:07+00:00
|
1. run a few chat responses
2. open the accessible view
3. try to go to next and previous
4. ๐ chat list is focused instead
|
completed
|
go to next/previous in the accessible view no longer work 1. run a few chat responses
2. open the accessible view
3. try to go to next and previous
4. ๐ chat list is focused instead
| 44 |
221495
|
Search editor shows the wrong results when running multiple
|
2024-07-11 18:22:08+00:00
|
Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.91.1
- OS Version: MacOS 13.6.7
Steps to Reproduce:
1. Open a large workspace.
2. Set `search.mode` to "newEditor".
3. Quickly do a project-wide search for two different things. Make sure they are running concurrently. When the search finishes for one, check the results of the other search editor. The search results in both editors are the same. It seems to match the last search completed (or maybe it's the results of the search in focus when it competes).
I've been noticing this for at least a few months now, so it's not related to the newest version. I can also duplicate this in the Insiders build.
|
Search editor shows the wrong results when running multiple Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.91.1
- OS Version: MacOS 13.6.7
Steps to Reproduce:
1. Open a large workspace.
2. Set `search.mode` to "newEditor".
3. Quickly do a project-wide search for two different things. Make sure they are running concurrently. When the search finishes for one, check the results of the other search editor. The search results in both editors are the same. It seems to match the last search completed (or maybe it's the results of the search in focus when it competes).
I've been noticing this for at least a few months now, so it's not related to the newest version. I can also duplicate this in the Insiders build.
| 181 |
||
221478
|
Breakpoints stuck under line numbers
|
2024-07-11 15:36:15+00:00
|
2024-07-11 18:35:31+00:00
|
I notice on the latest insiders now when I start and stop debugging the breakpoints are ending up below the line numbers instead of the gutter
|
completed
|
Breakpoints stuck under line numbers I notice on the latest insiders now when I start and stop debugging the breakpoints are ending up below the line numbers instead of the gutter
| 82 |
221464
|
Running a task does not show the build terminal if an editor terminal is open
|
2024-07-11 12:51:55+00:00
|
2024-07-16 19:26:47+00:00
|
Type: <b>Bug</b>
Preparation: create the following `.vscode/tasks.json` file:
```json
{
"version": "2.0.0",
"tasks": [
{
"label": "Test",
"type": "shell",
"command": "sleep 10"
}
]
}
```
1. In the terminals panel, create a new shell terminal
2. Drag it to the main editor area to make it a full-size terminal
3. Also open an editor tab (any file will do, including Command-N)
4. Make sure the panel is closed (press Command-J to close it if it is open)
5. Run the above task (e.g. with Command-P, then type `task Test`)
Expected: the panel opens and shows the running task
Actual: the editor terminal is brought to the front, and the panel stays closed
VS Code version: Code - Insiders 1.92.0-insider (c37f4a49e28831cec1aec1af0f626edaada1f7ce, 2024-07-11T05:03:58.450Z)
OS version: Darwin arm64 23.5.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M1 Max (10 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|4, 5, 6|
|Memory (System)|32.00GB (3.14GB free)|
|Process Argv|--disable-extensions . --crash-reporter-id 0af73232-1e42-4c3f-95c4-5b10f8deb228|
|Screen Reader|no|
|VM|0%|
</details>Extensions disabled
<!-- generated by issue reporter -->
|
completed
|
Running a task does not show the build terminal if an editor terminal is open
Type: <b>Bug</b>
Preparation: create the following `.vscode/tasks.json` file:
```json
{
"version": "2.0.0",
"tasks": [
{
"label": "Test",
"type": "shell",
"command": "sleep 10"
}
]
}
```
1. In the terminals panel, create a new shell terminal
2. Drag it to the main editor area to make it a full-size terminal
3. Also open an editor tab (any file will do, including Command-N)
4. Make sure the panel is closed (press Command-J to close it if it is open)
5. Run the above task (e.g. with Command-P, then type `task Test`)
Expected: the panel opens and shows the running task
Actual: the editor terminal is brought to the front, and the panel stays closed
VS Code version: Code - Insiders 1.92.0-insider (c37f4a49e28831cec1aec1af0f626edaada1f7ce, 2024-07-11T05:03:58.450Z)
OS version: Darwin arm64 23.5.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M1 Max (10 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|4, 5, 6|
|Memory (System)|32.00GB (3.14GB free)|
|Process Argv|--disable-extensions . --crash-reporter-id 0af73232-1e42-4c3f-95c4-5b10f8deb228|
|Screen Reader|no|
|VM|0%|
</details>Extensions disabled
<!-- generated by issue reporter -->
| 606 |
221450
|
VS Code 1.91 does not respect SourceControl.count
|
2024-07-11 08:13:37+00:00
|
2024-07-22 09:19:16+00:00
|
Type: <b>Bug</b>
Starting with version 1.91.0, the count badge on the Source Control icon no longer takes into account the `SourceControl.count` value and instead counts all SourceControlResourceGroup.
Steps to reproduce:
1. Set `git.countBadge` to "tracked"
2. Create new untracked file in Git repository
VS Code version: Code 1.91.0 (Universal) (ea1445cc7016315d0f5728f8e8b12a45dc0a7286, 2024-07-01T18:54:18.541Z)
OS version: Darwin arm64 23.5.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M1 Pro (10 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|2, 4, 4|
|Memory (System)|32.00GB (1.32GB free)|
|Process Argv|--enable-proposed-api jeanp413.open-remote-ssh --crash-reporter-id 481d6038-57fa-4033-9fd6-30428eae7833|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none
<!-- generated by issue reporter -->
|
completed
|
VS Code 1.91 does not respect SourceControl.count
Type: <b>Bug</b>
Starting with version 1.91.0, the count badge on the Source Control icon no longer takes into account the `SourceControl.count` value and instead counts all SourceControlResourceGroup.
Steps to reproduce:
1. Set `git.countBadge` to "tracked"
2. Create new untracked file in Git repository
VS Code version: Code 1.91.0 (Universal) (ea1445cc7016315d0f5728f8e8b12a45dc0a7286, 2024-07-01T18:54:18.541Z)
OS version: Darwin arm64 23.5.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M1 Pro (10 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|2, 4, 4|
|Memory (System)|32.00GB (1.32GB free)|
|Process Argv|--enable-proposed-api jeanp413.open-remote-ssh --crash-reporter-id 481d6038-57fa-4033-9fd6-30428eae7833|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none
<!-- generated by issue reporter -->
| 492 |
221416
|
Insider build no longer opens .code-workspace from command line
|
2024-07-10 21:18:41+00:00
|
2024-07-11 01:16:03+00:00
|
Type: <b>Bug</b>
I always start VS Code from the terminal using `code-insiders my.code-workspace` but as of 1 day ago it no longer opens to workspace, instead I get an empty file called "my.code-workspace" as if the file doesn't exist. The file exists, and it works fine if I open the work-space from the File menu.
VS Code version: Code - Insiders 1.92.0-insider (c0cdcac0616454584ec7611c34337efa046b6965, 2024-07-10T14:55:36.989Z)
OS version: Darwin arm64 23.5.0
Modes: Restricted
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M1 Pro (8 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|2, 2, 3|
|Memory (System)|32.00GB (0.71GB free)|
|Process Argv|defang-mvp.code-workspace --disable-extensions --crash-reporter-id a649755e-ea3a-456b-b387-1787cc6d54e7|
|Screen Reader|no|
|VM|0%|
</details>Extensions disabled<details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vsc_aacf:30263846
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:31024238
c4g48928:30535728
vscrp:30624060
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythonregdiag2:30926734
pythonmypyd1:30859725
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
cppperfnew:30980852
pythonait:30973460
chatpanelt:31014475
9c06g630:31013171
a69g1124:31018687
dvdeprecation:31040973
dwnewjupytercf:31046870
impr_priority:31057980
nativerepl1:31093711
refactort:31084545
pythonrstrctxt:31093868
4930e709:31088354
1iic9185:31091668
```
</details>
<!-- generated by issue reporter -->
|
completed
|
Insider build no longer opens .code-workspace from command line
Type: <b>Bug</b>
I always start VS Code from the terminal using `code-insiders my.code-workspace` but as of 1 day ago it no longer opens to workspace, instead I get an empty file called "my.code-workspace" as if the file doesn't exist. The file exists, and it works fine if I open the work-space from the File menu.
VS Code version: Code - Insiders 1.92.0-insider (c0cdcac0616454584ec7611c34337efa046b6965, 2024-07-10T14:55:36.989Z)
OS version: Darwin arm64 23.5.0
Modes: Restricted
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M1 Pro (8 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|2, 2, 3|
|Memory (System)|32.00GB (0.71GB free)|
|Process Argv|defang-mvp.code-workspace --disable-extensions --crash-reporter-id a649755e-ea3a-456b-b387-1787cc6d54e7|
|Screen Reader|no|
|VM|0%|
</details>Extensions disabled<details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vsc_aacf:30263846
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:31024238
c4g48928:30535728
vscrp:30624060
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythonregdiag2:30926734
pythonmypyd1:30859725
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
cppperfnew:30980852
pythonait:30973460
chatpanelt:31014475
9c06g630:31013171
a69g1124:31018687
dvdeprecation:31040973
dwnewjupytercf:31046870
impr_priority:31057980
nativerepl1:31093711
refactort:31084545
pythonrstrctxt:31093868
4930e709:31088354
1iic9185:31091668
```
</details>
<!-- generated by issue reporter -->
| 888 |
221401
|
No way to cancel launching a debug session that is stuck
|
2024-07-10 18:15:31+00:00
|
1. Use F5 with a prelaunch task that never completes, e.g. because it wants watchers that aren't available
2. :bug: debug session starts spinning and never completes. I have to do a full window reload in order to retry the debug session launch
|
No way to cancel launching a debug session that is stuck 1. Use F5 with a prelaunch task that never completes, e.g. because it wants watchers that aren't available
2. :bug: debug session starts spinning and never completes. I have to do a full window reload in order to retry the debug session launch
| 80 |
||
221399
|
Don't fire onDidEndTerminalShellExecution with exitCode undefined immediately after first onDidChangeTerminalShellIntegration
|
2024-07-10 18:02:12+00:00
|
I think what is causing problems for @anthonykim1 is that calling `executeCommand` immediately after `onDidChangeTerminalShellIntegration` would fire multiple times and end up triggering an invalid `onDidEndTerminalShellExecution` with exitCode=undefined but the execution was set when it shouldn't have been. We should suppress this event if possible.
|
Don't fire onDidEndTerminalShellExecution with exitCode undefined immediately after first onDidChangeTerminalShellIntegration I think what is causing problems for @anthonykim1 is that calling `executeCommand` immediately after `onDidChangeTerminalShellIntegration` would fire multiple times and end up triggering an invalid `onDidEndTerminalShellExecution` with exitCode=undefined but the execution was set when it shouldn't have been. We should suppress this event if possible.
| 135 |
||
221396
|
User activity api regression on stable
|
2024-07-10 17:26:07+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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/from sources
- OS Version:
Regression from https://github.com/microsoft/vscode/pull/214264
@connor4312 This broke user activity api, with this any extension that runs some background task using `showProgress` will make the api report as `active` which is not desired.
In my case:
- I use the api to send heartbeat events to backend
- GHPR extension runs some background git commands periodically
- Git extension calls the showProgress api which in turn makes user activity api report as `active`
Would be good to fix it for recovery release ๐
|
User activity api regression on stable <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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/from sources
- OS Version:
Regression from https://github.com/microsoft/vscode/pull/214264
@connor4312 This broke user activity api, with this any extension that runs some background task using `showProgress` will make the api report as `active` which is not desired.
In my case:
- I use the api to send heartbeat events to backend
- GHPR extension runs some background git commands periodically
- Git extension calls the showProgress api which in turn makes user activity api report as `active`
Would be good to fix it for recovery release ๐
| 445 |
||
221385
|
`ChatWidget#onDidChangeContentHeight` doesn't fire when attaching context
|
2024-07-10 15:46:45+00:00
|
2024-07-11 18:21:56+00:00
|
In process of enabling file attachments for inline chat. It seems that adding context doesn't trigger a `onDidChangeContentHeight`-event which causes ugly layouting for the content chat widget. Tho, it does [call re-layout](https://github.com/microsoft/vscode/blob/37d05b2a2d53361ad4cbe963bc55e08823ca69fc/src/vs/workbench/contrib/chat/browser/chatWidget.ts#L800-L802) which is fishy because it doesn't give the owner a chance to assign a new height
|
completed
|
`ChatWidget#onDidChangeContentHeight` doesn't fire when attaching context In process of enabling file attachments for inline chat. It seems that adding context doesn't trigger a `onDidChangeContentHeight`-event which causes ugly layouting for the content chat widget. Tho, it does [call re-layout](https://github.com/microsoft/vscode/blob/37d05b2a2d53361ad4cbe963bc55e08823ca69fc/src/vs/workbench/contrib/chat/browser/chatWidget.ts#L800-L802) which is fishy because it doesn't give the owner a chance to assign a new height
| 179 |
221382
|
opening folders from CLI tries to open a file
|
2024-07-10 15:23:32+00:00
|
2024-07-11 01:09:30+00:00
|
Type: <b>Bug</b>
On Mac, try to open a folder in vscode , from iterm2
$ code -n work
This opens a non-existing file, instead of the folder in the SCM
VS Code version: Code - Insiders 1.92.0-insider (8703a11164db333db471576d38ddc143d6ad7ead, 2024-07-10T08:26:11.347Z)
OS version: Darwin arm64 23.6.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M1 Pro (10 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|4, 3, 3|
|Memory (System)|32.00GB (0.16GB free)|
|Process Argv|-n work/di/SRE/sre-dev-consul-kv work/di/SRE/sre-dev-nomad-scheduler|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (19)</summary>
Extension|Author (truncated)|Version
---|---|---
vscode-base64|ada|0.1.0
inline-hasher|ale|1.1.0
spellright|ban|3.0.132
iam-policy|bin|0.0.1
copilot|Git|1.211.978
copilot-chat|Git|0.18.2024071001
terraform|has|2.32.2024070910
vscode-kubernetes-tools|ms-|1.3.16
indent-rainbow|ode|8.3.1
ytt-lint|phi|0.3.1
vscode-yaml|red|1.15.0
vscode-gitweblinks|red|2.11.0
iam-legend|Seb|1.1.49
kubernator-vscode|smp|1.0.0
code-spell-checker|str|3.0.1
shellcheck|tim|0.37.1
sort-lines|Tyr|1.11.0
errorlens|use|3.20.0
vscode-icons|vsc|12.8.0
(1 theme extensions excluded)
</details>
<!-- generated by issue reporter -->
|
completed
|
opening folders from CLI tries to open a file Type: <b>Bug</b>
On Mac, try to open a folder in vscode , from iterm2
$ code -n work
This opens a non-existing file, instead of the folder in the SCM
VS Code version: Code - Insiders 1.92.0-insider (8703a11164db333db471576d38ddc143d6ad7ead, 2024-07-10T08:26:11.347Z)
OS version: Darwin arm64 23.6.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M1 Pro (10 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|4, 3, 3|
|Memory (System)|32.00GB (0.16GB free)|
|Process Argv|-n work/di/SRE/sre-dev-consul-kv work/di/SRE/sre-dev-nomad-scheduler|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (19)</summary>
Extension|Author (truncated)|Version
---|---|---
vscode-base64|ada|0.1.0
inline-hasher|ale|1.1.0
spellright|ban|3.0.132
iam-policy|bin|0.0.1
copilot|Git|1.211.978
copilot-chat|Git|0.18.2024071001
terraform|has|2.32.2024070910
vscode-kubernetes-tools|ms-|1.3.16
indent-rainbow|ode|8.3.1
ytt-lint|phi|0.3.1
vscode-yaml|red|1.15.0
vscode-gitweblinks|red|2.11.0
iam-legend|Seb|1.1.49
kubernator-vscode|smp|1.0.0
code-spell-checker|str|3.0.1
shellcheck|tim|0.37.1
sort-lines|Tyr|1.11.0
errorlens|use|3.20.0
vscode-icons|vsc|12.8.0
(1 theme extensions excluded)
</details>
<!-- generated by issue reporter -->
| 697 |
221377
|
`getTerminalActionBarArgs` called twice
|
2024-07-10 14:54:13+00:00
|
2024-07-12 15:13:56+00:00
|
I'm not sure if that's an oversight, but `getTerminalActionBarArgs` is called twice.
https://github.com/microsoft/vscode/blob/6f2f74c6b21ac220f644509145e729a0dd78dd76/src/vs/workbench/contrib/terminal/browser/terminalView.ts#L276
and then again in
https://github.com/microsoft/vscode/blob/6f2f74c6b21ac220f644509145e729a0dd78dd76/src/vs/workbench/contrib/terminal/browser/terminalView.ts#L280
|
completed
|
`getTerminalActionBarArgs` called twice
I'm not sure if that's an oversight, but `getTerminalActionBarArgs` is called twice.
https://github.com/microsoft/vscode/blob/6f2f74c6b21ac220f644509145e729a0dd78dd76/src/vs/workbench/contrib/terminal/browser/terminalView.ts#L276
and then again in
https://github.com/microsoft/vscode/blob/6f2f74c6b21ac220f644509145e729a0dd78dd76/src/vs/workbench/contrib/terminal/browser/terminalView.ts#L280
| 182 |
221369
|
Ctrl+tab shows show in search panel button
|
2024-07-10 14:24:47+00:00
|
2024-07-11 01:02:49+00:00
|
|
completed
|
Ctrl+tab shows show in search panel button 
| 95 |
221367
|
Quick pick widget - header rendering issues
|
2024-07-10 14:09:09+00:00
|
2024-07-11 01:40:45+00:00
|
Open quick pick widget and notice the lower corners of the header are rounded.
|
completed
|
Quick pick widget - header rendering issues Open quick pick widget and notice the lower corners of the header are rounded.
| 73 |
221362
|
BUG: `Move line down` command doesnt preserve indentation
|
2024-07-10 13:35:02+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
Commit: ea1445cc7016315d0f5728f8e8b12a45dc0a7286
Steps to Reproduce:
1. Put TS code
```ts
import {
bla
} from 'bla';
```
2. Being on first line use command `Move line down`, move `import` on second line
3. Now move `import` back to first line
4. Formatting is lost:
```ts
import {
bla // here is lost original formatting
} from 'bla';
```
|
BUG: `Move line down` command doesnt preserve indentation
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
Commit: ea1445cc7016315d0f5728f8e8b12a45dc0a7286
Steps to Reproduce:
1. Put TS code
```ts
import {
bla
} from 'bla';
```
2. Being on first line use command `Move line down`, move `import` on second line
3. Now move `import` back to first line
4. Formatting is lost:
```ts
import {
bla // here is lost original formatting
} from 'bla';
```
| 429 |
||
221359
|
HoverWidget - codicons are not vertically aligned
|
2024-07-10 13:28:55+00:00
|
2024-07-10 13:29:09+00:00
|
Steps to Reproduce:
1. Open a folder/workspace that contains a git repository
2. Open a file, make some changes, and create a commit
3. In the Source Control view hover over a particular commit in the incoming/outgoing section (notice that the codicons are not aligned)
|
completed
|
HoverWidget - codicons are not vertically aligned Steps to Reproduce:
1. Open a folder/workspace that contains a git repository
2. Open a file, make some changes, and create a commit
3. In the Source Control view hover over a particular commit in the incoming/outgoing section (notice that the codicons are not aligned)
| 130 |
221358
|
undo not working in settings search input when i paste some text
|
2024-07-10 13:23:32+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91
- OS Version: win10 and macos
Steps to Reproduce:
1. ctrl v to paste some text in search input
2. the first ctrl z not working and try to again. it's ok!
|
undo not working in settings search input when i paste some text <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91
- OS Version: win10 and macos
Steps to Reproduce:
1. ctrl v to paste some text in search input
2. the first ctrl z not working and try to again. it's ok!
| 413 |
||
221356
|
Search/find gets stuck when changing tabs
|
2024-07-10 13:20:50+00:00
|
2024-07-10 14:26:13+00:00
|
Type: <b>Bug</b>
Search/find toolbar gets stuck, cannot be removed nor focused - when using keyboard shortuct it doesn't get focused as well.
VS Code version: Code - Insiders 1.92.0-insider (8703a11164db333db471576d38ddc143d6ad7ead, 2024-07-10T08:26:11.347Z)
OS version: Windows_NT x64 10.0.26100
Modes:
Remote OS version: Linux x64 5.15.146.1-microsoft-standard-WSL2
Remote OS version: Linux x64 5.15.146.1-microsoft-standard-WSL2
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 5800X 8-Core Processor (16 x 3800)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|31.92GB (11.24GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
|Item|Value|
|---|---|
|Remote|WSL: Ubuntu|
|OS|Linux x64 5.15.146.1-microsoft-standard-WSL2|
|CPUs|AMD Ryzen 7 5800X 8-Core Processor (6 x 0)|
|Memory (System)|15.62GB (11.85GB free)|
|VM|0%|
|Item|Value|
|---|---|
|Remote|WSL: Ubuntu|
|OS|Linux x64 5.15.146.1-microsoft-standard-WSL2|
|CPUs|AMD Ryzen 7 5800X 8-Core Processor (6 x 0)|
|Memory (System)|15.62GB (11.85GB free)|
|VM|0%|
</details><details><summary>Extensions (1)</summary>
Extension|Author (truncated)|Version
---|---|---
remote-wsl|ms-|0.88.2
</details>
<!-- generated by issue reporter -->
|
completed
|
Search/find gets stuck when changing tabs Type: <b>Bug</b>
Search/find toolbar gets stuck, cannot be removed nor focused - when using keyboard shortuct it doesn't get focused as well.
VS Code version: Code - Insiders 1.92.0-insider (8703a11164db333db471576d38ddc143d6ad7ead, 2024-07-10T08:26:11.347Z)
OS version: Windows_NT x64 10.0.26100
Modes:
Remote OS version: Linux x64 5.15.146.1-microsoft-standard-WSL2
Remote OS version: Linux x64 5.15.146.1-microsoft-standard-WSL2
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 5800X 8-Core Processor (16 x 3800)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|31.92GB (11.24GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
|Item|Value|
|---|---|
|Remote|WSL: Ubuntu|
|OS|Linux x64 5.15.146.1-microsoft-standard-WSL2|
|CPUs|AMD Ryzen 7 5800X 8-Core Processor (6 x 0)|
|Memory (System)|15.62GB (11.85GB free)|
|VM|0%|
|Item|Value|
|---|---|
|Remote|WSL: Ubuntu|
|OS|Linux x64 5.15.146.1-microsoft-standard-WSL2|
|CPUs|AMD Ryzen 7 5800X 8-Core Processor (6 x 0)|
|Memory (System)|15.62GB (11.85GB free)|
|VM|0%|
</details><details><summary>Extensions (1)</summary>
Extension|Author (truncated)|Version
---|---|---
remote-wsl|ms-|0.88.2
</details>
<!-- generated by issue reporter -->
| 738 |
221348
|
Terminal content is showing at fixed height after word wrap using Alt + z
|
2024-07-10 11:42:27+00:00
|
2024-07-18 20:27:24+00:00
|
Type: <b>Bug</b>
step 1 - Run any command or project whose lines does'nt fit in single line
step 2 - Your terminal can be full sized or small size does'nt matter
step 3- Presss Alt + z to wrap line in terminal
Step 4 - Resize your terminal window
Example -
If initially terminal window height is 100px from the bottom then word wrap using Alt + z and after that increase or discrease the size of terminal window. You will find that content is still showing in 100px of height
VS Code version: Code 1.91.0 (ea1445cc7016315d0f5728f8e8b12a45dc0a7286, 2024-07-01T18:52:41.959Z)
OS version: Linux x64 5.15.0-113-generic
Modes:
<!-- generated by issue reporter -->
|
completed
|
Terminal content is showing at fixed height after word wrap using Alt + z
Type: <b>Bug</b>
step 1 - Run any command or project whose lines does'nt fit in single line
step 2 - Your terminal can be full sized or small size does'nt matter
step 3- Presss Alt + z to wrap line in terminal
Step 4 - Resize your terminal window
Example -
If initially terminal window height is 100px from the bottom then word wrap using Alt + z and after that increase or discrease the size of terminal window. You will find that content is still showing in 100px of height
VS Code version: Code 1.91.0 (ea1445cc7016315d0f5728f8e8b12a45dc0a7286, 2024-07-01T18:52:41.959Z)
OS version: Linux x64 5.15.0-113-generic
Modes:
<!-- generated by issue reporter -->
| 203 |
221340
|
Close group tabs button includes the active tab in the close action
|
2024-07-10 10:43:25+00:00
|
2024-07-10 14:13:25+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
- Validation: ea1445cc7016315d0f5728f8e8b12a45dc0a7286
- Date: 2024-07-01T18:53:23.353Z
- Electron: 29.4.0
- ElectronBuildId: 9728852
- Chromium: 122.0.6261.156
- Node.js: 20.9.0
- V8: 12.2.281.27-electron.0
- OS Version: Darwin arm64 22.6.0
Steps to Reproduce:
1. Open multiple tabs
2. Keep a tab you don't want to close active (different group)
3. Click to close a different group (from the one with the active tab)
Demo:
https://github.com/microsoft/vscode/assets/9453090/2a41c06a-2b96-426b-b99d-9a09e2b0a715
|
completed
|
Close group tabs button includes the active tab in the close action <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
- Validation: ea1445cc7016315d0f5728f8e8b12a45dc0a7286
- Date: 2024-07-01T18:53:23.353Z
- Electron: 29.4.0
- ElectronBuildId: 9728852
- Chromium: 122.0.6261.156
- Node.js: 20.9.0
- V8: 12.2.281.27-electron.0
- OS Version: Darwin arm64 22.6.0
Steps to Reproduce:
1. Open multiple tabs
2. Keep a tab you don't want to close active (different group)
3. Click to close a different group (from the one with the active tab)
Demo:
https://github.com/microsoft/vscode/assets/9453090/2a41c06a-2b96-426b-b99d-9a09e2b0a715
| 511 |
221335
|
Action button in quick input menu is not aligned
|
2024-07-10 08:52:33+00:00
|
2024-07-22 23:09:11+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
- OS Version: MacOS Sonoma 14.5
Steps to Reproduce:
1. `Ctrl+R`
2. Hover the action button
3. See everything disaligned
<img width="46" alt="Screenshot 2024-07-10 at 09 48 44" src="https://github.com/microsoft/vscode/assets/15343819/82f7899b-7545-45cc-9f7d-7471581f3495">
Bigger and more demonstrative example
<img width="86" alt="Screenshot 2024-07-10 at 09 52 00" src="https://github.com/microsoft/vscode/assets/15343819/b1da444e-795f-4bcf-9b8b-faad4d1b789a">
|
completed
|
Action button in quick input menu is not aligned <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
- OS Version: MacOS Sonoma 14.5
Steps to Reproduce:
1. `Ctrl+R`
2. Hover the action button
3. See everything disaligned
<img width="46" alt="Screenshot 2024-07-10 at 09 48 44" src="https://github.com/microsoft/vscode/assets/15343819/82f7899b-7545-45cc-9f7d-7471581f3495">
Bigger and more demonstrative example
<img width="86" alt="Screenshot 2024-07-10 at 09 52 00" src="https://github.com/microsoft/vscode/assets/15343819/b1da444e-795f-4bcf-9b8b-faad4d1b789a">
| 494 |
221331
|
Incorrect coloring of text in a selected disabled extenstion within extensions view
|
2024-07-10 08:15:52+00:00
|
2024-07-12 11:30:09+00:00
|
Repro:
1. Set theme to Light+
2. Open extensions view and select a disabled extension - :bug: background is blue and text is in grey which makes it unreadable
|
completed
|
Incorrect coloring of text in a selected disabled extenstion within extensions view Repro:
1. Set theme to Light+
2. Open extensions view and select a disabled extension - :bug: background is blue and text is in grey which makes it unreadable
| 151 |
221299
|
TypeScript support on vscode.dev is broken
|
2024-07-09 20:57:07+00:00
|
2024-07-25 15:46:27+00:00
|
1. Open https://vscode.dev/github/microsoft/vscode-vsce
2. Open any TS file
```
ERR [Extension Host] Error processing request. Could not read file outside of project root /vscode-vfs/github/microsoft/node_modules/@typescript/lib-es5
Error: Could not read file outside of project root /vscode-vfs/github/microsoft/node_modules/@typescript/lib-es5
at e.PathMapper.toResource (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:2562875)
at Object.y [as realpath] (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:2568764)
at https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1399888
at $ (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1400319)
at P (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1398108)
at j (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1398383)
at O (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1397767)
at Object.resolveLibrary (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1392591)
at gcA.resolveLibrary (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:2276820)
at Rt (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1345815)
```
|
completed
|
TypeScript support on vscode.dev is broken 1. Open https://vscode.dev/github/microsoft/vscode-vsce
2. Open any TS file
```
ERR [Extension Host] Error processing request. Could not read file outside of project root /vscode-vfs/github/microsoft/node_modules/@typescript/lib-es5
Error: Could not read file outside of project root /vscode-vfs/github/microsoft/node_modules/@typescript/lib-es5
at e.PathMapper.toResource (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:2562875)
at Object.y [as realpath] (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:2568764)
at https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1399888
at $ (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1400319)
at P (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1398108)
at j (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1398383)
at O (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1397767)
at Object.resolveLibrary (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1392591)
at gcA.resolveLibrary (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:2276820)
at Rt (https://main.vscode-cdn.net/stable/ea1445cc7016315d0f5728f8e8b12a45dc0a7286/extensions/typescript-language-features/dist/browser/typescript/tsserver.web.js:7:1345815)
```
| 956 |
221281
|
SCM - history graph is not rendering correctly
|
2024-07-09 14:14:40+00:00
|
2024-07-09 14:32:42+00:00
|
Notice the white hair lines between the list rows:
It turns out that if the IconLabel has a description the height of the row is `22.5px` instead of `22px`.
|
completed
|
SCM - history graph is not rendering correctly Notice the white hair lines between the list rows:
It turns out that if the IconLabel has a description the height of the row is `22.5px` instead of `22px`.
| 106 |
221264
|
Background colour contributions for some `testing` UI elements do not have any effect
|
2024-07-09 12:03:12+00:00
|
It looks like the background-related colour contribution points for `testing` UI elements do not have any effect. I tested the following ones:
```
testing.message.error.lineBackground
testing.messagePeekHeaderBackground
```
and I assume `testing.message.info.lineBackground` will also not work.
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
Commit: ea1445cc7016315d0f5728f8e8b12a45dc0a7286
Date: 2024-07-01T18:54:18.541Z
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.91.0 Chrome/122.0.6261.156 Electron/29.4.0 Safari/537.36
```
Steps to Reproduce:
1. Set a colour for `testing.message.error.lineBackground`
2. Trigger a test failure
3. Observe the inline error decoration has no background colour
|
Background colour contributions for some `testing` UI elements do not have any effect It looks like the background-related colour contribution points for `testing` UI elements do not have any effect. I tested the following ones:
```
testing.message.error.lineBackground
testing.messagePeekHeaderBackground
```
and I assume `testing.message.info.lineBackground` will also not work.
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
Commit: ea1445cc7016315d0f5728f8e8b12a45dc0a7286
Date: 2024-07-01T18:54:18.541Z
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.91.0 Chrome/122.0.6261.156 Electron/29.4.0 Safari/537.36
```
Steps to Reproduce:
1. Set a colour for `testing.message.error.lineBackground`
2. Trigger a test failure
3. Observe the inline error decoration has no background colour
| 589 |
||
221147
|
allow focusing chat response list via keyboard for terminal chat
|
2024-07-08 15:26:19+00:00
|
> @meganrogge @Tyriar I can't remember what terminal chat looked like in March, do you still want this disabled? I think we probably want it enabled in all chat widgets now: https://github.com/microsoft/vscode/issues/208927
_Originally posted by @roblourens in [#218088](https://github.com/microsoft/vscode/issues/218088#issuecomment-2197419000)_
|
allow focusing chat response list via keyboard for terminal chat > @meganrogge @Tyriar I can't remember what terminal chat looked like in March, do you still want this disabled? I think we probably want it enabled in all chat widgets now: https://github.com/microsoft/vscode/issues/208927
_Originally posted by @roblourens in [#218088](https://github.com/microsoft/vscode/issues/218088#issuecomment-2197419000)_
| 117 |
||
221137
|
Open File via a shortcut in diff editor opens files in read only in some cases
|
2024-07-08 14:07:15+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
- OS Version: Windows 10 10.0.19045 Build 19045
### Steps to Reproduce:
1. Have outgoing changes in your source control view.
2. Click on a file that has changes in a commit to open diff view.
3. Configure a shortcut for the `Open File` action.
4. Press the shortcut.
5. Observe that the file is opened in read only mode.
6. Go back to the diff view and click the `Open File` button with a mouse.
7. Observe that the file opened in writeable mode.
### Expected results:
1. The way the action is invoked should not affect the mode in which the file is opened. I would personally prefer it to always open file in writeable mode if possible.
|
Open File via a shortcut in diff editor opens files in read only in some cases <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
- OS Version: Windows 10 10.0.19045 Build 19045
### Steps to Reproduce:
1. Have outgoing changes in your source control view.
2. Click on a file that has changes in a commit to open diff view.
3. Configure a shortcut for the `Open File` action.
4. Press the shortcut.
5. Observe that the file is opened in read only mode.
6. Go back to the diff view and click the `Open File` button with a mouse.
7. Observe that the file opened in writeable mode.
### Expected results:
1. The way the action is invoked should not affect the mode in which the file is opened. I would personally prefer it to always open file in writeable mode if possible.
| 481 |
||
220271
|
Web extension debug just hangs
|
2024-07-07 06:27:36+00:00
|
2024-07-08 15:16:33+00:00
|
Steps to Reproduce:
1. install latest `yo` and `generator-code`
2. run `yo code` and pick the option to do a web extension
3. open it in VS Code insiders
4. build it
5. hit F5
=> ๐ it just hangs
|
completed
|
Web extension debug just hangs Steps to Reproduce:
1. install latest `yo` and `generator-code`
2. run `yo code` and pick the option to do a web extension
3. open it in VS Code insiders
4. build it
5. hit F5
=> ๐ it just hangs
| 109 |
220139
|
Find (Ctrl+F/cmd+F) matches deleted text
|
2024-07-06 07:17:22+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
- OS Version: macOS Sonoma 14.5
Steps to Reproduce:
1. Paste `foo bar baz`
2. Delete ` baz`
3. Use `Ctrl+F`/`cmd+F` to find `foo bar baz`
|
Find (Ctrl+F/cmd+F) matches deleted text <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
- OS Version: macOS Sonoma 14.5
Steps to Reproduce:
1. Paste `foo bar baz`
2. Delete ` baz`
3. Use `Ctrl+F`/`cmd+F` to find `foo bar baz`
| 377 |
||
220064
|
Raw HTML in a header gets included in its id attribute (in preview mode)
|
2024-07-05 11:53:40+00:00
|
2024-07-15 19:17:12+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0.0
- OS Version: Windows 10 build 19045.4598
Steps to Reproduce:
1. Put a header with a raw HTML element
```md
# <mark>header</mark>
```
2. Raw HTML is included in markdown header anchors (`mark` is included!)
```md
```
|
completed
|
Raw HTML in a header gets included in its id attribute (in preview mode) <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0.0
- OS Version: Windows 10 build 19045.4598
Steps to Reproduce:
1. Put a header with a raw HTML element
```md
# <mark>header</mark>
```
2. Raw HTML is included in markdown header anchors (`mark` is included!)
```md
```
| 400 |
220028
|
Port label not applied when forwarding port with vscode.env.asExternalUri
|
2024-07-05 05:15:42+00:00
|
2024-07-05 12:26:45+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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
- OS Version:
Steps to Reproduce:
1. Forward a port using `vscode.env.asExternalUri`
2. Observe port label from `remote.portsAttributes` settings is not applied
|
completed
|
Port label not applied when forwarding port with vscode.env.asExternalUri <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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
- OS Version:
Steps to Reproduce:
1. Forward a port using `vscode.env.asExternalUri`
2. Observe port label from `remote.portsAttributes` settings is not applied
| 380 |
219984
|
"potential listener LEAK detected" for comment DOM elements that are recreated on every "display" call but not disposed of
|
2024-07-04 15:53:05+00:00
|
2024-07-05 14:28:14+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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: Head
- OS Version: Browser
## Steps to Reproduce:
1. Switch back and forth between the comments panel and some other panel.
This will trigger this warning:
https://github.com/microsoft/vscode/blob/3ce0d742a353b0df2e867b4d4fd531bba4a77395/src/vs/base/common/event.ts#L869
## Likely cause
* The DOM nodes for each comment thread are recreated whenever the comment is displayed, see:
https://github.com/microsoft/vscode/blob/3ce0d742a353b0df2e867b4d4fd531bba4a77395/src/vs/workbench/contrib/comments/browser/commentThreadBody.ts#L73-L104
* The new nodes are registered for cleanup, however to the lifecycle of the CommentThreadBody:
https://github.com/microsoft/vscode/blob/3ce0d742a353b0df2e867b4d4fd531bba4a77395/src/vs/workbench/contrib/comments/browser/commentThreadBody.ts#L259-L270
* This means they are eventually cleaned up, but only when the entire comment thread is cleaned up.
## Possible fix
There is already a separate commentsDisposable, which seems to be used to dispose comments when they are deleted in updateCommentThread. But not when the display function recreates the elements.
|
completed
|
"potential listener LEAK detected" for comment DOM elements that are recreated on every "display" call but not disposed of <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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: Head
- OS Version: Browser
## Steps to Reproduce:
1. Switch back and forth between the comments panel and some other panel.
This will trigger this warning:
https://github.com/microsoft/vscode/blob/3ce0d742a353b0df2e867b4d4fd531bba4a77395/src/vs/base/common/event.ts#L869
## Likely cause
* The DOM nodes for each comment thread are recreated whenever the comment is displayed, see:
https://github.com/microsoft/vscode/blob/3ce0d742a353b0df2e867b4d4fd531bba4a77395/src/vs/workbench/contrib/comments/browser/commentThreadBody.ts#L73-L104
* The new nodes are registered for cleanup, however to the lifecycle of the CommentThreadBody:
https://github.com/microsoft/vscode/blob/3ce0d742a353b0df2e867b4d4fd531bba4a77395/src/vs/workbench/contrib/comments/browser/commentThreadBody.ts#L259-L270
* This means they are eventually cleaned up, but only when the entire comment thread is cleaned up.
## Possible fix
There is already a separate commentsDisposable, which seems to be used to dispose comments when they are deleted in updateCommentThread. But not when the display function recreates the elements.
| 692 |
219979
|
Shell integration decoration is not vertically centered when terminal line height is set
|
2024-07-04 15:26:07+00:00
|
2024-07-04 16:36:02+00:00
|
Repro:
1. Open terminal
2. Set `"terminal.integrated.lineHeight": 2`
Note that this only applies right after setting the line height, it works when you run a command after that.
|
completed
|
Shell integration decoration is not vertically centered when terminal line height is set Repro:
1. Open terminal
2. Set `"terminal.integrated.lineHeight": 2`
Note that this only applies right after setting the line height, it works when you run a command after that.
| 105 |
219970
|
Terminal sparkle is cut off
|
2024-07-04 14:31:05+00:00
|
2024-07-04 16:13:03+00:00
|
* have side by side terminal
* trigger the sparkle in the RHS
* :bug: it isn't fully visible
|
completed
|
Terminal sparkle is cut off * have side by side terminal
* trigger the sparkle in the RHS
* :bug: it isn't fully visible
| 75 |
219953
|
Empty source control panel using scm.experimental.showHistoryGraph
|
2024-07-04 12:38:53+00:00
|
2024-07-10 13:34:36+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0 (user setup)
- OS Version: Windows_NT x64 10.0.22631
Steps to Reproduce:
1. Turn on **scm.experimental.showHistoryGraph**
2. Open another editor
3. Create modifications to populate source control pending modifications
--> Source control shows 'X' modifications pending on icon but is emtpy
|
completed
|
Empty source control panel using scm.experimental.showHistoryGraph <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0 (user setup)
- OS Version: Windows_NT x64 10.0.22631
Steps to Reproduce:
1. Turn on **scm.experimental.showHistoryGraph**
2. Open another editor
3. Create modifications to populate source control pending modifications
--> Source control shows 'X' modifications pending on icon but is emtpy
| 399 |
219946
|
Quick pick is showing mixed states
|
2024-07-04 11:57:41+00:00
|
2024-07-17 23:39:27+00:00
|
- Open Command Pallette
- Type `Dele` and press Enter
๐ For a moment, quick pick shows check boxes for currently shown commands and after shows the correct state.
Please check the following video:
https://github.com/user-attachments/assets/1145bc4c-8026-46a5-bd37-eb2e94aee0a9
|
completed
|
Quick pick is showing mixed states - Open Command Pallette
- Type `Dele` and press Enter
๐ For a moment, quick pick shows check boxes for currently shown commands and after shows the correct state.
Please check the following video:
https://github.com/user-attachments/assets/1145bc4c-8026-46a5-bd37-eb2e94aee0a9
| 91 |
219941
|
The devcontainer extensions do not work with a custom profile
|
2024-07-04 10:40:36+00:00
|
2024-07-10 09:43:09+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0 (Universal)
- OS Version: Darwin arm64 23.5.0
Steps to Reproduce:
1. create new profile test
2. switch to new profile
3. Open in Devcontainer
devcontainer.json sample
```json
{
"name": "Alpine",
"image": "mcr.microsoft.com/devcontainers/base:alpine-3.20",
"customizations": {
"vscode": {
"extensions": [
"dbaeumer.vscode-eslint"
]
}
}
}
```
**container is loaded without extensions.**
Opening in DevContainer with the default profile works correctly.
Works correctly with the previous version of vscode 1.90.2
|
completed
|
The devcontainer extensions do not work with a custom profile <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0 (Universal)
- OS Version: Darwin arm64 23.5.0
Steps to Reproduce:
1. create new profile test
2. switch to new profile
3. Open in Devcontainer
devcontainer.json sample
```json
{
"name": "Alpine",
"image": "mcr.microsoft.com/devcontainers/base:alpine-3.20",
"customizations": {
"vscode": {
"extensions": [
"dbaeumer.vscode-eslint"
]
}
}
}
```
**container is loaded without extensions.**
Opening in DevContainer with the default profile works correctly.
Works correctly with the previous version of vscode 1.90.2
| 476 |
221699
|
Add setting to change the reply font
|
2024-07-04 10:12:11+00:00
|
2024-07-15 09:52:37+00:00
|
First of all, apologies for the small screenshot, I can't share more as it's a private repo.
It does illustrate my point, I use Berkeley Mono for the code and would like to use it for the replies as well, since they're already using the monospaced Menlo.
I searched for a `githubPullRequests.replyFont` or similar and couldn't find anything. Outside the extension, the same.
|
completed
|
Add setting to change the reply font First of all, apologies for the small screenshot, I can't share more as it's a private repo.
It does illustrate my point, I use Berkeley Mono for the code and would like to use it for the replies as well, since they're already using the monospaced Menlo.
I searched for a `githubPullRequests.replyFont` or similar and couldn't find anything. Outside the extension, the same.
| 181 |
219924
|
Notebook cell comment is picked only from the first owner/provider
|
2024-07-04 07:37:27+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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: Head
- OS Version: Any
Steps to Reproduce:
1. Have two comment providers.
2. Make the first one return no comments for a cell, and the second one return a comment for that cell.
Expected:
The one comment from the second owner is picked.
Actual:
No comment is shown, because we only check the first provider if it has a comment.
See:
https://github.com/microsoft/vscode/blob/d69a8fb36d408b6bd89197668ba3b039d5f9bb91/src/vs/workbench/contrib/notebook/browser/view/cellParts/cellComments.ts#L138-L142
I will send a PR to fix that.
|
Notebook cell comment is picked only from the first owner/provider <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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: Head
- OS Version: Any
Steps to Reproduce:
1. Have two comment providers.
2. Make the first one return no comments for a cell, and the second one return a comment for that cell.
Expected:
The one comment from the second owner is picked.
Actual:
No comment is shown, because we only check the first provider if it has a comment.
See:
https://github.com/microsoft/vscode/blob/d69a8fb36d408b6bd89197668ba3b039d5f9bb91/src/vs/workbench/contrib/notebook/browser/view/cellParts/cellComments.ts#L138-L142
I will send a PR to fix that.
| 481 |
||
219916
|
bug: vscode terminal has a redundant blank line
|
2024-07-04 03:58:28+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
- OS Version: macos 1.15.0 beta + remote ssh
Steps to Reproduce:
1. see the video
https://github.com/microsoft/vscode/assets/10379994/740aeb95-84d8-4fcc-b595-4c71ba00f964
|
bug: vscode terminal has a redundant blank line <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0
- OS Version: macos 1.15.0 beta + remote ssh
Steps to Reproduce:
1. see the video
https://github.com/microsoft/vscode/assets/10379994/740aeb95-84d8-4fcc-b595-4c71ba00f964
| 382 |
||
219893
|
v1.91 does not launch on Catalina or Big Sur due to Fatal error in V8
|
2024-07-03 20:32:23+00:00
|
2024-07-08 12:34:09+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91
- OS Version: Mac OS Catalina
Steps to Reproduce:
1. Launch 1.91 on Mac OS Catalina, VSCode will crash. If you try launching from the command line, you'll see the following error: "Fatal error in V8: v8::Template::Set Invalid value, must be a primitive or a Template"
I know this is an old version of Mac OS, but if an OS will no longer be supported then perhaps it shouldn't update automatically. This particular installation is a developer test machine that won't/can't be updated past Catalina.
|
completed
|
v1.91 does not launch on Catalina or Big Sur due to Fatal error in V8 <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91
- OS Version: Mac OS Catalina
Steps to Reproduce:
1. Launch 1.91 on Mac OS Catalina, VSCode will crash. If you try launching from the command line, you'll see the following error: "Fatal error in V8: v8::Template::Set Invalid value, must be a primitive or a Template"
I know this is an old version of Mac OS, but if an OS will no longer be supported then perhaps it shouldn't update automatically. This particular installation is a developer test machine that won't/can't be updated past Catalina.
| 457 |
219892
|
Blank space on right of new terminals
|
2024-07-03 20:28:23+00:00
|
2024-07-12 17:02:05+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes (tested after recording the video)
<!-- ๐ช 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.91.0
- OS Version: macOS 14.5 (23F79)
Steps to Reproduce:
1. Open a new terminal (editor or panel)
2. Notice a blank space on the right side of the terminal (seems to scale proportional to window width)
3. Resize the terminal
4. Notice the blank space is filled and terminal is sized correctly
## Video
https://github.com/microsoft/vscode/assets/6618434/96efea25-672d-41e5-8b88-1a482d5599fe
|
completed
|
Blank space on right of new terminals <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes (tested after recording the video)
<!-- ๐ช 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.91.0
- OS Version: macOS 14.5 (23F79)
Steps to Reproduce:
1. Open a new terminal (editor or panel)
2. Notice a blank space on the right side of the terminal (seems to scale proportional to window width)
3. Resize the terminal
4. Notice the blank space is filled and terminal is sized correctly
## Video
https://github.com/microsoft/vscode/assets/6618434/96efea25-672d-41e5-8b88-1a482d5599fe
| 435 |
219877
|
Source control icon flashes every second if "Autofetch period" is set to 1
|
2024-07-03 18:18:42+00:00
|
2024-07-04 10:56:56+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0 (user setup)
Commit: ea1445cc7016315d0f5728f8e8b12a45dc0a7286
Date: 2024-07-01T18:52:22.949Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22621
- OS Version: Windows 11
Steps to Reproduce:
1. Set `Git: Autofetch` to `true`
2. Set `Git: Autofetch period` to `1`
3. Look at the `Source control` icon
https://github.com/microsoft/vscode/assets/29142494/9d0be9d4-e9b1-4edb-a05c-0385860a87b1
I'm not sure if it's a new feature or a bug, but it wasn't like that in previous version (1.90).
|
completed
|
Source control icon flashes every second if "Autofetch period" is set to 1 <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0 (user setup)
Commit: ea1445cc7016315d0f5728f8e8b12a45dc0a7286
Date: 2024-07-01T18:52:22.949Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22621
- OS Version: Windows 11
Steps to Reproduce:
1. Set `Git: Autofetch` to `true`
2. Set `Git: Autofetch period` to `1`
3. Look at the `Source control` icon
https://github.com/microsoft/vscode/assets/29142494/9d0be9d4-e9b1-4edb-a05c-0385860a87b1
I'm not sure if it's a new feature or a bug, but it wasn't like that in previous version (1.90).
| 545 |
219876
|
select a language option is not working
|
2024-07-03 17:59:07+00:00
|
2024-07-04 15:20:08+00:00
|
Type: <b>Bug</b>
the select a language button on a new file is not working neither giving any output or giving any option to select the languages available
VS Code version: Code 1.91.0 (ea1445cc7016315d0f5728f8e8b12a45dc0a7286, 2024-07-01T18:52:22.949Z)
OS version: Windows_NT x64 10.0.22621
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz (8 x 2712)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|15.85GB (6.63GB free)|
|Process Argv|--crash-reporter-id 9573c142-cc88-42d4-9188-6be0e3f36307|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (13)</summary>
Extension|Author (truncated)|Version
---|---|---
blackbox|Bla|1.3.61
uncanny-cognitive-complexity|Dab|1.2.0
copilot|Git|1.209.0
copilot-chat|Git|0.17.0
debugpy|ms-|2024.6.0
python|ms-|2024.8.1
vscode-pylance|ms-|2024.6.1
cmake-tools|ms-|1.18.42
cpptools|ms-|1.20.5
cpptools-extension-pack|ms-|1.3.0
vscode-numpy-viewer|Per|0.1.8
cmake|twx|0.0.17
incredibly-in-your-face|Vir|1.0.2
(1 theme extensions excluded)
</details><details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
vscrp:30673768
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31067544
chatpanelc:31048052
dsvsc021:30996838
jg8ic977:31013176
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
legacy_priority:31082724
```
</details>
<!-- generated by issue reporter -->
|
completed
|
select a language option is not working Type: <b>Bug</b>
the select a language button on a new file is not working neither giving any output or giving any option to select the languages available
VS Code version: Code 1.91.0 (ea1445cc7016315d0f5728f8e8b12a45dc0a7286, 2024-07-01T18:52:22.949Z)
OS version: Windows_NT x64 10.0.22621
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz (8 x 2712)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|15.85GB (6.63GB free)|
|Process Argv|--crash-reporter-id 9573c142-cc88-42d4-9188-6be0e3f36307|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (13)</summary>
Extension|Author (truncated)|Version
---|---|---
blackbox|Bla|1.3.61
uncanny-cognitive-complexity|Dab|1.2.0
copilot|Git|1.209.0
copilot-chat|Git|0.17.0
debugpy|ms-|2024.6.0
python|ms-|2024.8.1
vscode-pylance|ms-|2024.6.1
cmake-tools|ms-|1.18.42
cpptools|ms-|1.20.5
cpptools-extension-pack|ms-|1.3.0
vscode-numpy-viewer|Per|0.1.8
cmake|twx|0.0.17
incredibly-in-your-face|Vir|1.0.2
(1 theme extensions excluded)
</details><details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
vscrp:30673768
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31067544
chatpanelc:31048052
dsvsc021:30996838
jg8ic977:31013176
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
legacy_priority:31082724
```
</details>
<!-- generated by issue reporter -->
| 981 |
219875
|
Completions sometimes repeat existing input
|
2024-07-03 17:29:00+00:00
|
2024-07-17 20:24:21+00:00
|
|
completed
|
Completions sometimes repeat existing input 
| 61 |
219871
|
Use MSALjs for the `vscode.dev/azurerepos` route
|
2024-07-03 15:40:58+00:00
|
We have received reports around Conditional Access where users are unable to use this route do to our existing Microsoft auth support in vscode.dev.
We should consider enabling MSAL-based auth for this route.
Upsides:
* Conditional Access will be happy
Downsides:
* Sessions can only last 24hrs before the page needs to be refreshed
Since the downsides are being seen more and more as a feature request these days, we should probably just make this change...
|
Use MSALjs for the `vscode.dev/azurerepos` route We have received reports around Conditional Access where users are unable to use this route do to our existing Microsoft auth support in vscode.dev.
We should consider enabling MSAL-based auth for this route.
Upsides:
* Conditional Access will be happy
Downsides:
* Sessions can only last 24hrs before the page needs to be refreshed
Since the downsides are being seen more and more as a feature request these days, we should probably just make this change...
| 125 |
||
219843
|
WordOperations test failure on firefox
|
2024-07-03 09:56:15+00:00
|
* run `yarn test-browser`
* ๐ there are test failures for firefox
```
8739 passing (2m)
80 pending
2 failing
1) WordOperations
cursorWordLeft - Recognize words:
+ expected - actual
-|/* |ใใใฏใในใใงใ |/*
+|/* |ใใ|ใฏ|ใในใ|ใงใ |/*
AssertionError@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/test/unit/assert.js:184:21
fail@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/test/unit/assert.js:231:9
deepStrictEqual@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/test/unit/assert.js:283:9
@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/out/vs/editor/contrib/wordOperations/test/browser/wordOperations.test.js:151:30
2) WordOperations
cursorWordRight - Recognize words:
+ expected - actual
-/*| ใใใฏใในใใงใ|/*|
+/*| ใใ|ใฏ|ใในใ|ใงใ|/*|
AssertionError@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/test/unit/assert.js:184:21
fail@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/test/unit/assert.js:231:9
deepStrictEqual@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/test/unit/assert.js:283:9
@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/out/vs/editor/contrib/wordOperations/test/browser/wordOperations.test.js:298:30
The followings tests are failing:
- WordOperations cursorWordLeft - Recognize words (reason: "|/* |ใใใฏใในใใงใ |/*" deepStrictEqual "|/* |ใใ|ใฏ|ใในใ|ใงใ |/*")
- WordOperations cursorWordRight - Recognize words (reason: "/*| ใใใฏใในใใงใ|/*|" deepStrictEqual "/*| ใใ|ใฏ|ใในใ|ใงใ|/*|")
```
|
WordOperations test failure on firefox * run `yarn test-browser`
* ๐ there are test failures for firefox
```
8739 passing (2m)
80 pending
2 failing
1) WordOperations
cursorWordLeft - Recognize words:
+ expected - actual
-|/* |ใใใฏใในใใงใ |/*
+|/* |ใใ|ใฏ|ใในใ|ใงใ |/*
AssertionError@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/test/unit/assert.js:184:21
fail@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/test/unit/assert.js:231:9
deepStrictEqual@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/test/unit/assert.js:283:9
@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/out/vs/editor/contrib/wordOperations/test/browser/wordOperations.test.js:151:30
2) WordOperations
cursorWordRight - Recognize words:
+ expected - actual
-/*| ใใใฏใในใใงใ|/*|
+/*| ใใ|ใฏ|ใในใ|ใงใ|/*|
AssertionError@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/test/unit/assert.js:184:21
fail@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/test/unit/assert.js:231:9
deepStrictEqual@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/test/unit/assert.js:283:9
@http://localhost:58336/d93b92392c197e0dc1687e5c26f3e699/out/vs/editor/contrib/wordOperations/test/browser/wordOperations.test.js:298:30
The followings tests are failing:
- WordOperations cursorWordLeft - Recognize words (reason: "|/* |ใใใฏใในใใงใ |/*" deepStrictEqual "|/* |ใใ|ใฏ|ใในใ|ใงใ |/*")
- WordOperations cursorWordRight - Recognize words (reason: "/*| ใใใฏใในใใงใ|/*|" deepStrictEqual "/*| ใใ|ใฏ|ใในใ|ใงใ|/*|")
```
| 670 |
||
219821
|
Indent using spaces function does not convert tabs to spaces in mixed indentation text content
|
2024-07-03 06:12:15+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.89.1
- OS Version: Linux
Steps to Reproduce:
1. Open a saved file that has mixed indentation whitespace content (tabs and spaces). ex:
```
test with a tab
test with a space
```
[mixed_indentation_example_file.txt](https://github.com/user-attachments/files/16077831/mixed_indentation_example_file.txt)
2. Ctrl-Shift-P "Indent using spaces", default (4)
I expected this function to convert any tab characters present into the n number of spaces given in the functionality. This is useful for fixing content that has mixed use of whitespace indentation.
workaround: find and replace, regex mode, replace `\t` with four spaces ` `
[NO_TRAIN]::
|
Indent using spaces function does not convert tabs to spaces in mixed indentation text content <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.89.1
- OS Version: Linux
Steps to Reproduce:
1. Open a saved file that has mixed indentation whitespace content (tabs and spaces). ex:
```
test with a tab
test with a space
```
[mixed_indentation_example_file.txt](https://github.com/user-attachments/files/16077831/mixed_indentation_example_file.txt)
2. Ctrl-Shift-P "Indent using spaces", default (4)
I expected this function to convert any tab characters present into the n number of spaces given in the functionality. This is useful for fixing content that has mixed use of whitespace indentation.
workaround: find and replace, regex mode, replace `\t` with four spaces ` `
[NO_TRAIN]::
| 511 |
||
219814
|
Text cursor disappears automatically from Jupyter Notebook cell
|
2024-07-03 02:26:42+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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. -->
Text cursor disappears automatically from Jupyter Notebook cell two seconds after not typing. The original reporter was using Remote, it could be a document update from the remote extension host which triggers the editor to refresh.
|
Text cursor disappears automatically from Jupyter Notebook cell <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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. -->
Text cursor disappears automatically from Jupyter Notebook cell two seconds after not typing. The original reporter was using Remote, it could be a document update from the remote extension host which triggers the editor to refresh.
| 356 |
||
219705
|
Profiles: Changing the `Copy from` picker erases the profile name
|
2024-07-02 15:32:34+00:00
|
2024-07-03 18:54:44+00:00
|
1. Open Profiles editor
2. Click `New Profile`
3. Type a name for the new profile
4. Change the `Copy from` picker to `Default`
๐ You lost the name typed in step 3
|
completed
|
Profiles: Changing the `Copy from` picker erases the profile name 1. Open Profiles editor
2. Click `New Profile`
3. Type a name for the new profile
4. Change the `Copy from` picker to `Default`
๐ You lost the name typed in step 3
| 66 |
219713
|
Copilot icon covering code in notebooks
|
2024-07-01 22:13:43+00:00
|
The copilot icon popping up and covering code while typing is extremely distracting and annoying. It happens throughout the entire notebook and all cells as typing
## Expected behavior
For code not to be covered by popup icons
## Actual behavior
Code being covered by icons popping up
|
Copilot icon covering code in notebooks The copilot icon popping up and covering code while typing is extremely distracting and annoying. It happens throughout the entire notebook and all cells as typing
## Expected behavior
For code not to be covered by popup icons
## Actual behavior
Code being covered by icons popping up
| 178 |
||
219559
|
Terminal resize freezes computer
|
2024-07-01 15:56:27+00:00
|
2024-07-21 17:44:15+00:00
|
* having a lot of terminal output
* e.g. run `yarn test-browser`
* scroll the terminal to the top
* toggle side bar
* ๐ renderer freezes for multiple seconds in `xterm#resize`
[Trace-20240701T175556.json.zip](https://github.com/user-attachments/files/16056137/Trace-20240701T175556.json.zip)
|
completed
|
Terminal resize freezes computer * having a lot of terminal output
* e.g. run `yarn test-browser`
* scroll the terminal to the top
* toggle side bar
* ๐ renderer freezes for multiple seconds in `xterm#resize`
[Trace-20240701T175556.json.zip](https://github.com/user-attachments/files/16056137/Trace-20240701T175556.json.zip)
| 149 |
219542
|
Inline chat with sticky scroll looses top area
|
2024-07-01 13:41:48+00:00
|
Steps to Reproduce:
1. bring up inline chat with a lengthy response
2. make sure sticky scroll is enabled
3. notice how when inline chat widget grows up, the top part moves out of sight
//cc @aiday-mar
|
Inline chat with sticky scroll looses top area Steps to Reproduce:
1. bring up inline chat with a lengthy response
2. make sure sticky scroll is enabled
3. notice how when inline chat widget grows up, the top part moves out of sight
//cc @aiday-mar
| 152 |
||
219531
|
Clicking `X` on a inline chat response still shows buttons like "View in Chat"
|
2024-07-01 13:25:42+00:00
|
Steps to Reproduce:
1. have a inline chat response
2. click the "X" button to remove the chat [1]
3. you still have the buttons from the response, when I would have expected just no buttons [2]
[1]
[2]
|
Clicking `X` on a inline chat response still shows buttons like "View in Chat" Steps to Reproduce:
1. have a inline chat response
2. click the "X" button to remove the chat [1]
3. you still have the buttons from the response, when I would have expected just no buttons [2]
[1]
[2]
| 157 |
||
219336
|
Telemetry for window.newWindowProfile and extensions.autoRestart setting changes are getting reported using different event
|
2024-07-01 09:48:26+00:00
|
2024-07-01 14:37:48+00:00
|
Steps to Reproduce:
1. Enable Log Level to Trace and Open Telemetry Output view
2. Change the value of `window.newWindowProfile` or `extensions.autoRestart` setting
๐ These changes are being reported using `window.systemColorTheme` event.
|
completed
|
Telemetry for window.newWindowProfile and extensions.autoRestart setting changes are getting reported using different event Steps to Reproduce:
1. Enable Log Level to Trace and Open Telemetry Output view
2. Change the value of `window.newWindowProfile` or `extensions.autoRestart` setting
๐ These changes are being reported using `window.systemColorTheme` event.
| 97 |
219330
|
Git Commit Graph: 2 Parallel branches have the same color
|
2024-07-01 08:11:34+00:00
|
In the following image you can see that there are two branches next to each other with the same colour. I believe this is not by design?
Here the rest of the history for additional context:
|
Git Commit Graph: 2 Parallel branches have the same color In the following image you can see that there are two branches next to each other with the same colour. I believe this is not by design?
Here the rest of the history for additional context:
| 141 |
||
219210
|
Quick Pick imprecise filtering breaks after 60 characters
|
2024-06-28 20:05:34+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0-Insiders, 1.90.2
- OS Version: Windows 11, Ubuntu 18 (in WSL)
The filtering for quick pick items which lets you skip characters or words seems to not work on longer strings. Filtering does not work after the 60th character in the string (it seems).
Steps to Reproduce:
1. Create a quick pick menu with these options:
```
await vscode.window.showQuickPick([
"Alpha Bravo Charlie Delta Echo Foxtrot Golf Hotel India Juliett Kilo Lima Mike November Oscar Papa Quebec Romeo Sierra Tango Uniform Victor Whiskey X-ray Yankee Zulu",
"alpha bravo charlie delta echo foxtrot golf hotel india juliett kilo lima mike november oscar papa quebec romeo sierra tango uniform victor whiskey x-ray yankee zulu"
], {
canPickMany: false,
title: "Example",
});
```
2. In the search bar, type: "Alpha Juli". Both options will remain unfiltered and the strings "Alpha" and "Juli" will be highlighted separately:
3. Type "e". Both options now get filtered:
4. All imprecise searching seems to break after the 60th character (which is the 'e' in 'Juliett'):
https://github.com/microsoft/vscode/assets/56779108/4b888c64-cb6f-4af0-a876-e6b7d30214c6
|
Quick Pick imprecise filtering breaks after 60 characters <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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.91.0-Insiders, 1.90.2
- OS Version: Windows 11, Ubuntu 18 (in WSL)
The filtering for quick pick items which lets you skip characters or words seems to not work on longer strings. Filtering does not work after the 60th character in the string (it seems).
Steps to Reproduce:
1. Create a quick pick menu with these options:
```
await vscode.window.showQuickPick([
"Alpha Bravo Charlie Delta Echo Foxtrot Golf Hotel India Juliett Kilo Lima Mike November Oscar Papa Quebec Romeo Sierra Tango Uniform Victor Whiskey X-ray Yankee Zulu",
"alpha bravo charlie delta echo foxtrot golf hotel india juliett kilo lima mike november oscar papa quebec romeo sierra tango uniform victor whiskey x-ray yankee zulu"
], {
canPickMany: false,
title: "Example",
});
```
2. In the search bar, type: "Alpha Juli". Both options will remain unfiltered and the strings "Alpha" and "Juli" will be highlighted separately:
3. Type "e". Both options now get filtered:
4. All imprecise searching seems to break after the 60th character (which is the 'e' in 'Juliett'):
https://github.com/microsoft/vscode/assets/56779108/4b888c64-cb6f-4af0-a876-e6b7d30214c6
| 739 |
||
219199
|
Tab gets stuck in Problems filter input
|
2024-06-28 19:31:55+00:00
|
> The code I linked is related to a separate issue that I saw, which probably isn't really related to what you fixed. But if I put focus in the Problems or Debug Console filter input, and do some combination of tab out of the input, shift+tab back into it, type in it, then at some point focus gets stuck in the widget and 'tab' doesn't move focus out to the next toolbar.
_Originally posted in [#211979](https://github.com/microsoft/vscode/issues/211979#issuecomment-2187963936)_
|
Tab gets stuck in Problems filter input > The code I linked is related to a separate issue that I saw, which probably isn't really related to what you fixed. But if I put focus in the Problems or Debug Console filter input, and do some combination of tab out of the input, shift+tab back into it, type in it, then at some point focus gets stuck in the widget and 'tab' doesn't move focus out to the next toolbar.
_Originally posted in [#211979](https://github.com/microsoft/vscode/issues/211979#issuecomment-2187963936)_
| 139 |
||
219128
|
autoSurround fails for white-space only selections
|
2024-06-28 15:27:07+00:00
|
Type: <b>Bug</b>
## STR
0. Ensure `editor.autoSurround` is enabled (by default it is enabled).
1. Create file and set syntax to MarkDown.
2. Type a space.
3. Select the space.
4. Press `[`.
## Expected outcome
`[ ]` (a.k.a. "Markdown checkbox") produced.
## Actual outcome
`[` Produced. I.e. the selected space is simply overwritten, instead of surrounded by a bracket pair, like any other non-white-space selection is.
---
// Anecdotally, I am not fond much about this pref since I am more used to overwrite selections instead of deleting them, and I am constantly running into this feature when my intention is to replace selection with **single** bracket and then end up with the text being selected and surrounded instead. I'm just testing if I will get used to enabled `editor.autoSurround`, and paradoxically, maybe I'd appreciate the white-space autoSurround more than non-whitespace.
---
VS Code version: Code 1.90.2 (5437499feb04f7a586f677b155b039bc2b3669eb, 2024-06-18T22:34:26.404Z)
OS version: Windows_NT x64 10.0.19045
Modes:
<!-- generated by issue reporter -->
|
autoSurround fails for white-space only selections Type: <b>Bug</b>
## STR
0. Ensure `editor.autoSurround` is enabled (by default it is enabled).
1. Create file and set syntax to MarkDown.
2. Type a space.
3. Select the space.
4. Press `[`.
## Expected outcome
`[ ]` (a.k.a. "Markdown checkbox") produced.
## Actual outcome
`[` Produced. I.e. the selected space is simply overwritten, instead of surrounded by a bracket pair, like any other non-white-space selection is.
---
// Anecdotally, I am not fond much about this pref since I am more used to overwrite selections instead of deleting them, and I am constantly running into this feature when my intention is to replace selection with **single** bracket and then end up with the text being selected and surrounded instead. I'm just testing if I will get used to enabled `editor.autoSurround`, and paradoxically, maybe I'd appreciate the white-space autoSurround more than non-whitespace.
---
VS Code version: Code 1.90.2 (5437499feb04f7a586f677b155b039bc2b3669eb, 2024-06-18T22:34:26.404Z)
OS version: Windows_NT x64 10.0.19045
Modes:
<!-- generated by issue reporter -->
| 327 |
||
219123
|
Cut node fade applies to all inline folders
|
2024-06-28 15:17:43+00:00
|
โ
What a single cut item looks like:
๐ What a condensed cut item looks like:
It should only fade `base` in this case, not `vs \`
|
Cut node fade applies to all inline folders โ
What a single cut item looks like:
๐ What a condensed cut item looks like:
It should only fade `base` in this case, not `vs \`
| 137 |
||
219122
|
TreeError [FileExplorer] Data tree node not found: ExplorerItem: base
|
2024-06-28 15:16:37+00:00
|
What I did:
1. Click vs\base (this was in the xterm.js codebase, experimenting with pulling some vscode sources in)
2. Ctrl+x
3. Click common (vs\base\common)
4. Ctrl+x, :bug: error
|
TreeError [FileExplorer] Data tree node not found: ExplorerItem: base What I did:
1. Click vs\base (this was in the xterm.js codebase, experimenting with pulling some vscode sources in)
2. Ctrl+x
3. Click common (vs\base\common)
4. Ctrl+x, :bug: error
| 118 |
||
219091
|
Have to click "stop" action multiple times
|
2024-06-28 11:39:41+00:00
|
I feel like I mostly see this when debugging an extension. This doesn't happen every time.
1. Start debugging an extension (I'm usually using https://github.com/microsoft/vscode-pull-request-github)
2. Make a change to the extension code (this step may not be needed)
3. From the ext dev host window, run the Developer: Reload Window command
4. Repeat steps 2 and 3 at least once more
5. In your debugger window, click the "stop" action in the debug toolbar
6. It sometimes takes multiple clicks to actually stop the debugger
// cc @hediet since you've also seen this.
|
Have to click "stop" action multiple times I feel like I mostly see this when debugging an extension. This doesn't happen every time.
1. Start debugging an extension (I'm usually using https://github.com/microsoft/vscode-pull-request-github)
2. Make a change to the extension code (this step may not be needed)
3. From the ext dev host window, run the Developer: Reload Window command
4. Repeat steps 2 and 3 at least once more
5. In your debugger window, click the "stop" action in the debug toolbar
6. It sometimes takes multiple clicks to actually stop the debugger
// cc @hediet since you've also seen this.
| 160 |
||
219047
|
`The drag and drop` function is no longer functional in the latest code
|
2024-06-28 00:54:18+00:00
|
2024-07-08 20:40:48+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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. -->
work success
```
Version: 1.90.2
Commit: Unknown
Date: Unknown
Electron: 29.4.0
ElectronBuildId: undefined
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.5.0-41-generic
```
work failed
```
Version: 1.91.0
Commit: Unknown
Date: Unknown
Electron: 29.4.0
ElectronBuildId: undefined
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.5.0-41-generic
```
This issue occurs when opening a webview type window while developing extensions
Steps to Reproduce:
1. I use mdn demo https://mdn.github.io/dom-examples/drag-and-drop/copy-move-DataTransfer.html
2. add html to webview html
3. open webview .`dragover` loss,and can't drop
I use `tag 1.90.2` compile and run vscode-oss work .but use latest commit `aea213b7fcc7de5c24ad797ac1af209b159d451f` doesn't work.
|
completed
|
`The drag and drop` function is no longer functional in the latest code <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` 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. -->
work success
```
Version: 1.90.2
Commit: Unknown
Date: Unknown
Electron: 29.4.0
ElectronBuildId: undefined
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.5.0-41-generic
```
work failed
```
Version: 1.91.0
Commit: Unknown
Date: Unknown
Electron: 29.4.0
ElectronBuildId: undefined
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.5.0-41-generic
```
This issue occurs when opening a webview type window while developing extensions
Steps to Reproduce:
1. I use mdn demo https://mdn.github.io/dom-examples/drag-and-drop/copy-move-DataTransfer.html
2. add html to webview html
3. open webview .`dragover` loss,and can't drop
I use `tag 1.90.2` compile and run vscode-oss work .but use latest commit `aea213b7fcc7de5c24ad797ac1af209b159d451f` doesn't work.
| 611 |
219031
|
setting a breakpoint on a moved line in ts hit a breakpoint in js
|
2024-06-27 21:32:07+00:00
|
2024-06-28 16:21:25+00:00
|
Steps to Reproduce:
1. Debug a typescript project
2. add a newline to a ts file
3. add a breakpoint below the newline
4. reload the project being debugged
:bug: associated js file opens for a breakpoint at the top of that file
This happens more often than just these specific steps, but this is a consistent repro for me
|
completed
|
setting a breakpoint on a moved line in ts hit a breakpoint in js Steps to Reproduce:
1. Debug a typescript project
2. add a newline to a ts file
3. add a breakpoint below the newline
4. reload the project being debugged
:bug: associated js file opens for a breakpoint at the top of that file
This happens more often than just these specific steps, but this is a consistent repro for me
| 96 |
219006
|
Open File button in Refactor Preview diff opens temp result instead of the file
|
2024-06-27 20:49:11+00:00
|
2024-07-05 12:38:22+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: No (My repro requires a Rename provider that returns unconfirmed results)
<!-- ๐ช 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.91.0-insider (user setup)
Commit: cb9d1e4589a05bed292f298acba7369e812f8cf1
Date: 2024-06-27T05:50:21.997Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22631
The "Open File" button in the Refactor Preview diff view seems to be opening the wrong 'file'. Instead of opening the existing file, it opens temporary rename preview results for the file. Given that the button is titled just "Open File", I would expect it to open the file and not the temp contents.
https://github.com/microsoft/vscode/assets/49173979/2889ec58-5ab3-4d58-b9d8-717b7303a1bb
|
completed
|
Open File button in Refactor Preview diff opens temp result instead of the file <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: No (My repro requires a Rename provider that returns unconfirmed results)
<!-- ๐ช 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.91.0-insider (user setup)
Commit: cb9d1e4589a05bed292f298acba7369e812f8cf1
Date: 2024-06-27T05:50:21.997Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22631
The "Open File" button in the Refactor Preview diff view seems to be opening the wrong 'file'. Instead of opening the existing file, it opens temporary rename preview results for the file. Given that the button is titled just "Open File", I would expect it to open the file and not the temp contents.
https://github.com/microsoft/vscode/assets/49173979/2889ec58-5ab3-4d58-b9d8-717b7303a1bb
| 552 |
218905
|
Improve UI when having no reply
|
2024-06-27 15:24:18+00:00
|
* have the code snippet below
* start inline chat and ask "change a to a"
* we don't get a code change but the presentation isn't the best
<img width="580" alt="Screenshot 2024-06-27 at 17 21 50" src="https://github.com/user-attachments/assets/bde5e949-f6d3-450d-8aa1-a6cb89ce62a6">
### Sample
```
export function div(a, b) {
return a / b;
}
```
|
Improve UI when having no reply * have the code snippet below
* start inline chat and ask "change a to a"
* we don't get a code change but the presentation isn't the best
<img width="580" alt="Screenshot 2024-06-27 at 17 21 50" src="https://github.com/user-attachments/assets/bde5e949-f6d3-450d-8aa1-a6cb89ce62a6">
### Sample
```
export function div(a, b) {
return a / b;
}
```
| 139 |
||
218897
|
Option to automatically change the debug toolbar's selected active session when launching a new debug session
|
2024-06-27 15:12:39+00:00
|
<!-- โ ๏ธโ ๏ธ Do Not Delete This! feature_request_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Describe the feature you'd like. -->
When a debug session is active (running) and a new debug session is started, it would we nice if there was an option to automatically change the selected session dropdown in the debug toolbar to the newly launched session so it can be paused, restarted, stopped, etc.
Right now, if I have session A running and launch a new session B, if I want to stop B, I have to first go to the toolbar and change the session dropdown from A to B, and then I can stop B. If B has gone awry, it would be nice if the debug toolbar was automatically set to B so it can be immediately paused/stopped/etc (without having to manually change the active session in the debug toolbar dropdown)
Thanks
|
Option to automatically change the debug toolbar's selected active session when launching a new debug session <!-- โ ๏ธโ ๏ธ Do Not Delete This! feature_request_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Describe the feature you'd like. -->
When a debug session is active (running) and a new debug session is started, it would we nice if there was an option to automatically change the selected session dropdown in the debug toolbar to the newly launched session so it can be paused, restarted, stopped, etc.
Right now, if I have session A running and launch a new session B, if I want to stop B, I have to first go to the toolbar and change the session dropdown from A to B, and then I can stop B. If B has gone awry, it would be nice if the debug toolbar was automatically set to B so it can be immediately paused/stopped/etc (without having to manually change the active session in the debug toolbar dropdown)
Thanks
| 281 |
||
218804
|
Missing separator between command and prompt
|
2024-06-27 12:12:31+00:00
|
2024-06-27 12:45:54+00:00
|
* open inline chat
* type `/expl`, accept suggestion and type `this`
* :bug: you know have "/explainthis" even tho it isn't rendered as such
|
completed
|
Missing separator between command and prompt * open inline chat
* type `/expl`, accept suggestion and type `this`
* :bug: you know have "/explainthis" even tho it isn't rendered as such
| 98 |
218628
|
Branch list is sometimes out of order
|
2024-06-26 23:08:22+00:00
|
2024-07-03 14:11:59+00:00
|
Type: <b>Bug</b>
1. Open a workspace
2. Quickly open the branch picker and type `main`
**Bug**
The first time you do this, sometimes you end up with an unordered list:
The correct order shows up when you keep start typing or try doing this again:
VS Code version: Code - Insiders 1.91.0-insider (Universal) (0354163c1c66b950b0762364f5b4cd37937b624a, 2024-06-26T10:12:33.304Z)
OS version: Darwin arm64 23.5.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M2 Max (12 x 2400)|
|GPU Status|2d_canvas: unavailable_software<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: disabled_software<br>multiple_raster_threads: enabled_on<br>opengl: disabled_off<br>rasterization: disabled_software<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: disabled_software<br>video_encode: disabled_software<br>webgl: unavailable_software<br>webgl2: unavailable_software<br>webgpu: unavailable_software|
|Load (avg)|36, 13, 6|
|Memory (System)|64.00GB (0.08GB free)|
|Process Argv|--crash-reporter-id 0fffb5da-9cd7-46fd-9e7f-a1564e8c5fda|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
|
completed
|
Branch list is sometimes out of order
Type: <b>Bug</b>
1. Open a workspace
2. Quickly open the branch picker and type `main`
**Bug**
The first time you do this, sometimes you end up with an unordered list:
The correct order shows up when you keep start typing or try doing this again:
VS Code version: Code - Insiders 1.91.0-insider (Universal) (0354163c1c66b950b0762364f5b4cd37937b624a, 2024-06-26T10:12:33.304Z)
OS version: Darwin arm64 23.5.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M2 Max (12 x 2400)|
|GPU Status|2d_canvas: unavailable_software<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: disabled_software<br>multiple_raster_threads: enabled_on<br>opengl: disabled_off<br>rasterization: disabled_software<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: disabled_software<br>video_encode: disabled_software<br>webgl: unavailable_software<br>webgl2: unavailable_software<br>webgpu: unavailable_software|
|Load (avg)|36, 13, 6|
|Memory (System)|64.00GB (0.08GB free)|
|Process Argv|--crash-reporter-id 0fffb5da-9cd7-46fd-9e7f-a1564e8c5fda|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
| 567 |
218626
|
[Bug] Drag and Drop files onto extensions also opens the file inside the default application for that file type
|
2024-06-26 21:49:42+00:00
|
Type: <b>Bug</b>
1. clone repo https://github.com/maxbublik/vscode-customeditor-drop
2. press f5 to demo repo
3. drag and drop any file into the extension editor while holding shift
Notes:
I am primarily creating this issue to track the bug I made with https://github.com/microsoft/vscode/pull/209211
VS Code version: Code - OSS Dev 1.91.0 (Commit unknown, Date unknown)
OS version: Windows_NT x64 10.0.22631
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 5800X 8-Core Processor (16 x 3800)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|31.93GB (20.85GB free)|
|Process Argv|. --disable-extension=vscode.vscode-api-tests|
|Screen Reader|no|
|VM|50%|
</details>Extensions disabled
<!-- generated by issue reporter -->
https://github.com/microsoft/vscode/assets/21202515/31579895-e05b-4a5c-9b0e-ddfbc2cf19d5
|
reopened
|
[Bug] Drag and Drop files onto extensions also opens the file inside the default application for that file type
Type: <b>Bug</b>
1. clone repo https://github.com/maxbublik/vscode-customeditor-drop
2. press f5 to demo repo
3. drag and drop any file into the extension editor while holding shift
Notes:
I am primarily creating this issue to track the bug I made with https://github.com/microsoft/vscode/pull/209211
VS Code version: Code - OSS Dev 1.91.0 (Commit unknown, Date unknown)
OS version: Windows_NT x64 10.0.22631
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 5800X 8-Core Processor (16 x 3800)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|31.93GB (20.85GB free)|
|Process Argv|. --disable-extension=vscode.vscode-api-tests|
|Screen Reader|no|
|VM|50%|
</details>Extensions disabled
<!-- generated by issue reporter -->
https://github.com/microsoft/vscode/assets/21202515/31579895-e05b-4a5c-9b0e-ddfbc2cf19d5
| 510 |
|
218427
|
Use the webgl renderer in terminal sticky scroll
|
2024-06-26 16:32:37+00:00
|
2024-06-28 14:00:15+00:00
|
Notice how powerline symbols via custom glyphs don't work above:
The dimensions are also slight off due to this https://github.com/microsoft/vscode/issues/216817
|
completed
|
Use the webgl renderer in terminal sticky scroll Notice how powerline symbols via custom glyphs don't work above:
The dimensions are also slight off due to this https://github.com/microsoft/vscode/issues/216817
| 102 |
218414
|
Terminal inline chat should NOT hide when clicking the terminal or clicking away
|
2024-06-26 16:08:14+00:00
|
Caused by https://github.com/microsoft/vscode/issues/212672
Repro:
1. Focus terminal
2. ctrl/cmd+i
3. Click terminal buffer, ๐ the inline chat should remain
The reason I think this is currently bad behavior is because the terminal inline chat is more persistent than the inline chat, being more akin to the post-response editor inline chat. I ran into this naturally when opening inline chat and realizing I needed to copy something.
I'm not a fan of the behavior of hiding when focusing anywhere added in https://github.com/microsoft/vscode/issues/212672, but the main problem case is clicking into the terminal.
|
Terminal inline chat should NOT hide when clicking the terminal or clicking away Caused by https://github.com/microsoft/vscode/issues/212672
Repro:
1. Focus terminal
2. ctrl/cmd+i
3. Click terminal buffer, ๐ the inline chat should remain
The reason I think this is currently bad behavior is because the terminal inline chat is more persistent than the inline chat, being more akin to the post-response editor inline chat. I ran into this naturally when opening inline chat and realizing I needed to copy something.
I'm not a fan of the behavior of hiding when focusing anywhere added in https://github.com/microsoft/vscode/issues/212672, but the main problem case is clicking into the terminal.
| 215 |
||
218402
|
Terminal inline chat bottom padding is messed up
|
2024-06-26 14:51:01+00:00
|
2024-06-26 15:27:04+00:00
|
Think this started happening in the last ~2 days
|
completed
|
Terminal inline chat bottom padding is messed up Think this started happening in the last ~2 days
| 62 |
218397
|
Missing a line break before closing ``` in accessible view
|
2024-06-26 14:28:42+00:00
|
2024-06-26 17:28:18+00:00
|
Found testing https://github.com/microsoft/vscode/issues/213941
|
completed
|
Missing a line break before closing ``` in accessible view Found testing https://github.com/microsoft/vscode/issues/213941
| 80 |
218395
|
Inline chat buttons overlap with focus border
|
2024-06-26 14:17:26+00:00
|
2024-06-26 14:48:29+00:00
|
* make a inline chat request
* select ๐ or ๐
* ๐ the borders overlap
|
completed
|
Inline chat buttons overlap with focus border * make a inline chat request
* select ๐ or ๐
* ๐ the borders overlap
| 77 |
218320
|
Accessible Hover View/Help contains yellow rectangles for certain whitespace characters like  , &emsp etc.
|
2024-06-26 11:07:20+00:00
|
- Install the GitLens extension
- Hover on an editor line, some decorative text should appear to the right showing the last person who edited the line, the moment when it was edited and the commit message
- Hover on that text, an editor hover should appear
- Focus on a hover part of the editor hover
- Make the accessible hover view appear
- Notice that the accessible hover view contains yellow rectangles corresponding to the whitespace characters like   &emsp etc ๐
https://github.com/microsoft/vscode/assets/61460952/e4940367-93ad-4647-80e8-e6d80a74497b
|
reopened
|
Accessible Hover View/Help contains yellow rectangles for certain whitespace characters like  , &emsp etc. - Install the GitLens extension
- Hover on an editor line, some decorative text should appear to the right showing the last person who edited the line, the moment when it was edited and the commit message
- Hover on that text, an editor hover should appear
- Focus on a hover part of the editor hover
- Make the accessible hover view appear
- Notice that the accessible hover view contains yellow rectangles corresponding to the whitespace characters like   &emsp etc ๐
https://github.com/microsoft/vscode/assets/61460952/e4940367-93ad-4647-80e8-e6d80a74497b
| 182 |
|
218267
|
Notify the user when debug is blocked on prelaunch tasks
|
2024-06-26 09:34:19+00:00
|
Clone https://github.com/microsoft/vscode-dev and npm install. Hit F5, it never starts:
<img width="484" alt="image" src="https://github.com/user-attachments/assets/7bf34879-6e67-4e7a-8b78-2215a87974bf">
I am on macOS.
|
reopened
|
Notify the user when debug is blocked on prelaunch tasks Clone https://github.com/microsoft/vscode-dev and npm install. Hit F5, it never starts:
<img width="484" alt="image" src="https://github.com/user-attachments/assets/7bf34879-6e67-4e7a-8b78-2215a87974bf">
I am on macOS.
| 105 |
|
218255
|
jsx auto indentation not corrent
|
2024-06-26 08:07:04+00:00
|
https://github.com/microsoft/vscode/assets/41773861/cc499f00-1402-40b5-940e-ad897d033e6f
@hediet @aiday-mar
## Expect
after press enter, the indent should align to the start of `onClick`
```
Version: 1.90.2 (Universal)
Commit: 5437499feb04f7a586f677b155b039bc2b3669eb
Date: 2024-06-18T22:37:41.291Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.5.0
```
|
jsx auto indentation not corrent https://github.com/microsoft/vscode/assets/41773861/cc499f00-1402-40b5-940e-ad897d033e6f
@hediet @aiday-mar
## Expect
after press enter, the indent should align to the start of `onClick`
```
Version: 1.90.2 (Universal)
Commit: 5437499feb04f7a586f677b155b039bc2b3669eb
Date: 2024-06-18T22:37:41.291Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.5.0
```
| 183 |
||
218230
|
"default" colorCustomization doesn't get unset when removing setting override
|
2024-06-25 22:14:43+00:00
|
2024-06-26 12:40:50+00:00
|
From https://github.com/microsoft/vscode/issues/170576
Add to setting
```
"workbench.colorCustomizations": {
"editor.background": "default",
```
- See that the editor background changes to the 'default' gray color
- Comment or delete the setting
- The background color doesn't change back to the theme color, and I can't make it go back until reloading the window
|
completed
|
"default" colorCustomization doesn't get unset when removing setting override From https://github.com/microsoft/vscode/issues/170576
Add to setting
```
"workbench.colorCustomizations": {
"editor.background": "default",
```
- See that the editor background changes to the 'default' gray color
- Comment or delete the setting
- The background color doesn't change back to the theme color, and I can't make it go back until reloading the window
| 122 |
218225
|
Right clicking the graph part of Incoming/Outgoing shows a context menu that applies to the changes above
|
2024-06-25 21:46:19+00:00
|
2024-07-05 15:54:53+00:00
|
Testing #217398
<img width="290" alt="image" src="https://github.com/user-attachments/assets/59f185bc-46c7-4c69-a8bc-9ec215d03f94">
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)
|
completed
|
Right clicking the graph part of Incoming/Outgoing shows a context menu that applies to the changes above Testing #217398
<img width="290" alt="image" src="https://github.com/user-attachments/assets/59f185bc-46c7-4c69-a8bc-9ec215d03f94">
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)
| 144 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.