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 |
|---|---|---|---|---|---|---|---|
207834 | Blinking block cursor shifts letter down | 2024-03-15 12:03:28+00:00 | 2024-03-20 10:06:38+00:00 | Repro:
0. set your cursor to be a block -- setting ` "editor.cursorStyle": "block",`
1. open an editor
2. :bug: see blinking block cursor shifting the letter down
https://github.com/microsoft/vscode/assets/16353531/d226b61d-e2bd-4f8c-ba3c-b9a939d2f1d7
Version: 1.88.0-insider
Commit: be210b3a60c7d60030c1d3d92da00d008edf6ab9
Date: 2024-03-15T06:00:06.808Z
Electron: 28.2.6
ElectronBuildId: 27476517
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.3.0 | completed | Blinking block cursor shifts letter down Repro:
0. set your cursor to be a block -- setting ` "editor.cursorStyle": "block",`
1. open an editor
2. :bug: see blinking block cursor shifting the letter down
https://github.com/microsoft/vscode/assets/16353531/d226b61d-e2bd-4f8c-ba3c-b9a939d2f1d7
Version: 1.88.0-insider
Commit: be210b3a60c7d60030c1d3d92da00d008edf6ab9
Date: 2024-03-15T06:00:06.808Z
Electron: 28.2.6
ElectronBuildId: 27476517
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.3.0 | 211 |
207832 | Cannot "Open Folder" anymore | 2024-03-15 11:58:48+00:00 | 2024-03-15 17:51:22+00:00 | Steps to Reproduce:
1. run `scripts/code-server.sh`
2. open the web UI
3. pick "Open Folder"
4. fill in a path that exists on disk and enter
<img width="791" alt="image" src="https://github.com/microsoft/vscode/assets/900690/91db50e9-00cc-4590-8869-d970af99ed52">
| completed | Cannot "Open Folder" anymore Steps to Reproduce:
1. run `scripts/code-server.sh`
2. open the web UI
3. pick "Open Folder"
4. fill in a path that exists on disk and enter
<img width="791" alt="image" src="https://github.com/microsoft/vscode/assets/900690/91db50e9-00cc-4590-8869-d970af99ed52">
| 106 |
207818 | Scroll lock should not prevent scrolling in active editor | 2024-03-15 09:52:44+00:00 | 2024-03-15 11:12:28+00:00 | It seems today that when scroll locking is enabled, the active editor cannot scroll further down if the side editor is scrolled down. I would have expected that the active editor is always free to scroll anyway:
| completed | Scroll lock should not prevent scrolling in active editor It seems today that when scroll locking is enabled, the active editor cannot scroll further down if the side editor is scrolled down. I would have expected that the active editor is always free to scroll anyway:
| 110 |
207817 | Scroll lock does not indicate in floating windows | 2024-03-15 09:49:35+00:00 | 2024-03-15 10:50:18+00:00 | I think the indicator should show in all opened windows and for that you need to add it to all windows. I would monkey-see, monkey-do what we do for the accessibility status indicator:
https://github.com/microsoft/vscode/blob/b22f435d4848fa8f5ef3f1c89cf56f68d7ce6049/src/vs/workbench/contrib/accessibility/browser/accessibilityStatus.ts#L45
Specifically:
https://github.com/microsoft/vscode/blob/b22f435d4848fa8f5ef3f1c89cf56f68d7ce6049/src/vs/workbench/contrib/accessibility/browser/accessibilityStatus.ts#L94-L97 | completed | Scroll lock does not indicate in floating windows I think the indicator should show in all opened windows and for that you need to add it to all windows. I would monkey-see, monkey-do what we do for the accessibility status indicator:
https://github.com/microsoft/vscode/blob/b22f435d4848fa8f5ef3f1c89cf56f68d7ce6049/src/vs/workbench/contrib/accessibility/browser/accessibilityStatus.ts#L45
Specifically:
https://github.com/microsoft/vscode/blob/b22f435d4848fa8f5ef3f1c89cf56f68d7ce6049/src/vs/workbench/contrib/accessibility/browser/accessibilityStatus.ts#L94-L97 | 201 |
207804 | WARN [markdown-language-features]: Couldn't find message for key | 2024-03-15 07:23:42+00:00 | 2024-03-20 21:21:56+00:00 | In insiders:
```
WARN [markdown-language-features]: Couldn't find message for key configuration.markdown.editor.drop.enabled.always.
log.ts:429 WARN [markdown-language-features]: Couldn't find message for key configuration.markdown.editor.drop.enabled.smart.
log.ts:429 WARN [markdown-language-features]: Couldn't find message for key configuration.markdown.editor.drop.enabled.never.
log.ts:429 WARN [markdown-language-features]: Couldn't find message for key configuration.markdown.editor.filePaste.enabled.always.
log.ts:429 WARN [markdown-language-features]: Couldn't find message for key configuration.markdown.editor.filePaste.enabled.smart.
log.ts:429 WARN [markdown-language-features]: Couldn't find message for key configuration.markdown.editor.filePaste.enabled.never.
``` | completed | WARN [markdown-language-features]: Couldn't find message for key In insiders:
```
WARN [markdown-language-features]: Couldn't find message for key configuration.markdown.editor.drop.enabled.always.
log.ts:429 WARN [markdown-language-features]: Couldn't find message for key configuration.markdown.editor.drop.enabled.smart.
log.ts:429 WARN [markdown-language-features]: Couldn't find message for key configuration.markdown.editor.drop.enabled.never.
log.ts:429 WARN [markdown-language-features]: Couldn't find message for key configuration.markdown.editor.filePaste.enabled.always.
log.ts:429 WARN [markdown-language-features]: Couldn't find message for key configuration.markdown.editor.filePaste.enabled.smart.
log.ts:429 WARN [markdown-language-features]: Couldn't find message for key configuration.markdown.editor.filePaste.enabled.never.
``` | 275 |
207797 | Listener leak: `ipc.cp.ts` | 2024-03-15 06:55:40+00:00 | 2024-03-15 15:18:22+00:00 | https://github.com/microsoft/vscode/blob/be210b3a60c7d60030c1d3d92da00d008edf6ab9/src/vs/base/parts/ipc/node/ipc.cp.ts#L210 | completed | Listener leak: `ipc.cp.ts` https://github.com/microsoft/vscode/blob/be210b3a60c7d60030c1d3d92da00d008edf6ab9/src/vs/base/parts/ipc/node/ipc.cp.ts#L210 | 81 |
207767 | Slow execution of a all cells in Notebooks when working on large notebooks with plain text outputs (stdout) | 2024-03-14 22:26:02+00:00 | 2024-04-26 03:42:30+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: N/A
- OS Version: N/A
Steps to Reproduce:
1. Create a Jupyter notebook
2. Add a code cell with the following code
```python
1
```
3. Run the above cell
4. Now copy and paste this cell a few 100 times, at least 500 times
5. Save the notebook
6. Run one cell verify the cell runs
7. Open Jupyter extension logs (output panel) and clear it
8. Hit run all button
9. Problem 1: Notice that Jupyter extension logs do not get updated with anything and execution does not start for a few seconds.
Depending on the machine this can take a few seconds, event 40s.
After 40s, Jupyter extension finally gets the message from VS Code renderer process to run the cells
Now cells run to completion in 3-5s.
10. Problem 2: Now run a single cell, and we can still see the same delays.
**Summary**
* Perception is execution takes a few minutes
* In reality Jupyter extension runs in a few seconds (<5s)
* VS Code renderer process is busy doing something when we hit run all
Similar to https://github.com/microsoft/vscode/issues/207766 (but different as there are not image outputs, hence no images need to be transferred nor rendered) | completed | Slow execution of a all cells in Notebooks when working on large notebooks with plain text outputs (stdout) <!-- โ ๏ธโ ๏ธ 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: N/A
- OS Version: N/A
Steps to Reproduce:
1. Create a Jupyter notebook
2. Add a code cell with the following code
```python
1
```
3. Run the above cell
4. Now copy and paste this cell a few 100 times, at least 500 times
5. Save the notebook
6. Run one cell verify the cell runs
7. Open Jupyter extension logs (output panel) and clear it
8. Hit run all button
9. Problem 1: Notice that Jupyter extension logs do not get updated with anything and execution does not start for a few seconds.
Depending on the machine this can take a few seconds, event 40s.
After 40s, Jupyter extension finally gets the message from VS Code renderer process to run the cells
Now cells run to completion in 3-5s.
10. Problem 2: Now run a single cell, and we can still see the same delays.
**Summary**
* Perception is execution takes a few minutes
* In reality Jupyter extension runs in a few seconds (<5s)
* VS Code renderer process is busy doing something when we hit run all
Similar to https://github.com/microsoft/vscode/issues/207766 (but different as there are not image outputs, hence no images need to be transferred nor rendered) | 613 |
207766 | Slow execution of all cells in Notebooks when working on large notebooks with image outputs | 2024-03-14 22:23:37+00:00 | 2024-04-26 03:43:01+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: N/A
- OS Version: N/A
Steps to Reproduce:
1. Create a Jupyter notebook
2. Add a code cell with the following code
```python
from IPython import display
display.Image("<valid path>/output.png")
```
3. Run the above cell
4. Now copy and paste this cell a few 100 times, at least 200-300 times
5. Save the notebook
6. Run one cell verify the cell runs
7. Open Jupyter extension logs (output panel) and clear it
8. Hit run all button
9. Problem 1: Notice that Jupyter extension logs do not get updated with anything and execution does not start for a few seconds.
Depending on the machine this can take a few seconds, event 40s.
After 40s, Jupyter extension finally gets the message from VS Code renderer process to run the cells
Now cells run to completion in 3-5s.
10. Problem 2: Now run a single cell, and we can still see the same delays.
**Summary**
* Perception is execution takes a few minutes
* In reality Jupyter extension runs in a few seconds (<5s)
* VS Code renderer process is busy doing something when we hit run all
| completed | Slow execution of all cells in Notebooks when working on large notebooks with image outputs <!-- โ ๏ธโ ๏ธ 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: N/A
- OS Version: N/A
Steps to Reproduce:
1. Create a Jupyter notebook
2. Add a code cell with the following code
```python
from IPython import display
display.Image("<valid path>/output.png")
```
3. Run the above cell
4. Now copy and paste this cell a few 100 times, at least 200-300 times
5. Save the notebook
6. Run one cell verify the cell runs
7. Open Jupyter extension logs (output panel) and clear it
8. Hit run all button
9. Problem 1: Notice that Jupyter extension logs do not get updated with anything and execution does not start for a few seconds.
Depending on the machine this can take a few seconds, event 40s.
After 40s, Jupyter extension finally gets the message from VS Code renderer process to run the cells
Now cells run to completion in 3-5s.
10. Problem 2: Now run a single cell, and we can still see the same delays.
**Summary**
* Perception is execution takes a few minutes
* In reality Jupyter extension runs in a few seconds (<5s)
* VS Code renderer process is busy doing something when we hit run all
| 586 |
207751 | Unable to hide the chat widget in terminal | 2024-03-14 18:57:58+00:00 | 2024-03-19 13:29:04+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. -->
- Version: 1.88.0-insider
- Commit: 7107b38665e428a974c06b2c6e8f67a9a078aefd
- Date: 2024-03-13T06:02:12.129Z (1 day ago)
- Electron: 28.2.6
- ElectronBuildId: 27476517
- Chromium: 120.0.6099.291
- Node.js: 18.18.2
- V8: 12.0.267.19-electron.0
- OS: Darwin arm64 23.3.0
Steps to Reproduce:
Absolutely no idea how i ended up in this state, , howver I can no longer close this chat widget
<img width="546" alt="Screenshot 2024-03-15 at 05 55 43" src="https://github.com/microsoft/vscode/assets/1948812/e8019f21-e6f3-42dc-b685-3e119904c4a2">
| completed | Unable to hide the chat widget in terminal <!-- โ ๏ธโ ๏ธ 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. -->
- Version: 1.88.0-insider
- Commit: 7107b38665e428a974c06b2c6e8f67a9a078aefd
- Date: 2024-03-13T06:02:12.129Z (1 day ago)
- Electron: 28.2.6
- ElectronBuildId: 27476517
- Chromium: 120.0.6099.291
- Node.js: 18.18.2
- V8: 12.0.267.19-electron.0
- OS: Darwin arm64 23.3.0
Steps to Reproduce:
Absolutely no idea how i ended up in this state, , howver I can no longer close this chat widget
<img width="546" alt="Screenshot 2024-03-15 at 05 55 43" src="https://github.com/microsoft/vscode/assets/1948812/e8019f21-e6f3-42dc-b685-3e119904c4a2">
| 528 |
207744 | Orange filter highlight in quickopen | 2024-03-14 17:48:19+00:00 | 2024-03-19 17:09:01+00:00 | 
| completed | Orange filter highlight in quickopen 
| 54 |
207734 | z-index problem with scrollbar and collapsed region | 2024-03-14 16:35:45+00:00 | * open a multi-file diff editor
* observe how the scrollbar appears under the collapsed region
* this only happens when the hide animation plays
https://github.com/microsoft/vscode/assets/5047891/b888ff7d-848e-4109-8034-d8a2f22702a4
```
Version: 1.88.0-insider
Commit: 99a19815253d91900be5ec1016e0ecc7cc9a6950
Date: 2024-03-14T05:50:25.191Z
Electron: 28.2.6
ElectronBuildId: 27476517
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0
``` | z-index problem with scrollbar and collapsed region * open a multi-file diff editor
* observe how the scrollbar appears under the collapsed region
* this only happens when the hide animation plays
https://github.com/microsoft/vscode/assets/5047891/b888ff7d-848e-4109-8034-d8a2f22702a4
```
Version: 1.88.0-insider
Commit: 99a19815253d91900be5ec1016e0ecc7cc9a6950
Date: 2024-03-14T05:50:25.191Z
Electron: 28.2.6
ElectronBuildId: 27476517
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0
``` | 193 | ||
207707 | Toggle Word Wrap in multi-file diff editor should enable word wrap in all files | 2024-03-14 13:00:32+00:00 | * Open a multi-file diff editor
* Click in the first diff editor
* View > Toggle Word Wrap
* Observe that only the current file is word-wrapped | Toggle Word Wrap in multi-file diff editor should enable word wrap in all files * Open a multi-file diff editor
* Click in the first diff editor
* View > Toggle Word Wrap
* Observe that only the current file is word-wrapped | 58 | ||
207685 | Content inside line jumps | 2024-03-14 08:51:24+00:00 | 2024-03-20 10:06:39+00:00 | I'm typing `{` around this code, it seems inline completions triggers some kind of element with a certain height to be rendered which then appears to move the line content up. I think the height might not be set on the element.
```
export const getMapForWordSeparators = once<WordCharacterClassifier>(
(input) => new WordCharacterClassifier(input)
);
export function getMapForWordSeparators(wordSeparators: string, intlSegmenterLocales: Intl.UnicodeBCP47LocaleIdentifier[]): WordCharacterClassifier {}
```
https://github.com/microsoft/vscode/assets/5047891/9e8f1d3e-b995-4e55-832d-8ea2d7dc3840
```
Version: 1.88.0-insider
Commit: 99a19815253d91900be5ec1016e0ecc7cc9a6950
Date: 2024-03-14T05:50:25.191Z
Electron: 28.2.6
ElectronBuildId: 27476517
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0
``` | completed | Content inside line jumps I'm typing `{` around this code, it seems inline completions triggers some kind of element with a certain height to be rendered which then appears to move the line content up. I think the height might not be set on the element.
```
export const getMapForWordSeparators = once<WordCharacterClassifier>(
(input) => new WordCharacterClassifier(input)
);
export function getMapForWordSeparators(wordSeparators: string, intlSegmenterLocales: Intl.UnicodeBCP47LocaleIdentifier[]): WordCharacterClassifier {}
```
https://github.com/microsoft/vscode/assets/5047891/9e8f1d3e-b995-4e55-832d-8ea2d7dc3840
```
Version: 1.88.0-insider
Commit: 99a19815253d91900be5ec1016e0ecc7cc9a6950
Date: 2024-03-14T05:50:25.191Z
Electron: 28.2.6
ElectronBuildId: 27476517
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0
``` | 306 |
210528 | Slow edits and completions when editing Python code | 2024-03-14 00:14:42+00:00 | Reported by @ale-dg here https://github.com/microsoft/vscode/issues/206119#issuecomment-1996165888
Yes, but consider I did not use Pylance. Would you like me to test with it? I just activated it and opened the log trace for python and just for indexing it finishes its memory.
2024-03-13 17:51:01.092 [info] [Info - 17:51:01] (4192) Heap stats: total_heap_size=1220MB, used_heap_size=1156MB, total_physical_size=1218MB, total_available_size=2900MB, heap_size_limit=4096MB
2024-03-13 17:51:01.108 [info] [Warn - 17:51:01] (4192) Workspace indexing has hit its upper limit: 2000 files
| reopened | Slow edits and completions when editing Python code Reported by @ale-dg here https://github.com/microsoft/vscode/issues/206119#issuecomment-1996165888
Yes, but consider I did not use Pylance. Would you like me to test with it? I just activated it and opened the log trace for python and just for indexing it finishes its memory.
2024-03-13 17:51:01.092 [info] [Info - 17:51:01] (4192) Heap stats: total_heap_size=1220MB, used_heap_size=1156MB, total_physical_size=1218MB, total_available_size=2900MB, heap_size_limit=4096MB
2024-03-13 17:51:01.108 [info] [Warn - 17:51:01] (4192) Workspace indexing has hit its upper limit: 2000 files
| 208 | |
207651 | terminal chat cannot be opened | 2024-03-13 23:20:46+00:00 | terminal chat cannot be opened, I see in oss off of main this old setting.
| terminal chat cannot be opened terminal chat cannot be opened, I see in oss off of main this old setting.
| 77 | ||
207640 | cannot access 'session' before initialization | 2024-03-13 21:21:01+00:00 | 2024-03-14 05:31:38+00:00 | ```
voiceChatActions.ts:468 Uncaught ReferenceError: Cannot access 'session' before initialization
at voiceChatActions.ts:468:3
at async.ts:527:3
```
I see this when starting the panel chat voice action in dev tools.
An easy way to know when this reproduces is to enable the `chatResponsePending` audio cue, which then plays forever. | completed | cannot access 'session' before initialization ```
voiceChatActions.ts:468 Uncaught ReferenceError: Cannot access 'session' before initialization
at voiceChatActions.ts:468:3
at async.ts:527:3
```
I see this when starting the panel chat voice action in dev tools.
An easy way to know when this reproduces is to enable the `chatResponsePending` audio cue, which then plays forever. | 105 |
207639 | voice recording started sound is not on by default | 2024-03-13 21:18:37+00:00 | 2024-03-13 21:44:55+00:00 | This should be `on` by default
| completed | voice recording started sound is not on by default This should be `on` by default
| 68 |
207638 | pressing escape from within the accessible view's accessibility help dialog causes focus loss | 2024-03-13 21:06:30+00:00 | 2024-03-28 20:49:37+00:00 | 1. open the accessible view `alt+f2`
2. open accessibility help `alt+f1`
3. press `escape`
4. ๐ focus is lost, I expected the accessible view to be focused | completed | pressing escape from within the accessible view's accessibility help dialog causes focus loss 1. open the accessible view `alt+f2`
2. open accessibility help `alt+f1`
3. press `escape`
4. ๐ focus is lost, I expected the accessible view to be focused | 64 |
207619 | Inline chat does not render intents correctly if there's an intent that prefixes that intent | 2024-03-13 18:31:45+00:00 | 2024-03-19 17:13:09+00:00 | It runs the correct intent, but renders `/fix` rather than `/fixTestFailure`
This does not happen in panel chat | completed | Inline chat does not render intents correctly if there's an intent that prefixes that intent It runs the correct intent, but renders `/fix` rather than `/fixTestFailure`
This does not happen in panel chat | 145 |
207618 | Extension updates are not shown when there is a VS Code update | 2024-03-13 18:18:26+00:00 | 2024-03-13 18:46:19+00:00 | Steps to Reproduce:
**Platform: Windows**
1. Have older version of VS Code insiders installed
2. Have older version of an extension installed
3. Wait until VS Code insiders update is shown and **reload** (not restart) the window
๐ Extension update is not shown
๐ Telemetry is full of `galleryservice:cdnfallback` events if you Python extension installed.
| completed | Extension updates are not shown when there is a VS Code update Steps to Reproduce:
**Platform: Windows**
1. Have older version of VS Code insiders installed
2. Have older version of an extension installed
3. Wait until VS Code insiders update is shown and **reload** (not restart) the window
๐ Extension update is not shown
๐ Telemetry is full of `galleryservice:cdnfallback` events if you Python extension installed.
| 101 |
207605 | Terminal chat: Consider polishing the presentation in the single code block case special/common case | 2024-03-13 16:34:32+00:00 | 2024-03-19 15:47:05+00:00 | Feedback from @TylerLeonhardt: This looks weird how there's a border around the suggestion, should we polish this to remove padding and the border?
| completed | Terminal chat: Consider polishing the presentation in the single code block case special/common case Feedback from @TylerLeonhardt: This looks weird how there's a border around the suggestion, should we polish this to remove padding and the border?
| 104 |
207604 | Terminal chat: Consider UX for buttons when there are multiple chat blocks | 2024-03-13 16:32:46+00:00 | 2024-03-29 12:35:10+00:00 | When there are multiple code blocks we still just have "Run" and "Insert", but it's not clear that it will work on the first block only. Should we special case it such that if there are multiple code blocks the buttons change to "Run First" and "Insert First"? | completed | Terminal chat: Consider UX for buttons when there are multiple chat blocks When there are multiple code blocks we still just have "Run" and "Insert", but it's not clear that it will work on the first block only. Should we special case it such that if there are multiple code blocks the buttons change to "Run First" and "Insert First"? | 82 |
207602 | Terminal chat widget with a lot of content cannot be scrolled | 2024-03-13 16:30:17+00:00 | 2024-03-13 20:57:52+00:00 | Repro:
1. Open terminal chat
2. Ask "list files in various ways", ๐ content is clipped at bottom but scrolling doesn't work
| completed | Terminal chat widget with a lot of content cannot be scrolled Repro:
1. Open terminal chat
2. Ask "list files in various ways", ๐ content is clipped at bottom but scrolling doesn't work
| 92 |
207601 | Resizing terminal will not resize the terminal chat widget | 2024-03-13 16:29:04+00:00 | 2024-03-13 20:57:53+00:00 | Repro:
1. Open terminal chat
2. Ask "list files in various ways"
3. Reduce height of terminal
| completed | Resizing terminal will not resize the terminal chat widget Repro:
1. Open terminal chat
2. Ask "list files in various ways"
3. Reduce height of terminal
| 79 |
207599 | Terminal chat: View in chat should close the terminal chat widget | 2024-03-13 16:07:34+00:00 | 2024-03-13 19:55:58+00:00 | Repro:
1. Open terminal chat
2. Ask a question
3. Click the view in chat button, ๐ both chats show | completed | Terminal chat: View in chat should close the terminal chat widget Repro:
1. Open terminal chat
2. Ask a question
3. Click the view in chat button, ๐ both chats show | 39 |
207586 | remote.tunnels.access.hostNameOverride is sync'd | 2024-03-13 13:43:42+00:00 | 2024-03-14 16:12:08+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.87.2
- OS Version: Windows_NT x64 10.0.22621
Steps to Reproduce:
1. Set up 3 machines with VSCode, log into all 3 in VSCode and enable sync settings (make sure that Settings are configured to sync).
2. Set remote.tunnels.access.hostNameOverride on machine 1
3. remote.tunnels.access.hostNameOverride should be set on machine 2 and 3.
remote.tunnels.access.hostNameOverride should be local to the system so that you can provide each machine with its own name but because this setting is sync'd, the moment you set remote.tunnels.access.hostNameOverride, all machines get the same name tunnels can no longer figure out which machine to connect to when remote tunnels is turned on. You also don't have the ability to select each machine.
Current solution is to turn sync settings off in each machine and manually sync your settings. Once you do that, everything works as expected.
| completed | remote.tunnels.access.hostNameOverride is sync'd <!-- โ ๏ธโ ๏ธ 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.87.2
- OS Version: Windows_NT x64 10.0.22621
Steps to Reproduce:
1. Set up 3 machines with VSCode, log into all 3 in VSCode and enable sync settings (make sure that Settings are configured to sync).
2. Set remote.tunnels.access.hostNameOverride on machine 1
3. remote.tunnels.access.hostNameOverride should be set on machine 2 and 3.
remote.tunnels.access.hostNameOverride should be local to the system so that you can provide each machine with its own name but because this setting is sync'd, the moment you set remote.tunnels.access.hostNameOverride, all machines get the same name tunnels can no longer figure out which machine to connect to when remote tunnels is turned on. You also don't have the ability to select each machine.
Current solution is to turn sync settings off in each machine and manually sync your settings. Once you do that, everything works as expected.
| 541 |
207574 | `TestController` does not call its `resolveHandler` on root items after they are replaced | 2024-03-13 12:34:21+00:00 | 2024-03-29 17:16:22+00:00 | My extension's `TestController` has a `refreshHandler` that replaces all root items whenever it is called. It calls the same function that creates the items upon extension activation. After the `refreshHandler` is run, I've verified that the correct root items have been created with `canResolveChildren` set to `true`. However, when the user tries to expand the item, the `resolveHandler` is not called on that item and no children are created. This simple extension demonstrates the bug:
[test-provider-sample-0.0.1.vsix.zip](https://github.com/microsoft/vscode/files/14587669/test-provider-sample-0.0.1.vsix.zip)
Steps to Reproduce:
1. Install the extension above. It should immediately activate after the window refresh.
2. Open the text explorer and observe the root item. Expand it to reveal two children.
3. Open the `TestResolve` Output channel to see that the resolve handler was called.
4. Click the refresh icon and verify that "Refreshing" was written to the Output channel.
5. Try to expand the new root. Verify that the resolve handler was never called.
- VS Code Version: 1.87.2
| completed | `TestController` does not call its `resolveHandler` on root items after they are replaced My extension's `TestController` has a `refreshHandler` that replaces all root items whenever it is called. It calls the same function that creates the items upon extension activation. After the `refreshHandler` is run, I've verified that the correct root items have been created with `canResolveChildren` set to `true`. However, when the user tries to expand the item, the `resolveHandler` is not called on that item and no children are created. This simple extension demonstrates the bug:
[test-provider-sample-0.0.1.vsix.zip](https://github.com/microsoft/vscode/files/14587669/test-provider-sample-0.0.1.vsix.zip)
Steps to Reproduce:
1. Install the extension above. It should immediately activate after the window refresh.
2. Open the text explorer and observe the root item. Expand it to reveal two children.
3. Open the `TestResolve` Output channel to see that the resolve handler was called.
4. Click the refresh icon and verify that "Refreshing" was written to the Output channel.
5. Try to expand the new root. Verify that the resolve handler was never called.
- VS Code Version: 1.87.2
| 307 |
207551 | Shorten branch name in Source Control view to always have the changes indicator visible when using multi root workspace | 2024-03-13 08:00:47+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. -->
Hi, i could not find any request like this. We are using multi root workspaces and quite long branch names. The issue is, that the changes indicator next to the branch name in source control view is not visible for long branch names until you resize the source control view and make it wide enough. This is pretty enoying.
As a feature, I would like to have the branch names shortened using an ellipsis just like the projekt names. The full branch name remains visible in the tooltip. The goal is to always be able to see the changes indicator no matter how many chars the branch or project name is. | Shorten branch name in Source Control view to always have the changes indicator visible when using multi root workspace <!-- โ ๏ธโ ๏ธ 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. -->
Hi, i could not find any request like this. We are using multi root workspaces and quite long branch names. The issue is, that the changes indicator next to the branch name in source control view is not visible for long branch names until you resize the source control view and make it wide enough. This is pretty enoying.
As a feature, I would like to have the branch names shortened using an ellipsis just like the projekt names. The full branch name remains visible in the tooltip. The goal is to always be able to see the changes indicator no matter how many chars the branch or project name is. | 248 | ||
207550 | [Bug] MacOS: Multiline edit not functional in Safari, works well in Chrome | 2024-03-13 07:40:01+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:
- OS Version:
Steps to Reproduce:
1. Print a few lines of code in Monaco editor in browser and press Option+Command+Up Arrow or Option+Command+Down Arrow
2. This should place multiline cursor and works well in Chrome, but not in Safari.
| [Bug] MacOS: Multiline edit not functional in Safari, works well in Chrome <!-- โ ๏ธโ ๏ธ 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:
- OS Version:
Steps to Reproduce:
1. Print a few lines of code in Monaco editor in browser and press Option+Command+Up Arrow or Option+Command+Down Arrow
2. This should place multiline cursor and works well in Chrome, but not in Safari.
| 384 | ||
207547 | Clicking on an output and using Up/Down arrows scrolls through cells of another notebook | 2024-03-13 07:09:08+00:00 | Have two or more notebooks open side by side
* Select a cell of notebook 1
* Set focus to an output of a cell in another notebook
* Verify the new nb is selected (cell will be highlighted)
* Use up/down arrows
* Watch how cells in notebook 1 are highlighted instead of the nb that contains the output..
| reopened | Clicking on an output and using Up/Down arrows scrolls through cells of another notebook Have two or more notebooks open side by side
* Select a cell of notebook 1
* Set focus to an output of a cell in another notebook
* Verify the new nb is selected (cell will be highlighted)
* Use up/down arrows
* Watch how cells in notebook 1 are highlighted instead of the nb that contains the output..
| 101 | |
207517 | ChatParticipant.isSticky not being honored? | 2024-03-12 22:56:01+00:00 | 2024-03-23 22:11:51+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.88.0-insider
Commit: 7c284ae0c4922abf0ce6763b0d73da7012c5fa75
Date: 2024-03-12T09:50:06.404Z
Electron: 28.2.5
ElectronBuildId: 27336930
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
- OS Version: Darwin arm64 23.4.0
Steps to Reproduce:
1. I am running the the chat-sample on Insiders: https://github.com/microsoft/vscode-extension-samples/tree/297705fae877ab72190e4c920a7c6cc5747647dc/chat-sample
2. Note that the screenshot from the demo shows the icon for `@cat` overlaid on the Copilot icon: https://github.com/microsoft/vscode-extension-samples/tree/297705fae877ab72190e4c920a7c6cc5747647dc/chat-sample
3. I do not see this when I run this on Insiders today:
4. But more importantly, I see that `isSticky` is set: https://github.com/microsoft/vscode-extension-samples/blob/297705fae877ab72190e4c920a7c6cc5747647dc/chat-sample/src/extension.ts#L72
5. Yet the follow-up message does not start with `@cat`: I have to add it explicitly to continue the conversation with that chat participant. | completed | ChatParticipant.isSticky not being honored? <!-- โ ๏ธโ ๏ธ 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.88.0-insider
Commit: 7c284ae0c4922abf0ce6763b0d73da7012c5fa75
Date: 2024-03-12T09:50:06.404Z
Electron: 28.2.5
ElectronBuildId: 27336930
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
- OS Version: Darwin arm64 23.4.0
Steps to Reproduce:
1. I am running the the chat-sample on Insiders: https://github.com/microsoft/vscode-extension-samples/tree/297705fae877ab72190e4c920a7c6cc5747647dc/chat-sample
2. Note that the screenshot from the demo shows the icon for `@cat` overlaid on the Copilot icon: https://github.com/microsoft/vscode-extension-samples/tree/297705fae877ab72190e4c920a7c6cc5747647dc/chat-sample
3. I do not see this when I run this on Insiders today:
4. But more importantly, I see that `isSticky` is set: https://github.com/microsoft/vscode-extension-samples/blob/297705fae877ab72190e4c920a7c6cc5747647dc/chat-sample/src/extension.ts#L72
5. Yet the follow-up message does not start with `@cat`: I have to add it explicitly to continue the conversation with that chat participant. | 745 |
207505 | trying to render a codeblock without a model | 2024-03-12 19:56:49+00:00 | 2024-03-13 17:20:30+00:00 | 1. Run a request in the terminal chat
2. ๐ sometimes, no response will be rendered
| completed | trying to render a codeblock without a model 1. Run a request in the terminal chat
2. ๐ sometimes, no response will be rendered
| 81 |
207496 | regression: opened file navigation with arrow key no longer works | 2024-03-12 18:30:09+00:00 | 2024-03-14 02:52: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
<!-- ๐ช If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- ๐ฃ Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.88.0-insider (2024-03-12)
- OS Version: Windows 10 - 22H2 (19045.3930)
Steps to Reproduce:
1. have a few opened files in your editor
2. do Ctrl+Tab
3. try to use ArrowUp/Down to switch file but it no longer works and does nothing (only observer with insider builds)
> **Note** the long pause in the animated gif is when I try to use arrow keys, it works with Ctrl-Tab as shown below but it's not convenient
This problem started couple days ago in the Insider program, the stable version is currently unimpacted and I hope it won't either in the future. I use this ArrowUp/Down **a lot** when switching opened files, so I hope that this will be fixed shortly. The only alternative I know for now is to use the mouse but it's not as efficient. I did not find any similar opened issue but in my case it happens on all 3 computers that I use.
Not sure if some of these PRs could introduce the regression?
PR #207028
| completed | regression: opened file navigation with arrow key 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.88.0-insider (2024-03-12)
- OS Version: Windows 10 - 22H2 (19045.3930)
Steps to Reproduce:
1. have a few opened files in your editor
2. do Ctrl+Tab
3. try to use ArrowUp/Down to switch file but it no longer works and does nothing (only observer with insider builds)
> **Note** the long pause in the animated gif is when I try to use arrow keys, it works with Ctrl-Tab as shown below but it's not convenient
This problem started couple days ago in the Insider program, the stable version is currently unimpacted and I hope it won't either in the future. I use this ArrowUp/Down **a lot** when switching opened files, so I hope that this will be fixed shortly. The only alternative I know for now is to use the mouse but it's not as efficient. I did not find any similar opened issue but in my case it happens on all 3 computers that I use.
Not sure if some of these PRs could introduce the regression?
PR #207028
| 614 |
207489 | Terminal chat: No accept primary button | 2024-03-12 17:26:53+00:00 | 2024-03-13 17:20:29+00:00 | 
| completed | Terminal chat: No accept primary button 
| 58 |
207488 | Terminal chat is not wide enough | 2024-03-12 17:24:18+00:00 | 2024-03-15 22:02:03+00:00 | All content is squished:
| completed | Terminal chat is not wide enough All content is squished:
| 61 |
207484 | Navigating via "Go to Symbol in Editor..." does not add those navigated locations to the cursor navigation histories. | 2024-03-12 17:06:27+00:00 | 2024-03-13 09:58:57+00:00 | Type: <b>Bug</b>
Steps:
1. In an editor with recognized language symbols, activate action "Go to Symbol in Editor..." (workbench.action.gotoSymbol), then select a symbol to jump to. Notice the cursor location jumps to it.
2. Repeat Step 1 any number of times.
3. Activate either of two actions, "Go Back" (workbench.action.navigateBack) or "Go Back in Navigation Locations" (workbench.action.navigateBackInNavigationLocations)
RESULT: Instead of going back through any of the locations chosen from Step 1, the cursor skips to previous locations prior to any usage of "Go to Symbol", or simply doesn't move at all if you had begun with a newly opened editor in the beginning. Those locations should have been added to stacks for both "Go Back" and "Go Back in Navigation Locations".
NOTE:
I tested navigating with these two other similar actions, both of which do not have this problem: "Focus and Select Breadcrumbs" (breadcrumbs.focusAndSelect) and "Go to Symbol in Workspace..." (workbench.action.showAllSymbols).
Both worked properly with either subsequent action:"Go Back" or"Go Back in Navigation Locations". Only "Go to Symbol in Editor..." seems to be affected.
Tested in new --user-dir and --extensions-dir (with Python extension added) VSCode environment.
VS Code version: Code 1.87.0 (019f4d1419fbc8219a181fab7892ebccf7ee29a2, 2024-02-27T23:41:44.469Z)
OS version: Windows_NT x64 10.0.19043
Modes:
<details><summary>Extensions (3)</summary>
Extension|Author (truncated)|Version
---|---|---
debugpy|ms-|2024.2.0
python|ms-|2024.2.1
vscode-pylance|ms-|2024.2.3
</details>
<!-- generated by issue reporter --> | completed | Navigating via "Go to Symbol in Editor..." does not add those navigated locations to the cursor navigation histories. Type: <b>Bug</b>
Steps:
1. In an editor with recognized language symbols, activate action "Go to Symbol in Editor..." (workbench.action.gotoSymbol), then select a symbol to jump to. Notice the cursor location jumps to it.
2. Repeat Step 1 any number of times.
3. Activate either of two actions, "Go Back" (workbench.action.navigateBack) or "Go Back in Navigation Locations" (workbench.action.navigateBackInNavigationLocations)
RESULT: Instead of going back through any of the locations chosen from Step 1, the cursor skips to previous locations prior to any usage of "Go to Symbol", or simply doesn't move at all if you had begun with a newly opened editor in the beginning. Those locations should have been added to stacks for both "Go Back" and "Go Back in Navigation Locations".
NOTE:
I tested navigating with these two other similar actions, both of which do not have this problem: "Focus and Select Breadcrumbs" (breadcrumbs.focusAndSelect) and "Go to Symbol in Workspace..." (workbench.action.showAllSymbols).
Both worked properly with either subsequent action:"Go Back" or"Go Back in Navigation Locations". Only "Go to Symbol in Editor..." seems to be affected.
Tested in new --user-dir and --extensions-dir (with Python extension added) VSCode environment.
VS Code version: Code 1.87.0 (019f4d1419fbc8219a181fab7892ebccf7ee29a2, 2024-02-27T23:41:44.469Z)
OS version: Windows_NT x64 10.0.19043
Modes:
<details><summary>Extensions (3)</summary>
Extension|Author (truncated)|Version
---|---|---
debugpy|ms-|2024.2.0
python|ms-|2024.2.1
vscode-pylance|ms-|2024.2.3
</details>
<!-- generated by issue reporter --> | 508 |
207467 | Sticky scroll makes it hard to copy a big chunk of code | 2024-03-12 14:53:44+00:00 | Assume you have sticky scroll on and you want to copy a big chunk of code, you scroll up while selecting the text, and once you're almost at the top of the method, the mouse gets stuck.
I'm on the latest version of VSCode and the latest version of windows 11. I disabled sticky scroll until this is fixed. | reopened | Sticky scroll makes it hard to copy a big chunk of code Assume you have sticky scroll on and you want to copy a big chunk of code, you scroll up while selecting the text, and once you're almost at the top of the method, the mouse gets stuck.
I'm on the latest version of VSCode and the latest version of windows 11. I disabled sticky scroll until this is fixed. | 91 | |
207429 | Leaking event listener | 2024-03-12 13:37:37+00:00 | 2024-03-21 15:04:10+00:00 | https://github.com/microsoft/vscode/blob/be776fbfff16d18b19457cc271e4e049b766490d/src/vs/workbench/services/editor/browser/editorResolverService.ts#L81 | completed | Leaking event listener https://github.com/microsoft/vscode/blob/be776fbfff16d18b19457cc271e4e049b766490d/src/vs/workbench/services/editor/browser/editorResolverService.ts#L81 | 72 |
207418 | Unable to open notebook diff view from timeline (Leaking event listener) | 2024-03-12 13:30:00+00:00 | 2024-03-13 04:31:07+00:00 | https://github.com/microsoft/vscode/blob/be776fbfff16d18b19457cc271e4e049b766490d/src/vs/workbench/contrib/notebook/common/notebookEditorInput.ts#L55 | completed | Unable to open notebook diff view from timeline (Leaking event listener) https://github.com/microsoft/vscode/blob/be776fbfff16d18b19457cc271e4e049b766490d/src/vs/workbench/contrib/notebook/common/notebookEditorInput.ts#L55 | 89 |
207401 | "Retry as admin" don't respect "File: Save without Formatting" | 2024-03-12 09:46:36+00:00 | 2024-03-12 12:04:29+00:00 | Type: <b>Bug</b>
Open Visual Studio Code without admin privilege.
In settings, check "Format On Save".
Open a .html file that need admin privilege.
Insert html code that need to be formatted.
Save with "File: Save without Formatting"
Visual Studio Code will show a message box with "Retry as admin..."
Click on "Retry as admin..."
Validate Windows popup warning about admin rights.
The text will be formatted before be saved. (should not)
The problem also appears with cmake-format (I didn't test more formatter).
VS Code version: Code - Insiders 1.88.0-insider (9c3cc8b9948d52f04836997a7de01dbd9bb2a7bf, 2024-03-12T05:49:05.934Z)
OS version: Windows_NT x64 10.0.22631
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 2304)|
|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.67GB (18.14GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:30784851
c4g48928:30535728
a9j8j154:30646983
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonidxpt:30768918
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30926734
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
2e7ec940:30986170
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
d6fi2104:30968146
pydisww1:30981707
cppperfnew:30980852
d34g3935:30961436
fegfb526:30952798
bg6jg535:30979844
ccp1r6:30958151
pythonait:30973460
```
</details>
<!-- generated by issue reporter --> | completed | "Retry as admin" don't respect "File: Save without Formatting" Type: <b>Bug</b>
Open Visual Studio Code without admin privilege.
In settings, check "Format On Save".
Open a .html file that need admin privilege.
Insert html code that need to be formatted.
Save with "File: Save without Formatting"
Visual Studio Code will show a message box with "Retry as admin..."
Click on "Retry as admin..."
Validate Windows popup warning about admin rights.
The text will be formatted before be saved. (should not)
The problem also appears with cmake-format (I didn't test more formatter).
VS Code version: Code - Insiders 1.88.0-insider (9c3cc8b9948d52f04836997a7de01dbd9bb2a7bf, 2024-03-12T05:49:05.934Z)
OS version: Windows_NT x64 10.0.22631
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 2304)|
|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.67GB (18.14GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:30784851
c4g48928:30535728
a9j8j154:30646983
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonidxpt:30768918
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30926734
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
2e7ec940:30986170
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
d6fi2104:30968146
pydisww1:30981707
cppperfnew:30980852
d34g3935:30961436
fegfb526:30952798
bg6jg535:30979844
ccp1r6:30958151
pythonait:30973460
```
</details>
<!-- generated by issue reporter --> | 887 |
207389 | Mac text replacement | 2024-03-12 03:46:35+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: Version: 1.87.1 (Universal)
Commit: 1e790d77f81672c49be070e04474901747115651
Date: 2024-03-06T00:23:16.418Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin arm64 23.4.0
- OS Version: 14.4 (23E214)
Steps to Reproduce:
1. MacOS text replacement not working. MacOS shortcuts to replace text not working.
<img width="705" alt="Screenshot 2024-03-12 at 4 46 04โฏAM" src="https://github.com/microsoft/vscode/assets/25755563/cab4bb8b-3190-4bde-bdd1-9e80cf33a035">
| Mac text replacement <!-- โ ๏ธโ ๏ธ 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: Version: 1.87.1 (Universal)
Commit: 1e790d77f81672c49be070e04474901747115651
Date: 2024-03-06T00:23:16.418Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin arm64 23.4.0
- OS Version: 14.4 (23E214)
Steps to Reproduce:
1. MacOS text replacement not working. MacOS shortcuts to replace text not working.
<img width="705" alt="Screenshot 2024-03-12 at 4 46 04โฏAM" src="https://github.com/microsoft/vscode/assets/25755563/cab4bb8b-3190-4bde-bdd1-9e80cf33a035">
| 508 | ||
207372 | Embedder createTerminal API doesn't work for Codespaces anymore | 2024-03-11 22:45:25+00:00 | 2024-04-22 17:07:31+00:00 | https://github.com/microsoft/vscode/pull/159666 changed `TerminalMainContribution` to move to `LifecyclePhase.Restored` but this caused a feature for Codespaces to stop working where the terminal will start streaming in the init logs before the workbench has fully loaded. Ideally we would start it up on Starting only on remote, if we can't do that we need to move it back to Starting in the meantime.
cc @bpasero @osortega | completed | Embedder createTerminal API doesn't work for Codespaces anymore https://github.com/microsoft/vscode/pull/159666 changed `TerminalMainContribution` to move to `LifecyclePhase.Restored` but this caused a feature for Codespaces to stop working where the terminal will start streaming in the init logs before the workbench has fully loaded. Ideally we would start it up on Starting only on remote, if we can't do that we need to move it back to Starting in the meantime.
cc @bpasero @osortega | 137 |
207371 | PID = -1 showing for web embedder terminals | 2024-03-11 22:28:47+00:00 | 2024-03-15 18:07:55+00:00 | Repro:
1. Create codespace for https://github.com/microsoft/vscode-remote-try-node
2. Click building codespace link in notification
<img width="382" alt="Screenshot 2024-03-11 at 3 27 55โฏPM" src="https://github.com/microsoft/vscode/assets/2193314/1ddeac79-ac9b-41e3-9756-af78313045a2">
| completed | PID = -1 showing for web embedder terminals Repro:
1. Create codespace for https://github.com/microsoft/vscode-remote-try-node
2. Click building codespace link in notification
<img width="382" alt="Screenshot 2024-03-11 at 3 27 55โฏPM" src="https://github.com/microsoft/vscode/assets/2193314/1ddeac79-ac9b-41e3-9756-af78313045a2">
| 117 |
207368 | terminal chat response is `[object Object]` | 2024-03-11 21:49:51+00:00 | 2024-03-26 23:41:54+00:00 | not sure what the repro steps are yet.
| completed | terminal chat response is `[object Object]` not sure what the repro steps are yet.
| 69 |
207367 | terminal chat shows up when I start voice session in panel chat | 2024-03-11 21:40:59+00:00 | 2024-03-19 12:23:31+00:00 | 1. open a terminal
2. show the panel chat
3. click the mic icon in the panel chat
4. ๐ a badly rendered terminal chat widget shows up in the terminal | completed | terminal chat shows up when I start voice session in panel chat 1. open a terminal
2. show the panel chat
3. click the mic icon in the panel chat
4. ๐ a badly rendered terminal chat widget shows up in the terminal | 48 |
207365 | Rendering paused for long line for performance reasons. This can be configured via `editor.stopRenderingLineAfter`. | 2024-03-11 21:24:24+00:00 | When hovering over a very long line, a hover pops up saying:
> Rendering paused for long line for performance reasons. This can be configured via `editor.stopRenderingLineAfter`.
The hover only pops up when `Word Wrap` is turned on (and even when the entire line is rendering correctly) โ
but doesn't when `Word Wrap` is turned off (and the line stops rendering after 10,000 chars) โ
I think the check for `Word Wrap` needs to be inverted
| Rendering paused for long line for performance reasons. This can be configured via `editor.stopRenderingLineAfter`. When hovering over a very long line, a hover pops up saying:
> Rendering paused for long line for performance reasons. This can be configured via `editor.stopRenderingLineAfter`.
The hover only pops up when `Word Wrap` is turned on (and even when the entire line is rendering correctly) โ
but doesn't when `Word Wrap` is turned off (and the line stops rendering after 10,000 chars) โ
I think the check for `Word Wrap` needs to be inverted
| 251 | ||
207362 | terminal voice action starts voice recording in panel | 2024-03-11 21:07:12+00:00 | 2024-03-11 22:00:38+00:00 | ERROR: type should be string, got "\r\n\r\nhttps://github.com/microsoft/vscode/assets/29464607/a1214d21-f2b6-4fca-a162-56e2e1c66381\r\n\r\n" | completed | terminal voice action starts voice recording in panel
https://github.com/microsoft/vscode/assets/29464607/a1214d21-f2b6-4fca-a162-56e2e1c66381
| 55 |
207351 | editor hover appears behind inline chat widget | 2024-03-11 18:26:20+00:00 | - Hover over a variable that is just below an inline chat widget
| editor hover appears behind inline chat widget - Hover over a variable that is just below an inline chat widget
| 72 | ||
207335 | newWithProfile doesn't support contributed terminal profiles | 2024-03-11 14:44: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?: NA (its an issue with custom extensions)
<!-- ๐ช 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.87.0
- OS Version: Darwin arm64 23.1.0
**Related Issues**: https://github.com/microsoft/vscode/issues/152635, https://github.com/microsoft/vscode/issues/126738
**Description**: Creating an extension which contains a command that opens a custom terminal profile results in an error.
**Steps to Reproduce**:
1. while creating an extension, set up a custom terminal profile
```
"terminal": {
"profiles": [
{
"title": "custom-profile",
"id": "my-extension.custom-profile",
"icon": "assets/some-asset.png"
}
]
},
```
2. register it on extension activation via
```
vscode.window.registerTerminalProfileProvider('my-extension.custom-profile', {
provideTerminalProfile: async () => new vscode.TerminalProfile(await _some_async_loading_function())
}),
```
3. create a command meant to open the terminal in step 1
```
await commands.executeCommand(
'workbench.action.terminal.newWithProfile', {
profileName: "my-extension.custom-profile"
}
);
```
**RESULT**:
- running the command results in the error `Could not find terminal profile "my-extension.custom-profile"`
**EXPECTED RESULT**:
- no error, the terminal opens with the custom profile
**CAUSE**:
- I am still working to get a local build of vscode running so I can potentially contribute a fix, but it appears the issues lies [here](https://github.com/microsoft/vscode/blob/97c8d7e7ccf9028bba26ea47d284bbce93e8a1e8/src/vs/workbench/contrib/terminal/browser/terminalActions.ts#L1797) where we do `c.profileService.availableProfiles.find(...)`. Since the custom profiles live under `c.profileService.contributedProfiles.find(...)`, it never gets found resulting in the error being thrown. Unless I am mistaken and contributed profiles do exist under available profiles as well (not sure yet, just poking around in source looking at interfaces via intellisnse).
| newWithProfile doesn't support contributed terminal profiles <!-- โ ๏ธโ ๏ธ 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?: NA (its an issue with custom extensions)
<!-- ๐ช 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.87.0
- OS Version: Darwin arm64 23.1.0
**Related Issues**: https://github.com/microsoft/vscode/issues/152635, https://github.com/microsoft/vscode/issues/126738
**Description**: Creating an extension which contains a command that opens a custom terminal profile results in an error.
**Steps to Reproduce**:
1. while creating an extension, set up a custom terminal profile
```
"terminal": {
"profiles": [
{
"title": "custom-profile",
"id": "my-extension.custom-profile",
"icon": "assets/some-asset.png"
}
]
},
```
2. register it on extension activation via
```
vscode.window.registerTerminalProfileProvider('my-extension.custom-profile', {
provideTerminalProfile: async () => new vscode.TerminalProfile(await _some_async_loading_function())
}),
```
3. create a command meant to open the terminal in step 1
```
await commands.executeCommand(
'workbench.action.terminal.newWithProfile', {
profileName: "my-extension.custom-profile"
}
);
```
**RESULT**:
- running the command results in the error `Could not find terminal profile "my-extension.custom-profile"`
**EXPECTED RESULT**:
- no error, the terminal opens with the custom profile
**CAUSE**:
- I am still working to get a local build of vscode running so I can potentially contribute a fix, but it appears the issues lies [here](https://github.com/microsoft/vscode/blob/97c8d7e7ccf9028bba26ea47d284bbce93e8a1e8/src/vs/workbench/contrib/terminal/browser/terminalActions.ts#L1797) where we do `c.profileService.availableProfiles.find(...)`. Since the custom profiles live under `c.profileService.contributedProfiles.find(...)`, it never gets found resulting in the error being thrown. Unless I am mistaken and contributed profiles do exist under available profiles as well (not sure yet, just poking around in source looking at interfaces via intellisnse).
| 892 | ||
207296 | someting git diff didn't show correct place | 2024-03-11 03:18:57+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. -->
Version: 1.87.1 (Universal)
Commit: 1e790d77f81672c49be070e04474901747115651
Date: 2024-03-06T00:23:16.418Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin arm64 23.3.0
Steps to Reproduce:
https://github.com/microsoft/vscode/assets/20318608/3833b352-dc24-4bc0-8a72-50383362fc5a
| someting git diff didn't show correct place <!-- โ ๏ธโ ๏ธ 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. -->
Version: 1.87.1 (Universal)
Commit: 1e790d77f81672c49be070e04474901747115651
Date: 2024-03-06T00:23:16.418Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin arm64 23.3.0
Steps to Reproduce:
https://github.com/microsoft/vscode/assets/20318608/3833b352-dc24-4bc0-8a72-50383362fc5a
| 452 | ||
207354 | Report Issue dialog does not work for the Jupter extension | 2024-03-09 21:27:56+00:00 | <!-- Please search existing issues to avoid creating duplicates. -->
Followed the [helpful instructions](https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions) for submitting a bug report. Was impressed by the Report Issue feature mentioned. This should make things easier! But, alas, the "Preview on Github" button doesn't actually do anything useful.
This may be an integration or configuration issue with how the Jupyter extension project is connected up to the generic VS Code Report Issue feature.
## Environment data
About output:
Version: 1.87.1
Commit: 1e790d77f81672c49be070e04474901747115651
Date: 2024-03-06T00:21:07.287Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Linux x64 5.15.0-94-generic
- Jupyter Extension version (available under the Extensions sidebar): v2024.2.0
- Python Extension version (available under the Extensions sidebar): v2024.2.1
- Python and/or Anaconda version: 3.10.12
- Type of virtual environment used (N/A | venv | virtualenv | conda | ...): None
- Jupyter server running: Local
## Expected behaviour
The Report Issue dialog, when the "Preview on Github" button is pressed, should preview on Github as a new issue report.
## Actual behaviour
The [new issue](https://github.com/microsoft/vscode-jupyter/issues/new/choose) page appears without any of the information I provided.
## Steps to reproduce:
1. Follow [the instructions](https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions) to use the Report Issue feature.
2. Select File On: An Extension
3. Select Extension: Jupyter
4. Fill in the details of the report.
5. Click the "Preview on Github" button.
6. End up on the [new issue](https://github.com/microsoft/vscode-jupyter/issues/new/choose) with none of the information copied into a new issue.
7. Start all over again and copy the information out of the Report Issue dialog into a manually-created issue.
## Logs
No useful output could be found in any of the obvious logs. | Report Issue dialog does not work for the Jupter extension <!-- Please search existing issues to avoid creating duplicates. -->
Followed the [helpful instructions](https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions) for submitting a bug report. Was impressed by the Report Issue feature mentioned. This should make things easier! But, alas, the "Preview on Github" button doesn't actually do anything useful.
This may be an integration or configuration issue with how the Jupyter extension project is connected up to the generic VS Code Report Issue feature.
## Environment data
About output:
Version: 1.87.1
Commit: 1e790d77f81672c49be070e04474901747115651
Date: 2024-03-06T00:21:07.287Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Linux x64 5.15.0-94-generic
- Jupyter Extension version (available under the Extensions sidebar): v2024.2.0
- Python Extension version (available under the Extensions sidebar): v2024.2.1
- Python and/or Anaconda version: 3.10.12
- Type of virtual environment used (N/A | venv | virtualenv | conda | ...): None
- Jupyter server running: Local
## Expected behaviour
The Report Issue dialog, when the "Preview on Github" button is pressed, should preview on Github as a new issue report.
## Actual behaviour
The [new issue](https://github.com/microsoft/vscode-jupyter/issues/new/choose) page appears without any of the information I provided.
## Steps to reproduce:
1. Follow [the instructions](https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions) to use the Report Issue feature.
2. Select File On: An Extension
3. Select Extension: Jupyter
4. Fill in the details of the report.
5. Click the "Preview on Github" button.
6. End up on the [new issue](https://github.com/microsoft/vscode-jupyter/issues/new/choose) with none of the information copied into a new issue.
7. Start all over again and copy the information out of the Report Issue dialog into a manually-created issue.
## Logs
No useful output could be found in any of the obvious logs. | 590 | ||
207245 | Debug toolbar in Command Center does not respect debugIcon.disconnectForeground | 2024-03-09 19:05:08+00:00 | 2024-03-15 14:18:03+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.87.1
- OS Version: Windows 11 Home 22631.3235
Steps to Reproduce:
1. Change "debug.toolBarLocation" to commandCenter, and adjust the "debugIcon.disconnectForeground" color value:
```json
"debug.toolBarLocation": "commandCenter",
"workbench.colorCustomizations": {
"debugIcon.disconnectForeground": "#ff0000"
},
```
2. Color seems to be the default color, vs "floating" or "docked" settings that display the correct color. This is also the case when set in a custom theme extension.
Example screenshot of problem:
 | completed | Debug toolbar in Command Center does not respect debugIcon.disconnectForeground <!-- โ ๏ธโ ๏ธ 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.87.1
- OS Version: Windows 11 Home 22631.3235
Steps to Reproduce:
1. Change "debug.toolBarLocation" to commandCenter, and adjust the "debugIcon.disconnectForeground" color value:
```json
"debug.toolBarLocation": "commandCenter",
"workbench.colorCustomizations": {
"debugIcon.disconnectForeground": "#ff0000"
},
```
2. Color seems to be the default color, vs "floating" or "docked" settings that display the correct color. This is also the case when set in a custom theme extension.
Example screenshot of problem:
 | 524 |
207221 | can't access module `original-fs` in remote machine | 2024-03-09 03:13:26+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. -->
```
Version: 1.88.0-insider (Universal)
Commit: 6c19c003574b02afc604c0c1c471b1441b33a3d3
Date: 2024-03-08T05:49:06.954Z
Electron: 28.2.5
ElectronBuildId: 27336930
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.3.0
```
related issue๏ผ
- https://github.com/microsoft/vscode/issues/143393#issuecomment-1047518447
- https://github.com/tjx666/vscode-archive/issues/4
@deepak1556 @alexdima
| can't access module `original-fs` in remote machine <!-- โ ๏ธโ ๏ธ 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. -->
```
Version: 1.88.0-insider (Universal)
Commit: 6c19c003574b02afc604c0c1c471b1441b33a3d3
Date: 2024-03-08T05:49:06.954Z
Electron: 28.2.5
ElectronBuildId: 27336930
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.3.0
```
related issue๏ผ
- https://github.com/microsoft/vscode/issues/143393#issuecomment-1047518447
- https://github.com/tjx666/vscode-archive/issues/4
@deepak1556 @alexdima
| 486 | ||
207333 | Editing end of comment causes text to scroll offscreen | 2024-03-08 22:25:07+00:00 | 2024-03-20 13:36:50+00:00 | <!-- Please search existing issues to avoid creating duplicates. -->
<!-- Use Help > Report Issue to prefill some of these. -->
- Extension version: v0.83.2024030509 (pre-release)
- VSCode Version: 1.88.0-insider
- OS: Darwin x64 23.3.0
- Repository Clone Configuration (single repository/fork of an upstream repository): single repository
- Github Product (Github.com/Github Enterprise version x.x.x): Github.com
Steps to Reproduce:
1. Create a comment that causes the input box to scroll
2. While editing the comment insert the cursor at the end of the comment
3. Start typing
The edit input scrolls up so that the typed text is no longer visible. This makes it difficult to know what I'm typing.
https://github.com/microsoft/vscode-pull-request-github/assets/667716/2c786928-fe4f-4f0a-8f22-c848c00e01d8
| completed | Editing end of comment causes text to scroll offscreen <!-- Please search existing issues to avoid creating duplicates. -->
<!-- Use Help > Report Issue to prefill some of these. -->
- Extension version: v0.83.2024030509 (pre-release)
- VSCode Version: 1.88.0-insider
- OS: Darwin x64 23.3.0
- Repository Clone Configuration (single repository/fork of an upstream repository): single repository
- Github Product (Github.com/Github Enterprise version x.x.x): Github.com
Steps to Reproduce:
1. Create a comment that causes the input box to scroll
2. While editing the comment insert the cursor at the end of the comment
3. Start typing
The edit input scrolls up so that the typed text is no longer visible. This makes it difficult to know what I'm typing.
https://github.com/microsoft/vscode-pull-request-github/assets/667716/2c786928-fe4f-4f0a-8f22-c848c00e01d8
| 259 |
207205 | Terminal in the editor area created with an `iconPath` has overlapping icons with seti icon theme | 2024-03-08 21:55:42+00:00 | 2024-03-11 13:49:19+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.87.1
- OS Version:
Steps to Reproduce:
1. Enable the `vs-seti` icon theme
2. Create a terminal with the `createTerminal` function from the VS Code API, setting the `iconPath` to a file.
3. Move the terminal into the editor area
Example:
The extension defined `fileIcon` () is overlapping with the editor icon ().
| completed | Terminal in the editor area created with an `iconPath` has overlapping icons with seti icon theme <!-- โ ๏ธโ ๏ธ 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.87.1
- OS Version:
Steps to Reproduce:
1. Enable the `vs-seti` icon theme
2. Create a terminal with the `createTerminal` function from the VS Code API, setting the `iconPath` to a file.
3. Move the terminal into the editor area
Example:
The extension defined `fileIcon` () is overlapping with the editor icon ().
| 553 |
207200 | Cannot split a terminal without a group | 2024-03-08 21:12:16+00:00 | - Work in the vscode-copilot repo for awhile
- Run the default build task
- It doesn't run, I just get this error
It worked after I reloaded the window, thought the stack might be useful. This was Insiders 6c19c003574b02afc604c0c1c471b1441b33a3d3 for deminification
```
2024-03-08 16:02:19.138 [error] Cannot split a terminal without a group [object Object]: Error: Cannot split a terminal without a group [object Object]
at ae.Qb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2902:36622)
at ae.createTerminal (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2902:35337)
at async N.Cb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1599:16730)
at async N.Fb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1599:19468)
at async N.xb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1599:8411)
``` | Cannot split a terminal without a group - Work in the vscode-copilot repo for awhile
- Run the default build task
- It doesn't run, I just get this error
It worked after I reloaded the window, thought the stack might be useful. This was Insiders 6c19c003574b02afc604c0c1c471b1441b33a3d3 for deminification
```
2024-03-08 16:02:19.138 [error] Cannot split a terminal without a group [object Object]: Error: Cannot split a terminal without a group [object Object]
at ae.Qb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2902:36622)
at ae.createTerminal (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2902:35337)
at async N.Cb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1599:16730)
at async N.Fb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1599:19468)
at async N.xb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1599:8411)
``` | 494 | ||
207193 | QP Separator Items: Improve keybinding to navigate between sections | 2024-03-08 19:50:50+00:00 | 2024-03-15 16:17:16+00:00 | I introduced a keybinding recently (#207028) which works well for inline separators but not item separators... it was focusing the last item in a section when you go up.
Revisit to focus the first item in a section. | completed | QP Separator Items: Improve keybinding to navigate between sections I introduced a keybinding recently (#207028) which works well for inline separators but not item separators... it was focusing the last item in a section when you go up.
Revisit to focus the first item in a section. | 72 |
207191 | Quick Pick: make buttons easier to tab to | 2024-03-08 19:47:17+00:00 | Example:
To get to the button I have to hit TAB TAB TAB. Maybe we can improve the TAB behavior so that when you navigate the list (up and down) and hit TAB it goes to the buttons on the item... but after you type in the box, tab goes to the custom button. | Quick Pick: make buttons easier to tab to Example:
To get to the button I have to hit TAB TAB TAB. Maybe we can improve the TAB behavior so that when you navigate the list (up and down) and hit TAB it goes to the buttons on the item... but after you type in the box, tab goes to the custom button. | 124 | ||
207190 | QP Separator Items should either not be clickable or do something that makes sense | 2024-03-08 19:45:21+00:00 | 2024-03-19 02:12:30+00:00 |
I can click on them | completed | QP Separator Items should either not be clickable or do something that makes sense
I can click on them | 74 |
207186 | Paste link in markdown file adds extra markdown link syntax | 2024-03-08 19:38:22+00:00 | 2024-03-13 21:27:45+00:00 | * Be in insiders.vscode.dev
* Open a markdown file
* Add `[asdf](|)` where `|` is the cursor
* copy a link from the address bar and paste it
* ๐ `[asdf]([text](https://github.com/microsoft/vscode/issues/34563))` is what happens
I wonder if this is because the text is rich text? | completed | Paste link in markdown file adds extra markdown link syntax * Be in insiders.vscode.dev
* Open a markdown file
* Add `[asdf](|)` where `|` is the cursor
* copy a link from the address bar and paste it
* ๐ `[asdf]([text](https://github.com/microsoft/vscode/issues/34563))` is what happens
I wonder if this is because the text is rich text? | 112 |
207177 | Error when restarting extensions in WSL | 2024-03-08 17:32:23+00:00 | 2024-03-08 19:42:18+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.88.0-insider (user setup)
Commit: 6c19c003574b02afc604c0c1c471b1441b33a3d3
Date: 2024-03-08T08:14:03.524Z
Electron: 28.2.5
ElectronBuildId: 27336930
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.26058
```
Steps to Reproduce:
1. Using WSL extension
2. Get an update for extensions
3. Click on "Restart Extensions"
Result:
Click on Reload Window and everything seems to be fine.
| completed | Error when restarting extensions in WSL <!-- โ ๏ธโ ๏ธ 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.88.0-insider (user setup)
Commit: 6c19c003574b02afc604c0c1c471b1441b33a3d3
Date: 2024-03-08T08:14:03.524Z
Electron: 28.2.5
ElectronBuildId: 27336930
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.26058
```
Steps to Reproduce:
1. Using WSL extension
2. Get an update for extensions
3. Click on "Restart Extensions"
Result:
Click on Reload Window and everything seems to be fine.
| 522 |
207164 | Error while searching for extension | 2024-03-08 14:11:35+00:00 | From last couple of weeks I am seeing this a lot
When I search for an extension it shows this error for a sec or so and then it shows the actual results
- VS Code Version: 1.88 insider and 1.87
- OS Version: Windows 11
Steps to Reproduce:
1. Search for extension
initially showing the error while typing
2. and after a sec. or so it shows the actual results
| Error while searching for extension From last couple of weeks I am seeing this a lot
When I search for an extension it shows this error for a sec or so and then it shows the actual results
- VS Code Version: 1.88 insider and 1.87
- OS Version: Windows 11
Steps to Reproduce:
1. Search for extension
initially showing the error while typing
2. and after a sec. or so it shows the actual results
| 180 | ||
207150 | Multi Cursor: Selections Have Different Height | 2024-03-08 10:05:54+00:00 |
| Multi Cursor: Selections Have Different Height
| 104 | ||
207126 | Unable to run cells when opening an existing notebook and using pre-selected kernel | 2024-03-08 02:53:16+00:00 | 2024-03-08 04:16: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/No
<!-- ๐ช If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- ๐ฃ Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version:
- OS Version:
Steps to Reproduce:
1. Open workspace folder, create an ipynb file on disc, save this, select a kernel and run a cell
2. Reload VS Code
3. The kernel will be automatically selected,
4. We're unable to run cells, unless you switch kernels
```
Error: notebook controller is NOT associated to notebook: file:///Users/donjayamanne/demo/sample.ipynb
at Object.createNotebookCellExecution (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:150:213939)
at KernelController.createNotebookCellExecution (/Users/donjayamanne/Development/vsc/vscode-jupyter/src/kernels/kernelController.ts:13:32)
at Function.create (/Users/donjayamanne/Development/vsc/vscode-jupyter/src/kernels/execution/cellExecutionCreator.ts:152:24)
at Function.getOrCreate (/Users/donjayamanne/Development/vsc/vscode-jupyter/src/kernels/execution/cellExecutionCreator.ts:121:50)
at _VSCodeNotebookController.createCellExecutionIfNecessary (/Users/donjayamanne/Development/vsc/vscode-jupyter/src/notebooks/controllers/vscodeNotebookController.ts:515:53)
at _VSCodeNotebookController.executeCell (/Users/donjayamanne/Development/vsc/vscode-jupyter/src/notebooks/controllers/vscodeNotebookController.ts:534:25)
a
```
| completed | Unable to run cells when opening an existing notebook and using pre-selected kernel <!-- โ ๏ธโ ๏ธ 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:
- OS Version:
Steps to Reproduce:
1. Open workspace folder, create an ipynb file on disc, save this, select a kernel and run a cell
2. Reload VS Code
3. The kernel will be automatically selected,
4. We're unable to run cells, unless you switch kernels
```
Error: notebook controller is NOT associated to notebook: file:///Users/donjayamanne/demo/sample.ipynb
at Object.createNotebookCellExecution (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:150:213939)
at KernelController.createNotebookCellExecution (/Users/donjayamanne/Development/vsc/vscode-jupyter/src/kernels/kernelController.ts:13:32)
at Function.create (/Users/donjayamanne/Development/vsc/vscode-jupyter/src/kernels/execution/cellExecutionCreator.ts:152:24)
at Function.getOrCreate (/Users/donjayamanne/Development/vsc/vscode-jupyter/src/kernels/execution/cellExecutionCreator.ts:121:50)
at _VSCodeNotebookController.createCellExecutionIfNecessary (/Users/donjayamanne/Development/vsc/vscode-jupyter/src/notebooks/controllers/vscodeNotebookController.ts:515:53)
at _VSCodeNotebookController.executeCell (/Users/donjayamanne/Development/vsc/vscode-jupyter/src/notebooks/controllers/vscodeNotebookController.ts:534:25)
a
```
| 779 |
207180 | misalignment on border of markdown cell | 2024-03-08 00:54:49+00:00 |
## Environment data
- VS Code version: 1.87.0, 1.87.1
## Expected behaviour
XXX
## Actual behaviour
| misalignment on border of markdown cell
## Environment data
- VS Code version: 1.87.0, 1.87.1
## Expected behaviour
XXX
## Actual behaviour
| 86 | ||
207101 | Error message while launching VSCode | 2024-03-07 18:44:23+00:00 | 2024-04-04 14:29:04+00:00 | - VS Code Version: Versionย : 1.87.1
Validationย : 1e790d77f81672c49be070e04474901747115651
Dateย : 2024-03-06T00:22:39.156Z
Electronย : 27.3.2
ElectronBuildIdย : 26836302
Chromiumย : 118.0.5993.159
Node.jsย : 18.17.1
V8ย : 11.8.172.18-electron.0
Systรจme dโexploitationย : Darwin arm64 23.3.0
Steps to Reproduce:
Just launch VS Code and get an error message like in picture joined. I don't know how to not get them
<img width="582" alt="Capture dโeฬcran 2024-03-07 aฬ 19 40 25" src="https://github.com/microsoft/vscode/assets/49912455/cdbabaa2-b535-425e-bc4c-24ec2e2b228b">
| completed | Error message while launching VSCode - VS Code Version: Versionย : 1.87.1
Validationย : 1e790d77f81672c49be070e04474901747115651
Dateย : 2024-03-06T00:22:39.156Z
Electronย : 27.3.2
ElectronBuildIdย : 26836302
Chromiumย : 118.0.5993.159
Node.jsย : 18.17.1
V8ย : 11.8.172.18-electron.0
Systรจme dโexploitationย : Darwin arm64 23.3.0
Steps to Reproduce:
Just launch VS Code and get an error message like in picture joined. I don't know how to not get them
<img width="582" alt="Capture dโeฬcran 2024-03-07 aฬ 19 40 25" src="https://github.com/microsoft/vscode/assets/49912455/cdbabaa2-b535-425e-bc4c-24ec2e2b228b">
| 214 |
207089 | With active selection, terminal does not get focus when switching to its editor group | 2024-03-07 16:02:31+00:00 | 2024-03-07 20:59:39+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.87.0
- OS Version: MacOS Sonoma, 14.3.1 (23D60).
Steps to Reproduce:
1. Start VSCode with one editor group.
2. Start a new empty document and enter some text.
3. Create a new terminal in the editor area ("Terminal: Create New Terminal in Editor Area").
4. Move the terminal to the editor group on the right ("View: Move Editor into Right Group")
5. Select some text in the editor (left group).
6. Focus on the second editor group ("workbench.action.focusSecondEditorGroup" or CMD+2 on MacOS).
Screencast:
Additional notes:
1. The bug showed up a few months ago. It is not new to 1.87.
2. Editor gets focus just fine. The problem is only with the terminal.
3. The terminal in the panel (CMD+J) works fine.
4. Attaching my settings: [settings.json](https://github.com/microsoft/vscode/files/14526954/settings.json) | completed | With active selection, terminal does not get focus when switching to its editor group <!-- โ ๏ธโ ๏ธ 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.87.0
- OS Version: MacOS Sonoma, 14.3.1 (23D60).
Steps to Reproduce:
1. Start VSCode with one editor group.
2. Start a new empty document and enter some text.
3. Create a new terminal in the editor area ("Terminal: Create New Terminal in Editor Area").
4. Move the terminal to the editor group on the right ("View: Move Editor into Right Group")
5. Select some text in the editor (left group).
6. Focus on the second editor group ("workbench.action.focusSecondEditorGroup" or CMD+2 on MacOS).
Screencast:
Additional notes:
1. The bug showed up a few months ago. It is not new to 1.87.
2. Editor gets focus just fine. The problem is only with the terminal.
3. The terminal in the panel (CMD+J) works fine.
4. Attaching my settings: [settings.json](https://github.com/microsoft/vscode/files/14526954/settings.json) | 591 |
207080 | Styling of language features hover is wrong in latest | 2024-03-07 14:19:29+00:00 | 2024-03-07 15:31:38+00:00 | v1.87
Latest 1.88-insiders
| completed | Styling of language features hover is wrong in latest v1.87
Latest 1.88-insiders
| 114 |
207066 | git.stage shortcut loses file list focus | 2024-03-07 13:06:49+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, it's related to the git extension
<!-- ๐ช 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.87.0 (Universal)
Commit: 019f4d1419fbc8219a181fab7892ebccf7ee29a2
Date: 2024-02-27T23:42:56.944Z (1 wk ago)
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
```
- OS Version:
`Darwin arm64 22.5.0`
Steps to Reproduce:
1. Add this keybind in vscode:
```json
{
"key": "ctrl+alt+m",
"command": "git.stage",
"when": "view.workbench.scm.visible"
},
```
2. Have some unstaged files and focus on one
<img width="516" alt="image" src="https://github.com/microsoft/vscode/assets/17517057/36ccfd3d-7d2c-4cce-8df7-c4329837d67e">
3. Click ctrl + option + m to stage your selected file
4. Previously the focus would go to the next item of the list, but now the focus go to the workbench view, which is pretty annoying when you want to do that multiple times in multiple files
I used this shortcut massively last year and a recent update (something like 1-2 moths ago broke it)
| git.stage shortcut loses file list focus <!-- โ ๏ธโ ๏ธ 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, it's related to the git extension
<!-- ๐ช 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.87.0 (Universal)
Commit: 019f4d1419fbc8219a181fab7892ebccf7ee29a2
Date: 2024-02-27T23:42:56.944Z (1 wk ago)
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
```
- OS Version:
`Darwin arm64 22.5.0`
Steps to Reproduce:
1. Add this keybind in vscode:
```json
{
"key": "ctrl+alt+m",
"command": "git.stage",
"when": "view.workbench.scm.visible"
},
```
2. Have some unstaged files and focus on one
<img width="516" alt="image" src="https://github.com/microsoft/vscode/assets/17517057/36ccfd3d-7d2c-4cce-8df7-c4329837d67e">
3. Click ctrl + option + m to stage your selected file
4. Previously the focus would go to the next item of the list, but now the focus go to the workbench view, which is pretty annoying when you want to do that multiple times in multiple files
I used this shortcut massively last year and a recent update (something like 1-2 moths ago broke it)
| 655 | ||
207037 | Cannot read properties of undefined (reading 'reset') | 2024-03-07 06:11:50+00:00 | 2024-03-07 17:20:31+00:00 | Found this stack when I was using Code OSS:
```
[59916:0307/070110.455536:INFO:CONSOLE(241)] "%c ERR color: #f33 Cannot read properties of undefined (reading 'reset'): TypeError: Cannot read properties of undefined (reading 'reset')
at TerminalChatController.clear (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/contrib/terminalContrib/chat/browser/terminalChatController.js:159:42)
at TerminalChatController.dispose (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/contrib/terminalContrib/chat/browser/terminalChatController.js:308:18)
at UniqueContainer.value (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/contrib/terminal/browser/terminalInstance.js:412:34)
at Emitter._deliver (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/base/common/event.js:870:26)
at Emitter._deliverQueue (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/base/common/event.js:881:22)
at Emitter.fire (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/base/common/event.js:904:22)
at TerminalInstance.dispose (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/contrib/terminal/browser/terminalInstance.js:892:30)
at TerminalService._onWillShutdown (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/contrib/terminal/browser/terminalService.js:571:30)
at UniqueContainer.value (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/contrib/terminal/browser/terminalService.js:146:56)
at Emitter._deliver (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/base/common/event.js:870:26)
at Emitter._deliverQueue (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/base/common/event.js:881:22)
at Emitter.fire (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/base/common/event.js:904:22)
at NativeLifecycleService.handleWillShutdown (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/services/lifecycle/electron-sandbox/lifecycleService.js:132:34)
at vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/services/lifecycle/electron-sandbox/lifecycleService.js:53:28"
``` | completed | Cannot read properties of undefined (reading 'reset') Found this stack when I was using Code OSS:
```
[59916:0307/070110.455536:INFO:CONSOLE(241)] "%c ERR color: #f33 Cannot read properties of undefined (reading 'reset'): TypeError: Cannot read properties of undefined (reading 'reset')
at TerminalChatController.clear (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/contrib/terminalContrib/chat/browser/terminalChatController.js:159:42)
at TerminalChatController.dispose (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/contrib/terminalContrib/chat/browser/terminalChatController.js:308:18)
at UniqueContainer.value (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/contrib/terminal/browser/terminalInstance.js:412:34)
at Emitter._deliver (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/base/common/event.js:870:26)
at Emitter._deliverQueue (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/base/common/event.js:881:22)
at Emitter.fire (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/base/common/event.js:904:22)
at TerminalInstance.dispose (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/contrib/terminal/browser/terminalInstance.js:892:30)
at TerminalService._onWillShutdown (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/contrib/terminal/browser/terminalService.js:571:30)
at UniqueContainer.value (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/contrib/terminal/browser/terminalService.js:146:56)
at Emitter._deliver (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/base/common/event.js:870:26)
at Emitter._deliverQueue (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/base/common/event.js:881:22)
at Emitter.fire (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/base/common/event.js:904:22)
at NativeLifecycleService.handleWillShutdown (vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/services/lifecycle/electron-sandbox/lifecycleService.js:132:34)
at vscode-file://vscode-app/Users/bpasero/Development/Microsoft/vscode/out/vs/workbench/services/lifecycle/electron-sandbox/lifecycleService.js:53:28"
``` | 943 |
207003 | Add settings option to disable tab drag&drop indicator | 2024-03-06 19:24:26+00:00 | 2024-04-04 10:53:36+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. -->
As introduced in version 1.87.0 (https://github.com/microsoft/vscode/pull/203681) drag&drop tabs now features a border indicator. It would be nice to have an option to disable this indicator.
(Indicator also makes tabs width change and subsequent unwanted jump effect but that's perhaps a bug issue.)
| completed | Add settings option to disable tab drag&drop indicator <!-- โ ๏ธโ ๏ธ 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. -->
As introduced in version 1.87.0 (https://github.com/microsoft/vscode/pull/203681) drag&drop tabs now features a border indicator. It would be nice to have an option to disable this indicator.
(Indicator also makes tabs width change and subsequent unwanted jump effect but that's perhaps a bug issue.)
| 236 |
206999 | Custom hover behaves badly near the bottom of the screen | 2024-03-06 18:44:23+00:00 | 2024-03-08 13:03:07+00:00 | 1. Have a project with some kind of debugging and make sure the Breakpoints view is near the bottom of the screen
2. Hover over the pencil icon on the second-to-bottom list item. It works ๐
3. Hover over the bottom list icon. The tooltip seems to appear and disappear very quickly causing the mouse to flicker (the FPS on the gif doesn't capture it very well but you can see that it doesn't render correctly)
| completed | Custom hover behaves badly near the bottom of the screen 1. Have a project with some kind of debugging and make sure the Breakpoints view is near the bottom of the screen
2. Hover over the pencil icon on the second-to-bottom list item. It works ๐
3. Hover over the bottom list icon. The tooltip seems to appear and disappear very quickly causing the mouse to flicker (the FPS on the gif doesn't capture it very well but you can see that it doesn't render correctly)
| 164 |
206998 | Custom hover disappears before you can mouse over into it | 2024-03-06 18:42:04+00:00 | 2024-03-07 11:14:32+00:00 | 1. Have a status bar contribution with an actionable tooltip, like Rust Analyzer's contribution in a repo with Rust code (like vscode) or Joh's PR pinger
2. Hover over the status bar entry and try to move your mouse to interact with it
3. It disappears ๐
| completed | Custom hover disappears before you can mouse over into it 1. Have a status bar contribution with an actionable tooltip, like Rust Analyzer's contribution in a repo with Rust code (like vscode) or Joh's PR pinger
2. Hover over the status bar entry and try to move your mouse to interact with it
3. It disappears ๐
| 122 |
206995 | Overview ruler at right | 2024-03-06 18:36:49+00:00 | Type: <b>Bug</b>
When viewing a file in the diff editor or file. The overview ruler on the right side does not correctly match the location between the modified lines and the current view window.
I have used VScode for years and before it worked perfectly, but a few versions ago it started to work poorly. When I click on a modified line, I expect to see that part in my window, but I have to scroll up. or below to find it well.
The view part is not representing the current editor view.
VS Code version: Code 1.87.0 (019f4d1419fbc8219a181fab7892ebccf7ee29a2, 2024-02-27T23:42:51.279Z)
OS version: Darwin arm64 23.2.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M2 (8 x 24)|
|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, 2, 2|
|Memory (System)|8.00GB (0.05GB free)|
|Process Argv|--crash-reporter-id a69d8399-5890-4087-ad57-07b74649ada8|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (14)</summary>
Extension|Author (truncated)|Version
---|---|---
codesnap|adp|1.3.4
vscode-better-align|cho|1.4.2
npm-intellisense|chr|1.4.5
path-intellisense|chr|2.8.5
vscode-eslint|dba|2.4.4
EditorConfig|Edi|0.16.4
svg|joc|1.5.3
vscode-language-babel|mgm|0.0.40
git-graph|mhu|1.30.0
fluent-icons|mig|0.0.18
symbols|mig|0.0.16
vscode-yaml|red|1.14.0
vscode-postcss|vun|2.0.2
gitblame|wad|10.9.0
(1 theme extensions excluded)
</details>
<!-- generated by issue reporter -->
<img width="18" alt="image" src="https://github.com/microsoft/vscode/assets/5330860/937cc3d1-c76f-4a5b-8392-f0dac0bd6f9b">
| Overview ruler at right Type: <b>Bug</b>
When viewing a file in the diff editor or file. The overview ruler on the right side does not correctly match the location between the modified lines and the current view window.
I have used VScode for years and before it worked perfectly, but a few versions ago it started to work poorly. When I click on a modified line, I expect to see that part in my window, but I have to scroll up. or below to find it well.
The view part is not representing the current editor view.
VS Code version: Code 1.87.0 (019f4d1419fbc8219a181fab7892ebccf7ee29a2, 2024-02-27T23:42:51.279Z)
OS version: Darwin arm64 23.2.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M2 (8 x 24)|
|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, 2, 2|
|Memory (System)|8.00GB (0.05GB free)|
|Process Argv|--crash-reporter-id a69d8399-5890-4087-ad57-07b74649ada8|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (14)</summary>
Extension|Author (truncated)|Version
---|---|---
codesnap|adp|1.3.4
vscode-better-align|cho|1.4.2
npm-intellisense|chr|1.4.5
path-intellisense|chr|2.8.5
vscode-eslint|dba|2.4.4
EditorConfig|Edi|0.16.4
svg|joc|1.5.3
vscode-language-babel|mgm|0.0.40
git-graph|mhu|1.30.0
fluent-icons|mig|0.0.18
symbols|mig|0.0.16
vscode-yaml|red|1.14.0
vscode-postcss|vun|2.0.2
gitblame|wad|10.9.0
(1 theme extensions excluded)
</details>
<!-- generated by issue reporter -->
<img width="18" alt="image" src="https://github.com/microsoft/vscode/assets/5330860/937cc3d1-c76f-4a5b-8392-f0dac0bd6f9b">
| 740 | ||
206988 | cut off button | 2024-03-06 17:13:45+00:00 | 2024-03-07 12:40:52+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:
- OS Version:
Steps to Reproduce:
1. make the side bar narrow but acceptedly narrow
2. uninstall an extension
2. ๐
why is it `Code - Insiders` now and not just `reload`?
| completed | cut off button <!-- โ ๏ธโ ๏ธ 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:
- OS Version:
Steps to Reproduce:
1. make the side bar narrow but acceptedly narrow
2. uninstall an extension
2. ๐
why is it `Code - Insiders` now and not just `reload`?
| 402 |
206982 | No padding between button and bottom of issue reporter | 2024-03-06 16:20:31+00:00 | 2024-03-22 17:22:03+00:00 | 
| completed | No padding between button and bottom of issue reporter 
| 57 |
206981 | No padding between included info and create on github button | 2024-03-06 16:19:54+00:00 | 2024-03-21 22:15:51+00:00 |
| completed | No padding between included info and create on github button
| 62 |
206959 | multi-diff-editor with 100+ files triggers global event limit | 2024-03-06 12:05:08+00:00 | Type: <b>Bug</b>
1. Open the `vscode` git repository as workspace
2. Generate a list of 100+ changed files, e.g. `cp -r src/vscode-dts src/vscode-dts-copy`
3. From SCM view, show changes using the multi-diff-editor
4. Look at the developer console, there should be a lot of warnings like:
```
[1he] potential listener LEAK detected, having 175 listeners already. MOST frequent listener (1):
```
I'm filing this is a bug, while it's actually a limitation with the current design. In https://github.com/microsoft/vscode/blob/9626fb0cd29113bc7bbaf7035e0b0cbe96baae59/src/vs/workbench/contrib/multiDiffEditor/browser/multiDiffEditorInput.ts#L189
The current global event limit is 175.
https://github.com/microsoft/vscode/blob/9626fb0cd29113bc7bbaf7035e0b0cbe96baae59/src/vs/workbench/browser/workbench.ts#L144
So it's not that hard to hit the event limit with 100 files...
The limit sounds familiar, e.g. see https://github.com/microsoft/vscode/issues/199615, which btw I don't see happening any more, not even with 1K or 2K files.
This is unrelated to the other similar case where I hit the same event limit with an extension, as this can be reproduced without any extension installed.
cc @hediet
VS Code version: Code - OSS Dev 1.88.0 (Commit unknown, Date unknown)
OS version: Windows_NT x64 10.0.18362
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 2112)|
|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.81GB (3.63GB free)|
|Process Argv|.|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none
<!-- generated by issue reporter --> | multi-diff-editor with 100+ files triggers global event limit Type: <b>Bug</b>
1. Open the `vscode` git repository as workspace
2. Generate a list of 100+ changed files, e.g. `cp -r src/vscode-dts src/vscode-dts-copy`
3. From SCM view, show changes using the multi-diff-editor
4. Look at the developer console, there should be a lot of warnings like:
```
[1he] potential listener LEAK detected, having 175 listeners already. MOST frequent listener (1):
```
I'm filing this is a bug, while it's actually a limitation with the current design. In https://github.com/microsoft/vscode/blob/9626fb0cd29113bc7bbaf7035e0b0cbe96baae59/src/vs/workbench/contrib/multiDiffEditor/browser/multiDiffEditorInput.ts#L189
The current global event limit is 175.
https://github.com/microsoft/vscode/blob/9626fb0cd29113bc7bbaf7035e0b0cbe96baae59/src/vs/workbench/browser/workbench.ts#L144
So it's not that hard to hit the event limit with 100 files...
The limit sounds familiar, e.g. see https://github.com/microsoft/vscode/issues/199615, which btw I don't see happening any more, not even with 1K or 2K files.
This is unrelated to the other similar case where I hit the same event limit with an extension, as this can be reproduced without any extension installed.
cc @hediet
VS Code version: Code - OSS Dev 1.88.0 (Commit unknown, Date unknown)
OS version: Windows_NT x64 10.0.18362
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 2112)|
|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.81GB (3.63GB free)|
|Process Argv|.|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none
<!-- generated by issue reporter --> | 748 | ||
206941 | [Bug] The staged file disappears from the git view | 2024-03-06 08:51: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?: Unkown
<!-- ๐ช 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.87.0
- OS Version: Alpine Linux 3.19
Steps to Reproduce:
1. Delete a soft link from a repository.
2. Create a normal file using the name of the soft link and make modifications.
3. Stage file in the git view.
4. The staged file disappears from the git view.
ScreenShot:
https://github.com/microsoft/vscode/assets/54622331/b32327ac-feda-42d0-9912-40f24d9df86d
| [Bug] The staged file disappears from the git view <!-- โ ๏ธโ ๏ธ 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?: Unkown
<!-- ๐ช 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.87.0
- OS Version: Alpine Linux 3.19
Steps to Reproduce:
1. Delete a soft link from a repository.
2. Create a normal file using the name of the soft link and make modifications.
3. Stage file in the git view.
4. The staged file disappears from the git view.
ScreenShot:
https://github.com/microsoft/vscode/assets/54622331/b32327ac-feda-42d0-9912-40f24d9df86d
| 429 | ||
206919 | Missing Chat Participant Icons in GitHub Copilot Chat Responses | 2024-03-05 21:19:16+00:00 | 2024-03-19 15:21:53+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: & OS Version:
Version: 1.88.0-insider (user setup)
Commit: d73fa8b14a6c873958d00a7d7ad13fcb540a052c
Date: 2024-03-05T05:47:29.930Z
Electron: 28.2.5
ElectronBuildId: 27336930
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.22631
### Steps to Reproduce:
1. Clone [Chat-Sample
](https://github.com/microsoft/vscode-extension-samples/tree/main/chat-sample)
2. Run Chat-Sample in Extension Development Host VSCode instance
3. In the GitHub Copilot Chat send a message to the @cat participant
### Summary
Recently noticed that the participant icon is no longer showing next to the GitHub Copilot icon in the response header.
It used to look like:
and now it looks like:
GitHub Copilot Chat Version: v0.14.2024030501 (pre-release)
@isidorn FYI
| completed | Missing Chat Participant Icons in GitHub Copilot Chat Responses <!-- โ ๏ธโ ๏ธ 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: & OS Version:
Version: 1.88.0-insider (user setup)
Commit: d73fa8b14a6c873958d00a7d7ad13fcb540a052c
Date: 2024-03-05T05:47:29.930Z
Electron: 28.2.5
ElectronBuildId: 27336930
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.22631
### Steps to Reproduce:
1. Clone [Chat-Sample
](https://github.com/microsoft/vscode-extension-samples/tree/main/chat-sample)
2. Run Chat-Sample in Extension Development Host VSCode instance
3. In the GitHub Copilot Chat send a message to the @cat participant
### Summary
Recently noticed that the participant icon is no longer showing next to the GitHub Copilot icon in the response header.
It used to look like:
and now it looks like:
GitHub Copilot Chat Version: v0.14.2024030501 (pre-release)
@isidorn FYI
| 676 |
206929 | Previewing Plotly HTML Plots Suddenly Broken | 2024-03-05 18:10:44+00:00 | 2024-06-30 11:24:31+00:00 | <!-- Please search existing issues to avoid creating duplicates. -->
## Environment data
- VS Code version: 1.87.0
- Jupyter Extension version (available under the Extensions sidebar): v2024.2.0
- Python Extension version (available under the Extensions sidebar): v2024.2.1
- OS (Windows | Mac | Linux distro) and version: Ubuntu 20.04.5 LTS
- Python and/or Anaconda version: Python 3.8.10
- Type of virtual environment used: N/A
- Jupyter server running: Local
## Expected behaviour
I use an extension called [HTML Preview](https://marketplace.visualstudio.com/items?itemName=analytic-signal.preview-html) that has successfully allowed me to view 3D Scatter Plots created by Plotly and saved as an HTML inside the VSCode window. I would expect to see the html graph render as it did before.
## Actual behaviour
This image appears.
## Steps to reproduce:
1. Try to preview an HTML file created with Plotly that has 3D values. It simply won't work.
## Further Notes
- [This issue](https://github.com/microsoft/vscode-jupyter/issues/11400) seems very similar to what I have experienced, but it was closed without resolution.
- If I run VSCode with `--disable-gpu` then it works, but ofcourse it's incredibly laggy.
- Other Browsers seem to work. Firefox and Chrome can render the HTML just fine.
- I have gotten it to go away before by uninstalling and reinstalling VSCode, but that seems like a poor solution.
- If I open Developer Tools I get the following error:
| not_planned | Previewing Plotly HTML Plots Suddenly Broken <!-- Please search existing issues to avoid creating duplicates. -->
## Environment data
- VS Code version: 1.87.0
- Jupyter Extension version (available under the Extensions sidebar): v2024.2.0
- Python Extension version (available under the Extensions sidebar): v2024.2.1
- OS (Windows | Mac | Linux distro) and version: Ubuntu 20.04.5 LTS
- Python and/or Anaconda version: Python 3.8.10
- Type of virtual environment used: N/A
- Jupyter server running: Local
## Expected behaviour
I use an extension called [HTML Preview](https://marketplace.visualstudio.com/items?itemName=analytic-signal.preview-html) that has successfully allowed me to view 3D Scatter Plots created by Plotly and saved as an HTML inside the VSCode window. I would expect to see the html graph render as it did before.
## Actual behaviour
This image appears.
## Steps to reproduce:
1. Try to preview an HTML file created with Plotly that has 3D values. It simply won't work.
## Further Notes
- [This issue](https://github.com/microsoft/vscode-jupyter/issues/11400) seems very similar to what I have experienced, but it was closed without resolution.
- If I run VSCode with `--disable-gpu` then it works, but ofcourse it's incredibly laggy.
- Other Browsers seem to work. Firefox and Chrome can render the HTML just fine.
- I have gotten it to go away before by uninstalling and reinstalling VSCode, but that seems like a poor solution.
- If I open Developer Tools I get the following error:
| 507 |
206876 | `JSON Language Server` output channel appears twice | 2024-03-05 08:44:52+00:00 | 2024-03-05 09:01:56+00:00 | 
| completed | `JSON Language Server` output channel appears twice 
| 55 |
206854 | Debug console is very slow with a single long line | 2024-03-05 00:17: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
<!-- ๐ช 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.87.0
- OS Version: Windows 11
- Language: Python
Steps to Reproduce:
1. Write a Python script that outputs text to the console every iteration of an infinite while loop.
2. Execute the script using debugpy. Example: `python -m debugpy --listen 5678 --wait-for-client ./script.py`
3. Attach the debugger.
VSCode will slow down and eventually freeze up.
This also affects scripts that output a lot of text that overwrites the current line. In my case I have a script that sifts through hundreds of thousands of records and displays a count indicating its progress.
Here is an example script and launch.json file:
Script:
```
def main():
loops = 0
while(True):
loops += 1
print(f"This script has looped {loops} times.", end="\r", flush=True)
if __name__ == "__main__":
main()
```
launch.json
```
{
"version": "0.2.0",
"configurations": [
{
"name": "Python Debugger: Attach",
"type": "debugpy",
"request": "attach",
"connect": {
"host": "localhost",
"port": 5678
}
}
]
}
```
Note: the slowdown can be temporarily fixed by clearing the debug console. But if you have a script constantly outputting text you're going to need to be clicking it constantly to prevent VSCode from freezing.
This GitHub issue was closed because it was fixed apparently https://github.com/microsoft/vscode/issues/19678. But, it seems it was fixed by clearing the debug console when the debug session starts. I think this needs to be further improved upon and clear the oldest N lines so VSCode doesn't lock up.
| Debug console is very slow with a single long 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
<!-- ๐ช 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.87.0
- OS Version: Windows 11
- Language: Python
Steps to Reproduce:
1. Write a Python script that outputs text to the console every iteration of an infinite while loop.
2. Execute the script using debugpy. Example: `python -m debugpy --listen 5678 --wait-for-client ./script.py`
3. Attach the debugger.
VSCode will slow down and eventually freeze up.
This also affects scripts that output a lot of text that overwrites the current line. In my case I have a script that sifts through hundreds of thousands of records and displays a count indicating its progress.
Here is an example script and launch.json file:
Script:
```
def main():
loops = 0
while(True):
loops += 1
print(f"This script has looped {loops} times.", end="\r", flush=True)
if __name__ == "__main__":
main()
```
launch.json
```
{
"version": "0.2.0",
"configurations": [
{
"name": "Python Debugger: Attach",
"type": "debugpy",
"request": "attach",
"connect": {
"host": "localhost",
"port": 5678
}
}
]
}
```
Note: the slowdown can be temporarily fixed by clearing the debug console. But if you have a script constantly outputting text you're going to need to be clicking it constantly to prevent VSCode from freezing.
This GitHub issue was closed because it was fixed apparently https://github.com/microsoft/vscode/issues/19678. But, it seems it was fixed by clearing the debug console when the debug session starts. I think this needs to be further improved upon and clear the oldest N lines so VSCode doesn't lock up.
| 750 | ||
206848 | accessible diff viewer covers buttons | 2024-03-04 22:30:12+00:00 | 2024-03-14 11:23:53+00:00 | I ran a request, it showed the accessible diff viewer, and that overlaid the toolbar so I could not accept or take action.
| not_planned | accessible diff viewer covers buttons I ran a request, it showed the accessible diff viewer, and that overlaid the toolbar so I could not accept or take action.
| 101 |
206840 | `selectHighlights` selects wrong value when search is set to regex | 2024-03-04 21:03:29+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.84.1
2b35e1e6d88f1ce073683991d1eff5284a32690f
x64
```
- OS Version: Windows 10 Enterprise build 19045.4046
If the in-file search editor is present (but not focused) with "Use Regular Expression" toggled on, `ctrl+shift+L` (`editor.action.selectHighlights`) will select all matches for the value _in the search bar_ rather than the value _currently selected in the editor_. Turning off regex or exiting the in-page search bar will revert the shortcut to its correct behavior.
All steps below were performed on a new file with all user settings and key bindings disabled.
Steps to Reproduce:
1. Open/create a file with duplicate texts
2. Enable in-page search (`ctrl+f`)
3. Submit a value present in the file to the search editor (value A)
4. Enable the regex option for in-page search (`alt+r`)
5. Select a non-unique text in the page (value B)
6. Trigger `editor.action.selectHighlights` (`ctrl+shift+L`)
7. All instances of _A_ will be selected (if any) rather than all instances of _B_
In the GIF above you will see me attempt to select highlights a number of times by double-clicking a word and spamming `ctrl+shift+L`. The result varies slightly based on the current search editor value.
- If the search value is found in the page, selection flips from the value selected manually to all instances of the search value.
- If the search editor is empty, the editor is populated it with the current selection and all page instances are selected.
- If the search editor value has no matches, the shortcut will simply do nothing.
Note that I have submitted [this issue](https://github.com/microsoft/vscode/issues/141184) previously without realizing the reproduction hinged on enabling regex. My sincere apologies for not performing a more in-depth analysis at the time in response to the dev's request for more information. I was busy at the time, but I still regret wasting someone's time. | `selectHighlights` selects wrong value when search is set to regex <!-- โ ๏ธโ ๏ธ 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.84.1
2b35e1e6d88f1ce073683991d1eff5284a32690f
x64
```
- OS Version: Windows 10 Enterprise build 19045.4046
If the in-file search editor is present (but not focused) with "Use Regular Expression" toggled on, `ctrl+shift+L` (`editor.action.selectHighlights`) will select all matches for the value _in the search bar_ rather than the value _currently selected in the editor_. Turning off regex or exiting the in-page search bar will revert the shortcut to its correct behavior.
All steps below were performed on a new file with all user settings and key bindings disabled.
Steps to Reproduce:
1. Open/create a file with duplicate texts
2. Enable in-page search (`ctrl+f`)
3. Submit a value present in the file to the search editor (value A)
4. Enable the regex option for in-page search (`alt+r`)
5. Select a non-unique text in the page (value B)
6. Trigger `editor.action.selectHighlights` (`ctrl+shift+L`)
7. All instances of _A_ will be selected (if any) rather than all instances of _B_
In the GIF above you will see me attempt to select highlights a number of times by double-clicking a word and spamming `ctrl+shift+L`. The result varies slightly based on the current search editor value.
- If the search value is found in the page, selection flips from the value selected manually to all instances of the search value.
- If the search editor is empty, the editor is populated it with the current selection and all page instances are selected.
- If the search editor value has no matches, the shortcut will simply do nothing.
Note that I have submitted [this issue](https://github.com/microsoft/vscode/issues/141184) previously without realizing the reproduction hinged on enabling regex. My sincere apologies for not performing a more in-depth analysis at the time in response to the dev's request for more information. I was busy at the time, but I still regret wasting someone's time. | 891 | ||
206830 | `Git: commit (amend)` does not works properly when the working tree is not clean | 2024-03-04 18:54:14+00:00 | 2024-07-02 12:50:51+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.87.0
- OS Version: Windows 10
Steps to Reproduce:
1. Initialize a empty repository using the "source control" tab (with git)
2. Create a file, add it to stage and commit with any message
3. With a clean working tree, verify that the command `Git: commit (amend)` works ok (it opens COMMIT_EDITMSG editor)
4. Now make any modification in the repository (e.g. modify a line in the created file)
5. The command `Git: commit (amend)` does not works properly anymore, it shows the message below:
Which is the warning message used when running the command `Git: commit` alone (not amend)
| completed | `Git: commit (amend)` does not works properly when the working tree is not clean <!-- โ ๏ธโ ๏ธ 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.87.0
- OS Version: Windows 10
Steps to Reproduce:
1. Initialize a empty repository using the "source control" tab (with git)
2. Create a file, add it to stage and commit with any message
3. With a clean working tree, verify that the command `Git: commit (amend)` works ok (it opens COMMIT_EDITMSG editor)
4. Now make any modification in the repository (e.g. modify a line in the created file)
5. The command `Git: commit (amend)` does not works properly anymore, it shows the message below:
Which is the warning message used when running the command `Git: commit` alone (not amend)
| 532 |
206827 | Collapsed markdown cell icons misalignment | 2024-03-04 18:41:40+00:00 | What it looks today
maybe we can adjust the gutter border, position of the collapse info text to make it look better
<img width="450" alt="image" src="https://github.com/microsoft/vscode/assets/876920/ac596265-4610-4a1c-a0a2-6863c5916798">
| Collapsed markdown cell icons misalignment What it looks today
maybe we can adjust the gutter border, position of the collapse info text to make it look better
<img width="450" alt="image" src="https://github.com/microsoft/vscode/assets/876920/ac596265-4610-4a1c-a0a2-6863c5916798">
| 147 | ||
206774 | [Bug] Empty ending bracket in `"surroundingPairs"` results in bad selection range | 2024-03-04 10:08:48+00:00 | add a bracket pair to `"surroundingPairs"` under `language-configuration.json`, with the end bracket being empty/blank
```json
"surroundingPairs": [
[ "(", "" ]
]
```
Make a selection around some text and press `(`
Expected: โ
resulting selection is still around `text`
Actual: โ
resulting selection ends up being moved 1 to the left
This could have been used as a workaround for https://github.com/microsoft/vscode/issues/202386 | [Bug] Empty ending bracket in `"surroundingPairs"` results in bad selection range add a bracket pair to `"surroundingPairs"` under `language-configuration.json`, with the end bracket being empty/blank
```json
"surroundingPairs": [
[ "(", "" ]
]
```
Make a selection around some text and press `(`
Expected: โ
resulting selection is still around `text`
Actual: โ
resulting selection ends up being moved 1 to the left
This could have been used as a workaround for https://github.com/microsoft/vscode/issues/202386 | 302 | ||
206764 | Extension sidebar hover tooltips block view when primary sidebar is set to right and extensions reside in the secondary sidebar on the left. | 2024-03-04 06:55:25+00:00 | 2024-03-05 13:54:24+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
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.87.0
- OS Version: Windows 10
Steps to Reproduce:
1. Set primary bar on the right
2. Set secondary bar on the left
3. Move the extensions category to the secondary bar
4. Hover over any extension
5. The tooltip will open right on top of the extension, blocking buttons such as "Reload Required", "Install", or simply clicking to open the extension details tab. The toast arrow on the right indicates that the CSS is programmed in such a way that it expects the extensions to be on the right side in VSCode.
Screenshot:
| completed | Extension sidebar hover tooltips block view when primary sidebar is set to right and extensions reside in the secondary sidebar on the left. <!-- โ ๏ธโ ๏ธ 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
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.87.0
- OS Version: Windows 10
Steps to Reproduce:
1. Set primary bar on the right
2. Set secondary bar on the left
3. Move the extensions category to the secondary bar
4. Hover over any extension
5. The tooltip will open right on top of the extension, blocking buttons such as "Reload Required", "Install", or simply clicking to open the extension details tab. The toast arrow on the right indicates that the CSS is programmed in such a way that it expects the extensions to be on the right side in VSCode.
Screenshot:
| 509 |
206762 | Custom hover sometimes appears instantly | 2024-03-04 06:40:48+00:00 | 2024-03-05 08:02:20+00:00 | This issue is similar to https://github.com/microsoft/vscode/issues/205658
I yet have to figure out how this reproduces but here is what I see:
* I have `workbench.hover.delay` configured to `3000`, so I normally would not expect the hover to appear unless I want it
* I interact with the UI, for example switch back to the app, hover over a setting or a tree item
* the hover appears instantly
This indicates to me that some kind of condition is not cleared up that tracks how long the mouse was over the element.
I am not sure how to best diagnose this other than maybe reviewing the code again and/or add some logging. | completed | Custom hover sometimes appears instantly This issue is similar to https://github.com/microsoft/vscode/issues/205658
I yet have to figure out how this reproduces but here is what I see:
* I have `workbench.hover.delay` configured to `3000`, so I normally would not expect the hover to appear unless I want it
* I interact with the UI, for example switch back to the app, hover over a setting or a tree item
* the hover appears instantly
This indicates to me that some kind of condition is not cleared up that tracks how long the mouse was over the element.
I am not sure how to best diagnose this other than maybe reviewing the code again and/or add some logging. | 169 |
206761 | Native hover in search input | 2024-03-04 06:37:39+00:00 | 2024-03-05 08:27:29+00:00 | I think when hovering over the search input field:
| completed | Native hover in search input I think when hovering over the search input field:
| 67 |
206756 | Comments filter wording feedback | 2024-03-04 05:15:18+00:00 | 2024-03-04 10:55:16+00:00 | I find the comments filter dropdown unexpected. I would not expect labels to change:
Compare with timeline filter:
| completed | Comments filter wording feedback I find the comments filter dropdown unexpected. I would not expect labels to change:
Compare with timeline filter:
| 167 |
206755 | Comments filter looks unbalanced | 2024-03-04 05:13:43+00:00 | 2024-03-04 12:12:04+00:00 | Look at the right hand side:
| completed | Comments filter looks unbalanced Look at the right hand side:
| 60 |
206700 | Bracket matching (and coloring) broken in some cases | 2024-03-02 19:17:10+00:00 | 2024-03-04 13:57:49+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... turns out they weren't all disabled.
<!-- ๐ช If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- ๐ฃ Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.87.0
- OS Version: Microsoft Windows [Version 10.0.22631.3235]
Bracket matching seems to be broken as of the 1.87 release.
Previously, it worked fine.
It works in many/most files, but under some circumstances it is broken.
I've attached a simple example file (in its entirety!) to illustrate the issue. You'll note that this file is indeed valid; just the bracket matching and coloration makes it look wrong.
Steps to Reproduce:
1. Open a file with brackets, and find that they don't always match.
P.S. I see a lot of people saying that "matches highlighting" is broken in 1.87; that works fine for me.
| not_planned | Bracket matching (and coloring) broken 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~ No... turns out they weren't all disabled.
<!-- ๐ช If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- ๐ฃ Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.87.0
- OS Version: Microsoft Windows [Version 10.0.22631.3235]
Bracket matching seems to be broken as of the 1.87 release.
Previously, it worked fine.
It works in many/most files, but under some circumstances it is broken.
I've attached a simple example file (in its entirety!) to illustrate the issue. You'll note that this file is indeed valid; just the bracket matching and coloration makes it look wrong.
Steps to Reproduce:
1. Open a file with brackets, and find that they don't always match.
P.S. I see a lot of people saying that "matches highlighting" is broken in 1.87; that works fine for me.
| 531 |
206683 | Debug: Attach to Node Process: cannot enable debug mode for process (Error: kill EPERM) | 2024-03-02 14:08:45+00:00 | 2024-04-05 23:15: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. -->
- VS Code Version: 1.86.2
- OS Version: Arch Linux
Steps to Reproduce:
`a.js`:
```js
debugger
```
```
$ code --disable-extensions
$ docker run --rm -itv "$PWD/a.js:/a.js" -p 9229:9229 alpine:3.19 \
sh -euxc 'apk add nodejs && node --inspect-brk=0.0.0.0 a.js'
```
* Ctrl-Shift-P
* Debug: Attach to Node Process
* Choose the `node --inspect-brk` process and you'll see:
With the following command it works (I assume here that you're running under UID 1000):
```
$ docker run --rm -itv "$PWD/a.js:/a.js" -p 9229:9229 alpine:3.19 \
sh -euxc 'apk add nodejs shadow && useradd a \
&& su a -c "node --inspect-brk=0.0.0.0 a.js"'
```
Is it really needed to have access to the process? Chromium DevTools for one doesn't need that. Then the following is rather out of scope, but what about remote debugging?..
| completed | Debug: Attach to Node Process: cannot enable debug mode for process (Error: kill EPERM) <!-- โ ๏ธโ ๏ธ 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.86.2
- OS Version: Arch Linux
Steps to Reproduce:
`a.js`:
```js
debugger
```
```
$ code --disable-extensions
$ docker run --rm -itv "$PWD/a.js:/a.js" -p 9229:9229 alpine:3.19 \
sh -euxc 'apk add nodejs && node --inspect-brk=0.0.0.0 a.js'
```
* Ctrl-Shift-P
* Debug: Attach to Node Process
* Choose the `node --inspect-brk` process and you'll see:
With the following command it works (I assume here that you're running under UID 1000):
```
$ docker run --rm -itv "$PWD/a.js:/a.js" -p 9229:9229 alpine:3.19 \
sh -euxc 'apk add nodejs shadow && useradd a \
&& su a -c "node --inspect-brk=0.0.0.0 a.js"'
```
Is it really needed to have access to the process? Chromium DevTools for one doesn't need that. Then the following is rather out of scope, but what about remote debugging?..
| 682 |
206672 | Merge editor: TypeScript type errors do not appear | 2024-03-02 10:23:03+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.87.0
- OS Version: macOS 14.2.1 (23C71)
Steps to Reproduce:
Install TypeScript and create `main.ts` with contents:
```ts
export const add1 = (n: number) => n + 1;
add1(2)
```
Copy and apply the following patch e.g. using `pbpaste | git apply -3`. This will result in a conflict.
```diff
diff --git a/main.ts b/main.ts
index 4885bfc..bfd86b9 100644
--- a/main.ts
+++ b/main.ts
@@ -1,3 +1,4 @@
export const add1 = (n: number) => n + 1;
+// foo
add1(1)
```
Open the conflict in VS Code's merge editor.
Resolve the conflict but purposefully create a type error.
Expected: the type error should appear.
Actual: the type error does not appear. The type error only appears if I open the file outside of the merge editor.
https://github.com/microsoft/vscode/assets/921609/2b6763b2-d725-4f1b-82d2-16c4355b9671
| Merge editor: TypeScript type errors do not appear <!-- โ ๏ธโ ๏ธ 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.87.0
- OS Version: macOS 14.2.1 (23C71)
Steps to Reproduce:
Install TypeScript and create `main.ts` with contents:
```ts
export const add1 = (n: number) => n + 1;
add1(2)
```
Copy and apply the following patch e.g. using `pbpaste | git apply -3`. This will result in a conflict.
```diff
diff --git a/main.ts b/main.ts
index 4885bfc..bfd86b9 100644
--- a/main.ts
+++ b/main.ts
@@ -1,3 +1,4 @@
export const add1 = (n: number) => n + 1;
+// foo
add1(1)
```
Open the conflict in VS Code's merge editor.
Resolve the conflict but purposefully create a type error.
Expected: the type error should appear.
Actual: the type error does not appear. The type error only appears if I open the file outside of the merge editor.
https://github.com/microsoft/vscode/assets/921609/2b6763b2-d725-4f1b-82d2-16c4355b9671
| 577 | ||
206664 | `SCM: Auto Reveal` does not work consistently in multi repo projects | 2024-03-02 06:29:25+00:00 | 2024-05-27 13:18:10+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.87.0
- OS Version: Windows 10
Steps to Reproduce:
### Image 1: SCM (Source Control)
### Image 2: Explorer
1. In a multi repo project like above, we have 3 repos, and `repo1` is currently selected
2. We switch to `Explorer` to open `repo2-a.md`, make some changes and save
3. Switch to `SCM`, but `repo2-a.md` is not automatically selected even though the `SCM: Auto Reveal` setting is ticked
4. This is because `repo1` is still selected in `Source Control Repositories` (BUG)
5. My expectation was for `repo2` and `repo2-a.md` to be selected when I switch to `SCM` in step 3
| completed | `SCM: Auto Reveal` does not work consistently in multi repo projects <!-- โ ๏ธโ ๏ธ 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.87.0
- OS Version: Windows 10
Steps to Reproduce:
### Image 1: SCM (Source Control)
### Image 2: Explorer
1. In a multi repo project like above, we have 3 repos, and `repo1` is currently selected
2. We switch to `Explorer` to open `repo2-a.md`, make some changes and save
3. Switch to `SCM`, but `repo2-a.md` is not automatically selected even though the `SCM: Auto Reveal` setting is ticked
4. This is because `repo1` is still selected in `Source Control Repositories` (BUG)
5. My expectation was for `repo2` and `repo2-a.md` to be selected when I switch to `SCM` in step 3
| 582 |
206644 | Problems in chat codeblocks show as workspace problems | 2024-03-01 20:55:12+00:00 | 2024-03-04 21:40:40+00:00 | - Send a chat request with this codeblock
~~~
```js
const x = require('
```
~~~
- Make sure the TS extension is activated
- Get an error in the Problems view
| completed | Problems in chat codeblocks show as workspace problems - Send a chat request with this codeblock
~~~
```js
const x = require('
```
~~~
- Make sure the TS extension is activated
- Get an error in the Problems view
| 102 |
206618 | Go To Most Recently Failed Cell - no longer works | 2024-03-01 14:22:04+00:00 | 2024-03-26 17:23:23+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.87
- OS Version: Sonoma 14.2.1
Steps to Reproduce:
1. Create a coding error down a ways in your code
2. At the top of your code click "Execute Cell and Below"
3. Click on Go To Most Recently Failed Cell at top of screen
4. Notice it never goes to the failed cell location
| completed | Go To Most Recently Failed Cell - 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/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.87
- OS Version: Sonoma 14.2.1
Steps to Reproduce:
1. Create a coding error down a ways in your code
2. At the top of your code click "Execute Cell and Below"
3. Click on Go To Most Recently Failed Cell at top of screen
4. Notice it never goes to the failed cell location
| 386 |
206595 | Search panel does not show elements when using view as tree | 2024-03-01 06:34:26+00:00 | 2024-03-01 16:43:53+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.88.0-insider b148975cafa8f034592310659f3dc989b124685c
- OS Version: Darwin arm64 23.2.0
Steps to Reproduce:
1. Open folder
2. Search text
3. Toggle View as Tree
View as Tree
View as List
Mysteriously, some of them do show up when run in a project with many folders...
| completed | Search panel does not show elements when using view as tree <!-- โ ๏ธโ ๏ธ 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.88.0-insider b148975cafa8f034592310659f3dc989b124685c
- OS Version: Darwin arm64 23.2.0
Steps to Reproduce:
1. Open folder
2. Search text
3. Toggle View as Tree
View as Tree
View as List
Mysteriously, some of them do show up when run in a project with many folders...
| 515 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.