Dataset Viewer
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
|
|---|---|---|---|---|---|---|---|
223706
|
Configure unassigned keybindings, command name incorrect
|
2024-07-25 14:34:59+00:00
|
- Place cursor in the panel chat
- Open the accessibility help
- Click on the icon `Accessibility Help Configure Unassigned Keybindings`
- The command list does not contain actual command names
https://github.com/user-attachments/assets/73b8b4da-2bdf-4664-9d47-7c7d2bde73a0
|
Configure unassigned keybindings, command name incorrect - Place cursor in the panel chat
- Open the accessibility help
- Click on the icon `Accessibility Help Configure Unassigned Keybindings`
- The command list does not contain actual command names
https://github.com/user-attachments/assets/73b8b4da-2bdf-4664-9d47-7c7d2bde73a0
| 103 |
||
223658
|
Some suggestions are missing on Windows with pwsh
|
2024-07-25 13:06:40+00:00
|
2024-07-25 16:14:57+00:00
|
I was trying to verify https://github.com/microsoft/vscode/issues/222233.
1. Open VS Code window
2. In pwsh terminal `.\sc`
3. I expect to see a suggestion for the `.\scripts\` folder
|
completed
|
Some suggestions are missing on Windows with pwsh I was trying to verify https://github.com/microsoft/vscode/issues/222233.
1. Open VS Code window
2. In pwsh terminal `.\sc`
3. I expect to see a suggestion for the `.\scripts\` folder
| 109 |
223641
|
Cannot split a terminal without a group [object Object]
|
2024-07-25 12:19:09+00:00
|
https://github.com/microsoft/vscode/blob/b4eb7c94495e25b5dc968a4d3a723346e27f48a3/src/vs/workbench/contrib/terminal/browser/terminalService.ts#L1084
|
Cannot split a terminal without a group [object Object] 
https://github.com/microsoft/vscode/blob/b4eb7c94495e25b5dc968a4d3a723346e27f48a3/src/vs/workbench/contrib/terminal/browser/terminalService.ts#L1084
| 129 |
||
223622
|
SCM - history graph handling of first commit in the repository
|
2024-07-25 10:44:47+00:00
|
- [ ] Show the first commit in the repository when it's the only one
- [ ] Show the contents of the first commit (single select/multi select)
|
SCM - history graph handling of first commit in the repository - [ ] Show the first commit in the repository when it's the only one
- [ ] Show the contents of the first commit (single select/multi select)
| 58 |
||
223607
|
SCM - history graph using incorrect color
|
2024-07-25 09:43:02+00:00
|
2024-07-25 11:02:46+00:00
|
|
completed
|
SCM - history graph using incorrect color 
| 55 |
223601
|
SCM - the refresh action does not refresh the history graph
|
2024-07-25 09:16:10+00:00
|
2024-07-25 09:54:31+00:00
|
Steps to Reproduce:
1. Open a folder/workspace that contains a git repository
2. Create some commits so that you have some outgoing changes in the history graph
3. Open the output window, switch to the Git output channel, and clear the contents
4. Click the "Refresh" action in the "Source Control" viewlet
5. You should see a `git log` entry int the output channel
|
completed
|
SCM - the refresh action does not refresh the history graph Steps to Reproduce:
1. Open a folder/workspace that contains a git repository
2. Create some commits so that you have some outgoing changes in the history graph
3. Open the output window, switch to the Git output channel, and clear the contents
4. Click the "Refresh" action in the "Source Control" viewlet
5. You should see a `git log` entry int the output channel
| 105 |
223582
|
issue reporter dropdown is too large
|
2024-07-25 07:48:54+00:00
|
> Type: Bug
>
> 1. Open Help > Report Issue
>
> The dropdowns are too large....
also make sure `"issueReporter.experimental.auxWindow": true`
the issue with the dropdown seems related to the aux window service. looks like in all zoom levels, it is at `current zoom level + 1`
might consider switching to the custom dropdowns (like we have in settings).
_Originally posted by @kieferrm in https://github.com/microsoft/vscode/issues/223506_
|
issue reporter dropdown is too large > Type: Bug
>
> 1. Open Help > Report Issue
>
> The dropdowns are too large....
also make sure `"issueReporter.experimental.auxWindow": true`
the issue with the dropdown seems related to the aux window service. looks like in all zoom levels, it is at `current zoom level + 1`
might consider switching to the custom dropdowns (like we have in settings).
_Originally posted by @kieferrm in https://github.com/microsoft/vscode/issues/223506_
| 130 |
||
223571
|
Terminal displays UTF graphemes 👩🚒 as 👩<200d>🚒
|
2024-07-25 04:42:44+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.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:07:54.982Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
- OS Version: OS: Darwin x64 21.6.0
Steps to Reproduce:
1. Open terminal, copy and paste 👩🚒
2. terminal cannot display it, instead, it displays 👩<200d>🚒
|
Terminal displays UTF graphemes 👩🚒 as 👩<200d>🚒 <!-- ⚠️⚠️ 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.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:07:54.982Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
- OS Version: OS: Darwin x64 21.6.0
Steps to Reproduce:
1. Open terminal, copy and paste 👩🚒
2. terminal cannot display it, instead, it displays 👩<200d>🚒
| 464 |
||
223564
|
Accessible view doesn't navigate well over empty runCommand responses
|
2024-07-24 23:37:28+00:00
|
Noticed while verifing https://github.com/microsoft/vscode/issues/221497
When I get to the runCommand response, I have to click twice to navigate past it.
|
Accessible view doesn't navigate well over empty runCommand responses Noticed while verifing https://github.com/microsoft/vscode/issues/221497
When I get to the runCommand response, I have to click twice to navigate past it.
| 107 |
||
223550
|
[Testing] Only create test log entry when createTestRun is invoked, do not create one automatically.
|
2024-07-24 21:48: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?: 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.92
- OS Version: all
Multiple (2) "Test run" history entries are created per single `createTestRun` invocation.
This is a request to complete (1) from https://github.com/microsoft/vscode/issues/213182.
//cc @connor4312
|
[Testing] Only create test log entry when createTestRun is invoked, do not create one automatically. <!-- ⚠️⚠️ 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
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.92
- OS Version: all
Multiple (2) "Test run" history entries are created per single `createTestRun` invocation.
This is a request to complete (1) from https://github.com/microsoft/vscode/issues/213182.
//cc @connor4312
| 389 |
||
223528
|
terminal chat help dialog immediately closes
|
2024-07-24 17:41:00+00:00
|
1. open terminal chat
2. use `alt+f1`
3. 🐛 dialog closes
https://github.com/user-attachments/assets/723d1951-92f6-4b28-bc98-0e17a1931f02
|
terminal chat help dialog immediately closes 1. open terminal chat
2. use `alt+f1`
3. 🐛 dialog closes
https://github.com/user-attachments/assets/723d1951-92f6-4b28-bc98-0e17a1931f02
| 63 |
||
223501
|
Issue Reporter: Picking "Feature Request" in first dropdown results in blue button being permanently labelled "Loading data..."
|
2024-07-24 14:53:22+00:00
|
2024-07-25 07:45:35+00:00
|
Type: <b>Bug</b>
1. Launch Issue Reporter, e.g. from `Help: Report Issue` off Command Palette.
2. Change the first dropdown to `Feaure Request`
VS Code version: Code - Insiders 1.92.0-insider (7ed4cdc56d037146b2c4c890f09e78b2ba14b49d, 2024-07-24T07:50:18.385Z)
OS version: Windows_NT x64 10.0.22631
Modes:
<!-- generated by issue reporter -->
|
completed
|
Issue Reporter: Picking "Feature Request" in first dropdown results in blue button being permanently labelled "Loading data..."
Type: <b>Bug</b>
1. Launch Issue Reporter, e.g. from `Help: Report Issue` off Command Palette.
2. Change the first dropdown to `Feaure Request`
VS Code version: Code - Insiders 1.92.0-insider (7ed4cdc56d037146b2c4c890f09e78b2ba14b49d, 2024-07-24T07:50:18.385Z)
OS version: Windows_NT x64 10.0.22631
Modes:
<!-- generated by issue reporter -->
| 157 |
223492
|
SCM - history graph empty after publishing branch
|
2024-07-24 13:06:07+00:00
|
2024-07-24 13:23:38+00:00
|
Steps to Reproduce:
1. Open a folder/workspace that contains a git repository
2. Create a topic branch, and create multiple commits
3. Click the "Publish Branch" action button to publish the topic branch
Expected: history graph should be updated with the label for the published branch
Actual: history graph is empty
|
completed
|
SCM - history graph empty after publishing branch Steps to Reproduce:
1. Open a folder/workspace that contains a git repository
2. Create a topic branch, and create multiple commits
3. Click the "Publish Branch" action button to publish the topic branch
Expected: history graph should be updated with the label for the published branch
Actual: history graph is empty
| 92 |
223490
|
Task times out on the terminal smoke tests
|
2024-07-24 12:40:30+00:00
|
Smoke tests regularly fails with the error:
```
Terminal
Terminal Editors
✔ should update color of the tab
✔ should rename the tab
✔ should show the panel when the terminal is moved there and close the editor
✔ should open a terminal in a new group for open to the side
✔ should open a terminal in a new group when the split button is pressed
1) should create new terminals in the active editor group via command
2) should create new terminals in the active editor group via plus button
3) should create a terminal in the editor area by default
Terminal Input
Auto replies
4) should automatically reply to a custom entry
Terminal Persistence
detach/attach
5) should support basic reconnection
- should persist buffer content
Terminal Profiles
6) should launch the default profile
7) should set the default profile to a contributed one
8) should use the default contributed profile on panel open and for splitting
9) should set the default profile
10) should use the default profile on panel open and for splitting
11) createWithProfile command should create a terminal with a profile
12) createWithProfile command should create a terminal with a contributed profile
##[error]The task has timed out.
Finishing: Run smoke tests (Electron)
```
Example build: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=284839&view=logs&j=7a91b4be-20b5-51ee-04c3-33f03492145f&t=3255846e-ed0b-5948-a22e-d5f1a1fdd237
|
Task times out on the terminal smoke tests Smoke tests regularly fails with the error:
```
Terminal
Terminal Editors
✔ should update color of the tab
✔ should rename the tab
✔ should show the panel when the terminal is moved there and close the editor
✔ should open a terminal in a new group for open to the side
✔ should open a terminal in a new group when the split button is pressed
1) should create new terminals in the active editor group via command
2) should create new terminals in the active editor group via plus button
3) should create a terminal in the editor area by default
Terminal Input
Auto replies
4) should automatically reply to a custom entry
Terminal Persistence
detach/attach
5) should support basic reconnection
- should persist buffer content
Terminal Profiles
6) should launch the default profile
7) should set the default profile to a contributed one
8) should use the default contributed profile on panel open and for splitting
9) should set the default profile
10) should use the default profile on panel open and for splitting
11) createWithProfile command should create a terminal with a profile
12) createWithProfile command should create a terminal with a contributed profile
##[error]The task has timed out.
Finishing: Run smoke tests (Electron)
```
Example build: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=284839&view=logs&j=7a91b4be-20b5-51ee-04c3-33f03492145f&t=3255846e-ed0b-5948-a22e-d5f1a1fdd237
| 364 |
||
223487
|
SCM - incoming/outgoing separator actions rendering issue
|
2024-07-24 11:57:50+00:00
|
2024-07-24 12:23:00+00:00
|
Steps to Reproduce:
1. Launch VS Code Insiders
2. Select the Light (Visual Studio) theme
3. Open the "Source Control" viewlet
4. Click on the Incoming/Outgoing separator (actions are white)
|
completed
|
SCM - incoming/outgoing separator actions rendering issue Steps to Reproduce:
1. Launch VS Code Insiders
2. Select the Light (Visual Studio) theme
3. Open the "Source Control" viewlet
4. Click on the Incoming/Outgoing separator (actions are white)
| 112 |
223475
|
Git - history graph does not show commits for an unpublished repository
|
2024-07-24 08:18:28+00:00
|
2024-07-24 08:38:33+00:00
|
1. Open a folder/workspace in VS Code Insiders
2. Initialise a git repository in the folder
3. Create a file, make changes to it, and create multiple commits
Expected: commits should appear in the history graph
Actual: no commits are being shown in the history graph
|
completed
|
Git - history graph does not show commits for an unpublished repository 1. Open a folder/workspace in VS Code Insiders
2. Initialise a git repository in the folder
3. Create a file, make changes to it, and create multiple commits
Expected: commits should appear in the history graph
Actual: no commits are being shown in the history graph
| 91 |
223455
|
Extension signature verification is failing with SIGSYS error code
|
2024-07-24 04:15:56+00:00
|
In Linux (majorly fedora), extension signature verification is failing with SIGSYS `159` error code
```
SIGSYS
"Signal system call"
The SIGSYS signal is sent to a process when it passes a bad argument to a system call. In practice, this kind of signal is rarely encountered since applications rely on libraries (e.g. libc) to make the call for them. SIGSYS can be received by applications violating the Linux Seccomp security rules configured to restrict them. SIGSYS can also be used to emulate foreign system calls, e.g. emulate Windows system calls on Linux.[19]
```
This issue is investigate and fix this.
|
Extension signature verification is failing with SIGSYS error code In Linux (majorly fedora), extension signature verification is failing with SIGSYS `159` error code
```
SIGSYS
"Signal system call"
The SIGSYS signal is sent to a process when it passes a bad argument to a system call. In practice, this kind of signal is rarely encountered since applications rely on libraries (e.g. libc) to make the call for them. SIGSYS can be received by applications violating the Linux Seccomp security rules configured to restrict them. SIGSYS can also be used to emulate foreign system calls, e.g. emulate Windows system calls on Linux.[19]
```
This issue is investigate and fix this.
| 171 |
||
223432
|
Error: Unable to find repository for current working directory on a windows VM
|
2024-07-23 23:17:28+00:00
|
Testing #223068
I'm on a windows VM on my mac, and I see this error regardless of where my integrated terminal is rooted:
I DO NOT see this error on non-VM windows install.
|
Error: Unable to find repository for current working directory on a windows VM Testing #223068
I'm on a windows VM on my mac, and I see this error regardless of where my integrated terminal is rooted:
I DO NOT see this error on non-VM windows install.
| 108 |
||
223431
|
Repeats breakpoint announcement twice
|
2024-07-23 23:13:07+00:00
|
Testing #222238
This is the same recording as in #223429 . It seems to be announcing the breakpoint twice. Not sure if this is a issue.
https://github.com/user-attachments/assets/3ce59bc5-1cf9-4191-8fa4-ec92c87810d9
|
Repeats breakpoint announcement twice Testing #222238
This is the same recording as in #223429 . It seems to be announcing the breakpoint twice. Not sure if this is a issue.
https://github.com/user-attachments/assets/3ce59bc5-1cf9-4191-8fa4-ec92c87810d9
| 82 |
||
223430
|
Issue Title
|
2024-07-23 23:12:55+00:00
|
2024-07-23 23:13: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/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.
2.
<!-- Edit the body of your new issue then click the ✓ "Create Issue" button in the top right of the editor. The first line will be the issue title. Assignees and Labels follow after a blank line. Leave an empty line before beginning the body of the issue. -->
|
not_planned
|
Issue Title <!-- ⚠️⚠️ 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.
2.
<!-- Edit the body of your new issue then click the ✓ "Create Issue" button in the top right of the editor. The first line will be the issue title. Assignees and Labels follow after a blank line. Leave an empty line before beginning the body of the issue. -->
| 380 |
223428
|
Dismiss button doesn't work
|
2024-07-23 23:09:28+00:00
|
2024-07-23 23:19:33+00:00
|
1. Create a new empty profile
2. Open a new window with that profile
3. Wait for the window to load
4. Open the Settings editor
5. Verify that a Copilot entry shows up under Commonly Used. If not, try reloading the window
6. Press the dismiss button
7. :bug: Entry does not dismiss
I'm unable to repro this issue locally
|
completed
|
Dismiss button doesn't work 1. Create a new empty profile
2. Open a new window with that profile
3. Wait for the window to load
4. Open the Settings editor
5. Verify that a Copilot entry shows up under Commonly Used. If not, try reloading the window
6. Press the dismiss button
7. :bug: Entry does not dismiss
I'm unable to repro this issue locally
| 88 |
223420
|
Unsure about when to expect suggestions to automatically appear
|
2024-07-23 22:55:02+00:00
|
2024-07-25 13:08:18+00:00
|
Testing #223130
I notice that sometimes, I need to trigger the suggest widget manually (ctrl+space). For example, I have` git add .\.vscode\notebooks\` typed, and I need to ctrl+space to see the filenames.
|
completed
|
Unsure about when to expect suggestions to automatically appear Testing #223130
I notice that sometimes, I need to trigger the suggest widget manually (ctrl+space). For example, I have` git add .\.vscode\notebooks\` typed, and I need to ctrl+space to see the filenames.
| 74 |
223410
|
Inline diff line numbers broken after reload
|
2024-07-23 22:02:31+00:00
|
2024-07-24 14:43:19+00:00
|
Type: <b>Bug</b>
1. In a git repo
2. Make a small change in a tracked file
3. Open diff from `changes` scm view
4. Make sure inline diff is on
5. Reload window so that diff editor is also reloaded
**bug**
The wrong line numbers are shown. Notice how many lines `1` there are on the left gutter
VS Code version: Code - Insiders 1.92.0-insider (Universal) (22e3447b4b410dcf8426bf70743c5dd4030d6122, 2024-07-23T05:03:52.385Z)
OS version: Darwin arm64 23.5.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M2 Max (12 x 2400)|
|GPU Status|2d_canvas: unavailable_software<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: disabled_software<br>multiple_raster_threads: enabled_on<br>opengl: disabled_off<br>rasterization: disabled_software<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: disabled_software<br>video_encode: disabled_software<br>webgl: unavailable_software<br>webgl2: unavailable_software<br>webgpu: unavailable_software<br>webnn: disabled_off|
|Load (avg)|10, 6, 5|
|Memory (System)|64.00GB (1.61GB free)|
|Process Argv|--crash-reporter-id 0fffb5da-9cd7-46fd-9e7f-a1564e8c5fda|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
|
completed
|
Inline diff line numbers broken after reload
Type: <b>Bug</b>
1. In a git repo
2. Make a small change in a tracked file
3. Open diff from `changes` scm view
4. Make sure inline diff is on
5. Reload window so that diff editor is also reloaded
**bug**
The wrong line numbers are shown. Notice how many lines `1` there are on the left gutter
VS Code version: Code - Insiders 1.92.0-insider (Universal) (22e3447b4b410dcf8426bf70743c5dd4030d6122, 2024-07-23T05:03:52.385Z)
OS version: Darwin arm64 23.5.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Apple M2 Max (12 x 2400)|
|GPU Status|2d_canvas: unavailable_software<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: disabled_software<br>multiple_raster_threads: enabled_on<br>opengl: disabled_off<br>rasterization: disabled_software<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: disabled_software<br>video_encode: disabled_software<br>webgl: unavailable_software<br>webgl2: unavailable_software<br>webgpu: unavailable_software<br>webnn: disabled_off|
|Load (avg)|10, 6, 5|
|Memory (System)|64.00GB (1.61GB free)|
|Process Argv|--crash-reporter-id 0fffb5da-9cd7-46fd-9e7f-a1564e8c5fda|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
| 548 |
223405
|
Only one changed variable gets announced by screen reader
|
2024-07-23 21:47:41+00:00
|
Testing #222239
1. use this script and create a launch config to launch it with node.
```
console.log('here');
let j = 0;
let i =0;
console.log('done');
```
2. Set a breakpoint on the first and last lines. Add `i` and `j` to the watch.
3. monitor the screen reading between the first and second
4. Notice that only `j=0` is announced when you go from the first to second breakpoint.
|
Only one changed variable gets announced by screen reader Testing #222239
1. use this script and create a launch config to launch it with node.
```
console.log('here');
let j = 0;
let i =0;
console.log('done');
```
2. Set a breakpoint on the first and last lines. Add `i` and `j` to the watch.
3. monitor the screen reading between the first and second
4. Notice that only `j=0` is announced when you go from the first to second breakpoint.
| 119 |
||
223402
|
Settings description should format keyboard key labels
|
2024-07-23 21:40:36+00:00
|
2024-07-24 15:12:22+00:00
|
Testing #223130
I know we are inconsistent, but can we put keyboard key labels in backticks
|
completed
|
Settings description should format keyboard key labels Testing #223130
I know we are inconsistent, but can we put keyboard key labels in backticks
| 122 |
223397
|
FindFiles2OptionsNew.useIgnoreFiles feedback
|
2024-07-23 21:24:46+00:00
|
Testing #223154
https://github.com/microsoft/vscode/blob/d4bb523d43261a3ec2c4c9ca01052faeb0a874e7/src/vscode-dts/vscode.proposed.findFiles2New.d.ts#L25-L51
Should this be named `ignoreFileOverrides` or similar instead to make it more clear that not using it is fine and will likely be what the user expects?
|
FindFiles2OptionsNew.useIgnoreFiles feedback Testing #223154
https://github.com/microsoft/vscode/blob/d4bb523d43261a3ec2c4c9ca01052faeb0a874e7/src/vscode-dts/vscode.proposed.findFiles2New.d.ts#L25-L51
Should this be named `ignoreFileOverrides` or similar instead to make it more clear that not using it is fine and will likely be what the user expects?
| 133 |
||
223395
|
Does FindFiles2OptionsNew.maxResults impact performance?
|
2024-07-23 21:18:06+00:00
|
Testing #223154
If so, should we mention it?
https://github.com/microsoft/vscode/blob/d4bb523d43261a3ec2c4c9ca01052faeb0a874e7/src/vscode-dts/vscode.proposed.findFiles2New.d.ts#L20-L23
Also, should this have a conservative default value to help developers from misusing it?
|
Does FindFiles2OptionsNew.maxResults impact performance? Testing #223154
If so, should we mention it?
https://github.com/microsoft/vscode/blob/d4bb523d43261a3ec2c4c9ca01052faeb0a874e7/src/vscode-dts/vscode.proposed.findFiles2New.d.ts#L20-L23
Also, should this have a conservative default value to help developers from misusing it?
| 125 |
||
223394
|
Don't use "we" in apis
|
2024-07-23 21:16:05+00:00
|
Testing #223154
https://github.com/microsoft/vscode/blob/d4bb523d43261a3ec2c4c9ca01052faeb0a874e7/src/vscode-dts/vscode.proposed.findFiles2New.d.ts#L25-L27
|
Don't use "we" in apis Testing #223154
https://github.com/microsoft/vscode/blob/d4bb523d43261a3ec2c4c9ca01052faeb0a874e7/src/vscode-dts/vscode.proposed.findFiles2New.d.ts#L25-L27
| 91 |
||
223391
|
Retain object types in doc comments
|
2024-07-23 21:09:32+00:00
|
Testing #223154
https://github.com/microsoft/vscode/blob/d4bb523d43261a3ec2c4c9ca01052faeb0a874e7/src/vscode-dts/vscode.proposed.findFiles2New.d.ts#L62-L78
<img width="849" alt="Screenshot 2024-07-23 at 2 08 51 PM" src="https://github.com/user-attachments/assets/b4545156-7677-4435-98bc-5858c0b242d2">
When I first read this I assumed both `glob pattern` and `relative pattern` was talking about a string. If we keep the object name it makes it clear that it's talking about a type:
<img width="826" alt="Screenshot 2024-07-23 at 2 09 27 PM" src="https://github.com/user-attachments/assets/d1821c64-1e69-42ae-96a4-fe14f4eb8779">
|
Retain object types in doc comments Testing #223154
https://github.com/microsoft/vscode/blob/d4bb523d43261a3ec2c4c9ca01052faeb0a874e7/src/vscode-dts/vscode.proposed.findFiles2New.d.ts#L62-L78
<img width="849" alt="Screenshot 2024-07-23 at 2 08 51 PM" src="https://github.com/user-attachments/assets/b4545156-7677-4435-98bc-5858c0b242d2">
When I first read this I assumed both `glob pattern` and `relative pattern` was talking about a string. If we keep the object name it makes it clear that it's talking about a type:
<img width="826" alt="Screenshot 2024-07-23 at 2 09 27 PM" src="https://github.com/user-attachments/assets/d1821c64-1e69-42ae-96a4-fe14f4eb8779">
| 262 |
||
223389
|
Settings deep-linking issues when extensions update
|
2024-07-23 21:07:56+00:00
|
Testing #223027
I'm not able to get this feature working on my linux host 😓 Attached a video for clarity.
https://github.com/user-attachments/assets/2afdd792-de8e-4773-aff2-88d0aa9fa4ed
# Repro steps
_Tested on Ubuntu 24.04_
1. Install and launch VS Code Insiders
1. Install Remote - SSH pre-release (or try with a different setting)
1. Open default browser in Ubuntu 22.04 (Firefox)
1. Paste in a deep link (eg: `vscode-insiders://settings/remote.SSH.permitPtyAllocation`)
1. I also tried following a link on a mock website, source:
```html
<head><title>Title></title></head>
<body>
<a href="vscode-insiders://settings/remote.SSH.permitPtyAllocation">CLICK ME</a>
</body>
```
1. Note that VS Code launches but we aren't deep linked into settings
These steps work successfully for me on my MacOS host
|
reopened
|
Settings deep-linking issues when extensions update Testing #223027
I'm not able to get this feature working on my linux host 😓 Attached a video for clarity.
https://github.com/user-attachments/assets/2afdd792-de8e-4773-aff2-88d0aa9fa4ed
# Repro steps
_Tested on Ubuntu 24.04_
1. Install and launch VS Code Insiders
1. Install Remote - SSH pre-release (or try with a different setting)
1. Open default browser in Ubuntu 22.04 (Firefox)
1. Paste in a deep link (eg: `vscode-insiders://settings/remote.SSH.permitPtyAllocation`)
1. I also tried following a link on a mock website, source:
```html
<head><title>Title></title></head>
<body>
<a href="vscode-insiders://settings/remote.SSH.permitPtyAllocation">CLICK ME</a>
</body>
```
1. Note that VS Code launches but we aren't deep linked into settings
These steps work successfully for me on my MacOS host
| 269 |
|
223384
|
Enum values should start with caps
|
2024-07-23 21:01:24+00:00
|
Testing #223154
https://github.com/microsoft/vscode/blob/d4bb523d43261a3ec2c4c9ca01052faeb0a874e7/src/vscode-dts/vscode.proposed.findTextInFilesNew.d.ts#L112-L128
|
Enum values should start with caps Testing #223154
https://github.com/microsoft/vscode/blob/d4bb523d43261a3ec2c4c9ca01052faeb0a874e7/src/vscode-dts/vscode.proposed.findTextInFilesNew.d.ts#L112-L128
| 90 |
||
223383
|
Debug console sticky scroll is much larger than its content
|
2024-07-23 20:58:37+00:00
|
Repro:
A logged a large array when testing a proposed API and saw this:
<img width="1356" alt="Screenshot 2024-07-23 at 1 57 41 PM" src="https://github.com/user-attachments/assets/b48d4b96-567f-45aa-82fc-95c4d49082a2">
Code:
```ts
const disposable = vscode.commands.registerCommand('test.helloWorld', async () => {
const result = await vscode.workspace.findFiles2New(["**/*.ts"]);
console.log(result);
});
```
|
Debug console sticky scroll is much larger than its content Repro:
A logged a large array when testing a proposed API and saw this:
<img width="1356" alt="Screenshot 2024-07-23 at 1 57 41 PM" src="https://github.com/user-attachments/assets/b48d4b96-567f-45aa-82fc-95c4d49082a2">
Code:
```ts
const disposable = vscode.commands.registerCommand('test.helloWorld', async () => {
const result = await vscode.workspace.findFiles2New(["**/*.ts"]);
console.log(result);
});
```
| 178 |
||
223382
|
Scrolling is not working on contents section
|
2024-07-23 20:54:37+00:00
|
2024-07-24 05:28:28+00:00
|
Testing #223080
1. Open the Profiles view, and choose a profile.
2. Open settings.
3. Open one extension.
4. When the width of the window is too small, the two finger gesture in Mac to scroll does not work. So i can not scroll. 🐛
<img width="1425" alt="Screenshot 2024-07-23 at 1 45 53 PM" src="https://github.com/user-attachments/assets/eee9bee6-c77e-44cd-bb2d-1a1907d39b7f">
|
completed
|
Scrolling is not working on contents section Testing #223080
1. Open the Profiles view, and choose a profile.
2. Open settings.
3. Open one extension.
4. When the width of the window is too small, the two finger gesture in Mac to scroll does not work. So i can not scroll. 🐛
<img width="1425" alt="Screenshot 2024-07-23 at 1 45 53 PM" src="https://github.com/user-attachments/assets/eee9bee6-c77e-44cd-bb2d-1a1907d39b7f">
| 142 |
223380
|
Open to the side action is not working properly
|
2024-07-23 20:41:13+00:00
|
2024-07-24 04:39:04+00:00
|
Testing #223080
When i am creating a Profile:
1. Select a copy from: `Python`
2. In the case of Settings the default option selected is python, i click on `Open to the side Action`
3. It will open the setting for Python
4. Close the settings.
5. Change the source to default, and click again `Open to the side Action`
6. It opened again the `Python Settings` and not the `default settings`. 🐛
<img width="1170" alt="Screenshot 2024-07-23 at 1 39 24 PM" src="https://github.com/user-attachments/assets/53ed4aaf-d67c-4849-8275-128f071aceae">
|
completed
|
Open to the side action is not working properly Testing #223080
When i am creating a Profile:
1. Select a copy from: `Python`
2. In the case of Settings the default option selected is python, i click on `Open to the side Action`
3. It will open the setting for Python
4. Close the settings.
5. Change the source to default, and click again `Open to the side Action`
6. It opened again the `Python Settings` and not the `default settings`. 🐛
<img width="1170" alt="Screenshot 2024-07-23 at 1 39 24 PM" src="https://github.com/user-attachments/assets/53ed4aaf-d67c-4849-8275-128f071aceae">
| 178 |
223379
|
run and debug accessibility dialog typo
|
2024-07-23 20:34:23+00:00
|
2024-07-24 17:08:00+00:00
|
`The debug console is a REPL (Read-Eval-Print-Loop) that allows you to evaluate expressions and run commands and can be focused with<keybinding:workbench.panel.repl.view.focus.`
|
completed
|
run and debug accessibility dialog typo
`The debug console is a REPL (Read-Eval-Print-Loop) that allows you to evaluate expressions and run commands and can be focused with<keybinding:workbench.panel.repl.view.focus.`
| 114 |
223374
|
`workbench.action.terminal.sendSequence` keybinding does not trigger on linux
|
2024-07-23 19:48:13+00:00
|
Testing #223130
On Linux, `workbench.action.terminalsendSequence` doesn't fire correctly on `ctrl+space` because it checks for `terminalShellType == 'pwsh'`. However, when looking at the context keys, `terminalShellType` is not set
|
`workbench.action.terminal.sendSequence` keybinding does not trigger on linux Testing #223130
On Linux, `workbench.action.terminalsendSequence` doesn't fire correctly on `ctrl+space` because it checks for `terminalShellType == 'pwsh'`. However, when looking at the context keys, `terminalShellType` is not set
| 100 |
||
223373
|
Resizing stacktrace UI causes a line to be hidden
|
2024-07-23 19:46:11+00:00
|
Testing #223148
There's only one frame in the stack trace, pull down to resize and notice how a line goes missing from the editor.
Line 116 vanishes
|
Resizing stacktrace UI causes a line to be hidden Testing #223148
There's only one frame in the stack trace, pull down to resize and notice how a line goes missing from the editor.
Line 116 vanishes
| 96 |
||
223369
|
Add `Unassigned` to command description for clarity
|
2024-07-23 18:45:20+00:00
|
2024-07-24 17:01:28+00:00
|
> I noticed that the first keybinding label is `Accessibility Help Configure Keybindings`, the second is `Accessibility Help Configure Assigned Keybindings`. The first label does not mention that the keybindings are not unassigned, perhaps we could add the word `unassigned` before?
_Originally posted by @aiday-mar in [#221744](https://github.com/microsoft/vscode/issues/221744#issuecomment-2245233032)_
|
completed
|
Add `Unassigned` to command description for clarity > I noticed that the first keybinding label is `Accessibility Help Configure Keybindings`, the second is `Accessibility Help Configure Assigned Keybindings`. The first label does not mention that the keybindings are not unassigned, perhaps we could add the word `unassigned` before?
_Originally posted by @aiday-mar in [#221744](https://github.com/microsoft/vscode/issues/221744#issuecomment-2245233032)_
| 134 |
223368
|
Extension hover is often dismissed too early
|
2024-07-23 18:35:21+00:00
|
Testing #223090
The hover widget of the extension is often dismissed too early and making it hard to move cursor to the hover widget and click on the links.
https://github.com/user-attachments/assets/89aff1b2-5c54-45c4-9ed9-3a1b4017a509
From the recording above you can see that I only get it working 1 out of 3 times.
|
Extension hover is often dismissed too early Testing #223090
The hover widget of the extension is often dismissed too early and making it hard to move cursor to the hover widget and click on the links.
https://github.com/user-attachments/assets/89aff1b2-5c54-45c4-9ed9-3a1b4017a509
From the recording above you can see that I only get it working 1 out of 3 times.
| 108 |
||
223367
|
Clicking on "View Commit" re opens a new editor diff view for the same commit
|
2024-07-23 18:34:29+00:00
|
2024-07-24 10:59:28+00:00
|
Testing #223106
Have remote commits.
Click on a remote commit to view the commit
Use the commit menu to view the commit
Expected: Focus shifts to the already opened editor
Actual: New diff editor opened for the commit.
|
completed
|
Clicking on "View Commit" re opens a new editor diff view for the same commit Testing #223106
Have remote commits.
Click on a remote commit to view the commit
Use the commit menu to view the commit
Expected: Focus shifts to the already opened editor
Actual: New diff editor opened for the commit.
| 120 |
223364
|
Clicking on the ticked item for the remote branch in the Incoming/Outgoing header clears out the SCM view.
|
2024-07-23 18:15:03+00:00
|
2024-07-24 14:39:58+00:00
|
Testing #223106
>Confirm that there is a ticked item for the remote branch (ex: origin/main)
See repro below:
|
completed
|
Clicking on the ticked item for the remote branch in the Incoming/Outgoing header clears out the SCM view. Testing #223106
>Confirm that there is a ticked item for the remote branch (ex: origin/main)
See repro below:
| 108 |
223360
|
Terminal: Sparkle cheese and variable line spacing when holding down Enter key
|
2024-07-23 17:51:04+00:00
|
When pressing and holding the Enter key on a folder for a while I get mixed results regarding spacing between the prompts, with a few Copilot Sparkles sprinkled in.
to repro just open a terminal and hold down the Enter key:
Note I'm on WSL.
|
Terminal: Sparkle cheese and variable line spacing when holding down Enter key When pressing and holding the Enter key on a folder for a while I get mixed results regarding spacing between the prompts, with a few Copilot Sparkles sprinkled in.
to repro just open a terminal and hold down the Enter key:
Note I'm on WSL.
| 122 |
||
223358
|
Terminal Scrollbar: Right Click on scrollbar does paste not scroll
|
2024-07-23 17:42:34+00:00
|
Testing #223132
Right clicking on the scrollbar does a paste into the terminal, as if I was in any other part of the terminal. Given the behavior of scrollbars in the editor I expected the terminal to scroll at a minimum (and a context menu might be nice).
|
Terminal Scrollbar: Right Click on scrollbar does paste not scroll Testing #223132
Right clicking on the scrollbar does a paste into the terminal, as if I was in any other part of the terminal. Given the behavior of scrollbars in the editor I expected the terminal to scroll at a minimum (and a context menu might be nice).
| 75 |
||
223356
|
Terminal Scroll Bar: Cursor location indicator not always visible
|
2024-07-23 17:33:55+00:00
|
Testing #223132
When doing a Find in the Terminal, I see the horizontal bar which indicates where the cursor is in the terminal history/buffer. Otherwise, there is no cursor location indicator. Given how the scrollbar works in a normal editor, I expected to see the cursor location indicator regardless.
Find:
without find (`code` is selected):
|
Terminal Scroll Bar: Cursor location indicator not always visible Testing #223132
When doing a Find in the Terminal, I see the horizontal bar which indicates where the cursor is in the terminal history/buffer. Otherwise, there is no cursor location indicator. Given how the scrollbar works in a normal editor, I expected to see the cursor location indicator regardless.
Find:
without find (`code` is selected):
| 180 |
||
223355
|
Multi-line ohmyposh themes don't work with terminal suggest
|
2024-07-23 17:25:27+00:00
|
Testing #223130
I'm on windows.
1. Powershell `$PROFILE` is:
```
Import-Module -Name Terminal-Icons
oh-my-posh init pwsh --config "$env:POSH_THEMES_PATH\tokyonight_storm.omp.json" | Invoke-Expression
```
2. Seems that the debug only recognizes the first line of input
|
Multi-line ohmyposh themes don't work with terminal suggest Testing #223130
I'm on windows.
1. Powershell `$PROFILE` is:
```
Import-Module -Name Terminal-Icons
oh-my-posh init pwsh --config "$env:POSH_THEMES_PATH\tokyonight_storm.omp.json" | Invoke-Expression
```
2. Seems that the debug only recognizes the first line of input
| 156 |
||
223352
|
alt+f2 doesn't show console info if debug session is done
|
2024-07-23 16:48:16+00:00
|
Testing #222238
1. Make a js file at the root that console.logs something.
2. Make a launch config to run it using node like:
```
{
"name": "Run Test JS file 1",
"program": "${workspaceFolder}/test1.js",
"request": "launch",
"skipFiles": [
"<node_internals>/**"
],
"type": "node"
}
```
3. Run it and see the logs persist in the debug console.]
4. Try to use alt+f2 to read it
5. 'no debug session is active'
|
alt+f2 doesn't show console info if debug session is done Testing #222238
1. Make a js file at the root that console.logs something.
2. Make a launch config to run it using node like:
```
{
"name": "Run Test JS file 1",
"program": "${workspaceFolder}/test1.js",
"request": "launch",
"skipFiles": [
"<node_internals>/**"
],
"type": "node"
}
```
3. Run it and see the logs persist in the debug console.]
4. Try to use alt+f2 to read it
5. 'no debug session is active'
| 210 |
||
223350
|
NVDA reads REPL as 'replace'
|
2024-07-23 16:34:59+00:00
|
2024-07-24 17:08:00+00:00
|
Testing #222238
Not sure whether this is something in your control, but I noticed that NVDA reads REPL as replace when it's reading this:
Might be a bit confusing.
|
completed
|
NVDA reads REPL as 'replace' Testing #222238
Not sure whether this is something in your control, but I noticed that NVDA reads REPL as replace when it's reading this:
Might be a bit confusing.
| 103 |
223347
|
No support for tsx files in notebooks
|
2024-07-23 16:19:05+00:00
|
Testing #223152
1) paste TSX source into a cell -> there is no language support for TSX
|
No support for tsx files in notebooks Testing #223152
1) paste TSX source into a cell -> there is no language support for TSX
| 33 |
||
223344
|
Handling of cells outside of viewport
|
2024-07-23 16:11:51+00:00
|
Testing #223152
1) select two cells
2) scroll the lower cell (cell 2) out of the viewport
3) cmd+/
4) scroll cell 2 partially into the viewport -> only cell 1 has been commented
5) cmd+/ -> cell 1 has been uncommented, cell 2 has been commented
After step 3 I'd expect both cells to be commented and after step 5 both to be uncommented
|
Handling of cells outside of viewport Testing #223152
1) select two cells
2) scroll the lower cell (cell 2) out of the viewport
3) cmd+/
4) scroll cell 2 partially into the viewport -> only cell 1 has been commented
5) cmd+/ -> cell 1 has been uncommented, cell 2 has been commented
After step 3 I'd expect both cells to be commented and after step 5 both to be uncommented
| 102 |
||
223343
|
Selection management
|
2024-07-23 16:07:49+00:00
|
2024-07-25 22:43:14+00:00
|
Testing #223152
1) set a selection within a given cell
2) ESC -> cell gets focus
3) Cmd+/ -> selection from step 1 is lost and all content of the cell is selected
4) Arrow-up or down
5) Cmd+/ -> now you have two cells with fully selected content
I would expect that the selection from step 1 is retained/restored. And, if I don't have a selection after step 3, no selection would be visible.
|
completed
|
Selection management Testing #223152
1) set a selection within a given cell
2) ESC -> cell gets focus
3) Cmd+/ -> selection from step 1 is lost and all content of the cell is selected
4) Arrow-up or down
5) Cmd+/ -> now you have two cells with fully selected content
I would expect that the selection from step 1 is retained/restored. And, if I don't have a selection after step 3, no selection would be visible.
| 104 |
223342
|
Not prompted for credentials on reload despite not having checked 'Remember my credentials'
|
2024-07-23 15:59:07+00:00
|
2024-07-24 10:39:16+00:00
|
Testing #221327
I can only retrigger the auth dialog after changing the user1 password. Is that expected?
|
completed
|
Not prompted for credentials on reload despite not having checked 'Remember my credentials' Testing #221327
I can only retrigger the auth dialog after changing the user1 password. Is that expected?
| 54 |
223338
|
`onDidTriggerButton` description is incorrect
|
2024-07-23 15:41:17+00:00
|
2024-07-24 18:04:51+00:00
|
Testing #223135
This description says only for the tittle bar but it also fires for inline buttons
```
/**
* An event signaling when a button in the title bar was triggered.
* This event does not fire for buttons on a {@link QuickPickItem}.
*/
readonly onDidTriggerButton: Event<QuickInputButton>;
```
|
completed
|
`onDidTriggerButton` description is incorrect Testing #223135
This description says only for the tittle bar but it also fires for inline buttons
```
/**
* An event signaling when a button in the title bar was triggered.
* This event does not fire for buttons on a {@link QuickPickItem}.
*/
readonly onDidTriggerButton: Event<QuickInputButton>;
```
| 104 |
223334
|
a11y help reports no assigned keybinding for Go to Next Commenting Range and Go to Previous Commenting Range
|
2024-07-23 15:21:14+00:00
|
Testing #222240
When I open the keybinding editor it seems we already have keybindings for these:
|
a11y help reports no assigned keybinding for Go to Next Commenting Range and Go to Previous Commenting Range Testing #222240
When I open the keybinding editor it seems we already have keybindings for these:
| 141 |
||
223333
|
Inline chat a11y help text is indistinguishable from panel chat a11y help text
|
2024-07-23 15:17:04+00:00
|
2024-07-25 19:12:15+00:00
|
Testing #222240
Maybe a11y help is showing me stale text from the last panel chat invocation (even after I closed the panel chat view), but the help text seems to be the same when I focus an inline chat response and do Alt F1.
|
completed
|
Inline chat a11y help text is indistinguishable from panel chat a11y help text Testing #222240
Maybe a11y help is showing me stale text from the last panel chat invocation (even after I closed the panel chat view), but the help text seems to be the same when I focus an inline chat response and do Alt F1.
| 78 |
223332
|
Chat a11y help dialog mentions Chat Clear command that doesn't exist in keybinding editor
|
2024-07-23 15:12:44+00:00
|
Testing #222240
Should this be New Chat (Ctrl+L)?
|
Chat a11y help dialog mentions Chat Clear command that doesn't exist in keybinding editor Testing #222240
Should this be New Chat (Ctrl+L)?
| 40 |
||
223330
|
Typo in notebook a11y help dialog text
|
2024-07-23 15:06:51+00:00
|
2024-07-24 17:04:38+00:00
|
Testing #222240
> The Insert Cell Above/Below commands will create new empty code cells
should be terminated with a `.`
|
completed
|
Typo in notebook a11y help dialog text Testing #222240
> The Insert Cell Above/Below commands will create new empty code cells
should be terminated with a `.`
| 45 |
223329
|
"Configure Keybindings" action appears in quick pick toolbar but does nothing when clicked in a11y dialog for notebooks
|
2024-07-23 15:03:39+00:00
|
2024-07-24 22:43:52+00:00
|
Testing #222240
In this context when there are no unassigned keybindings, perhaps the action should be disabled or not added?
|
completed
|
"Configure Keybindings" action appears in quick pick toolbar but does nothing when clicked in a11y dialog for notebooks Testing #222240
In this context when there are no unassigned keybindings, perhaps the action should be disabled or not added?
| 102 |
223318
|
Extension update - review extension does not always focus the changelog tab
|
2024-07-23 13:30:07+00:00
|
2024-07-24 04:49:24+00:00
|
Testing #223090
1. Close all opened editors
2. Open the Extensions viewlet, hover on a extension that is not auto-updated, and click on the "review the extension" link. This will open the extension details in the editor and will focus the "Changelog" tab.
3. Click on the "Details" tab in the extension editor
4. Click on the "Update"button which will show a warning dialog
5. Click on the "Review" button
* This should focus the "Changelog" tab but it does not
|
completed
|
Extension update - review extension does not always focus the changelog tab Testing #223090
1. Close all opened editors
2. Open the Extensions viewlet, hover on a extension that is not auto-updated, and click on the "review the extension" link. This will open the extension details in the editor and will focus the "Changelog" tab.
3. Click on the "Details" tab in the extension editor
4. Click on the "Update"button which will show a warning dialog
5. Click on the "Review" button
* This should focus the "Changelog" tab but it does not
| 133 |
223316
|
Completions do not show up after accepting part of the path to folder
|
2024-07-23 13:27:45+00:00
|
2024-07-25 15:51:32+00:00
|
Testing #223130
- Open the folder where the `vscode` repo is located. Type `open v`
- Completions should show up with `vscode` inside of the list.
- Select the result `vscode` from the list.
- The result `cd ./vscode/` is added into the powershell terminal
- After the addition the completions list does not automatically appear to suggest the next part of the path 🐛
https://github.com/user-attachments/assets/83b7ab43-e3c2-46e6-ba8d-76c7006dd0c5
|
completed
|
Completions do not show up after accepting part of the path to folder Testing #223130
- Open the folder where the `vscode` repo is located. Type `open v`
- Completions should show up with `vscode` inside of the list.
- Select the result `vscode` from the list.
- The result `cd ./vscode/` is added into the powershell terminal
- After the addition the completions list does not automatically appear to suggest the next part of the path 🐛
https://github.com/user-attachments/assets/83b7ab43-e3c2-46e6-ba8d-76c7006dd0c5
| 154 |
223315
|
"debug.autoExpandLazyVariables": false replaced with the default
|
2024-07-23 13:22:34+00:00
|
2024-07-24 19:25:15+00:00
|
Testing #222238
There does not seem to be a need to keep the setting in the JSON, it can be removed because "auto" (with which the value is replaced) is the new default.
|
completed
|
"debug.autoExpandLazyVariables": false replaced with the default Testing #222238
There does not seem to be a need to keep the setting in the JSON, it can be removed because "auto" (with which the value is replaced) is the new default.
| 66 |
223308
|
Wrong auto-indentation in typescript when pasting
|
2024-07-23 12:20:33+00:00
|
<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.91.1
- OS Version:
Steps to Reproduce:
1. Start with this code.
```ts
if (true)
{
// Do something.
}
```
2. Select and cut the the block.
3. Paste it back:
```ts
if (true)
{
// Do something.
}
```
Related to issue #209802.
|
Wrong auto-indentation in typescript when pasting <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.91.1
- OS Version:
Steps to Reproduce:
1. Start with this code.
```ts
if (true)
{
// Do something.
}
```
2. Select and cut the the block.
3. Paste it back:
```ts
if (true)
{
// Do something.
}
```
Related to issue #209802.
| 384 |
||
223305
|
Hover shows zero files changed even though opening the commit shows the files diff
|
2024-07-23 11:30:42+00:00
|
2024-07-25 13:43:57+00:00
|
Testing #223106
Hover shows zero files changed even though clicking on the commit shows multiple files changes
https://github.com/user-attachments/assets/c7c7ce67-0739-4be9-9b62-613712ac72f3
|
completed
|
Hover shows zero files changed even though opening the commit shows the files diff Testing #223106
Hover shows zero files changed even though clicking on the commit shows multiple files changes
https://github.com/user-attachments/assets/c7c7ce67-0739-4be9-9b62-613712ac72f3
| 78 |
223304
|
Cannot register two commands with the same id:
|
2024-07-23 11:29:35+00:00
|
2024-07-24 05:12:58+00:00
|
Testing #223080
ERR Cannot register two commands with the same id: workbench.action.openProfile.empty: Error: Cannot register two commands with the same id: workbench.action.openProfile.empty
(used the split editor command)
|
completed
|
Cannot register two commands with the same id: Testing #223080
ERR Cannot register two commands with the same id: workbench.action.openProfile.empty: Error: Cannot register two commands with the same id: workbench.action.openProfile.empty
(used the split editor command)
| 119 |
223299
|
"Create" becomes "Replace" only after changing name and back.
|
2024-07-23 11:21:25+00:00
|
2024-07-24 03:27:59+00:00
|
Testing #223080
"Create" becomes "Replace" only after changing name and back.
|
completed
|
"Create" becomes "Replace" only after changing name and back. Testing #223080
"Create" becomes "Replace" only after changing name and back.
| 83 |
223291
|
Settings URL handling - "Open Current File as Release Notes" command not working
|
2024-07-23 10:49:12+00:00
|
2024-07-24 14:52:51+00:00
|
Testing #223027
* Created a new Markdown file - test.md
* Added the release notes sample to the file and saved it
* Invoked the "Open Current File as Release Notes" command and it failed
Not seeing anything in the developer tools console nor in the various output channel logs.
|
completed
|
Settings URL handling - "Open Current File as Release Notes" command not working Testing #223027
* Created a new Markdown file - test.md
* Added the release notes sample to the file and saved it
* Invoked the "Open Current File as Release Notes" command and it failed
Not seeing anything in the developer tools console nor in the various output channel logs.
| 127 |
223288
|
Settings URL - case sensitivity
|
2024-07-23 10:06:11+00:00
|
2024-07-24 14:06:14+00:00
|
Testing #223027
VSCODE-insiders://settings/files.autoSave - works as expected
vscode-insiders://seTTings/files.autoSave - does not work as expected
vscode-insiders://settings/files.autoSAVE - does not work as expected
|
completed
|
Settings URL - case sensitivity Testing #223027
VSCODE-insiders://settings/files.autoSave - works as expected
vscode-insiders://seTTings/files.autoSave - does not work as expected
vscode-insiders://settings/files.autoSAVE - does not work as expected
| 81 |
223282
|
Prompt user to reload window when changing Accessibility > Verbosity: Debug
|
2024-07-23 09:03:33+00:00
|
2024-07-24 19:54:45+00:00
|
Testing #222238
The description mentions that the window needs to be reloaded. Other settings additionally prompt the user to reload window.
(E.g., changing the update mode prompts the user for restarting VS Code.)
|
completed
|
Prompt user to reload window when changing Accessibility > Verbosity: Debug Testing #222238
The description mentions that the window needs to be reloaded. Other settings additionally prompt the user to reload window.
(E.g., changing the update mode prompts the user for restarting VS Code.)
| 76 |
223280
|
Debug Console does not mention Accessibility Help
|
2024-07-23 08:58:38+00:00
|
2024-07-23 22:58:40+00:00
|
Testing #222238
Only Accessbility View is mentioned (though wrongly called "help"?):
|
completed
|
Debug Console does not mention Accessibility Help Testing #222238
Only Accessbility View is mentioned (though wrongly called "help"?):
| 76 |
223277
|
Mention shell integration is important for suggest to work
|
2024-07-23 08:47:38+00:00
|
2024-07-24 15:03:30+00:00
|
-
|
completed
|
Mention shell integration is important for suggest to work -
| 14 |
223276
|
Potentially FATAL: Invalid `editor.language.brackets` or `editor.language.colorizedBracketPairs`
|
2024-07-23 08:41: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
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:07:54.982Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin x64 22.6.0
OS Version: macOS Ventura 13.6.6
The bug causes the Text Editor to stop functioning. It appears that all the other features still work as normal. This action is reversible.
When the bug is active, VSCode will either show an error message, or not render any text. This prevents the user from editing the `settings.json` file to fix it.
(Note that it can be fixed by either fixing, moving, or deleting the `settings.json` file.)
> [!caution]
> This bug causes the text editor to __stop functioning__.
Steps to Reproduce:
1. Enable bracket matching / colourising.
2. Set the `editor.language.brackets` or the `editor.language.colorizedBracketPairs` to an invalid value.
For example:
```jsonc
{
"editor.language.brackets": [["<", [">"]]]
}
```
or
```jsonc
{
"editor.language.colorizedBracketPairs": [
["{", "}"],
["[", "]"],
// The following is faulty
[["${"], "}"]
]
}
```
To fix the file, you need to revert it back to a previous working state (e.g. using the Timeline, or an external Text Editor).
|
Potentially FATAL: Invalid `editor.language.brackets` or `editor.language.colorizedBracketPairs` <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:07:54.982Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin x64 22.6.0
OS Version: macOS Ventura 13.6.6
The bug causes the Text Editor to stop functioning. It appears that all the other features still work as normal. This action is reversible.
When the bug is active, VSCode will either show an error message, or not render any text. This prevents the user from editing the `settings.json` file to fix it.
(Note that it can be fixed by either fixing, moving, or deleting the `settings.json` file.)
> [!caution]
> This bug causes the text editor to __stop functioning__.
Steps to Reproduce:
1. Enable bracket matching / colourising.
2. Set the `editor.language.brackets` or the `editor.language.colorizedBracketPairs` to an invalid value.
For example:
```jsonc
{
"editor.language.brackets": [["<", [">"]]]
}
```
or
```jsonc
{
"editor.language.colorizedBracketPairs": [
["{", "}"],
["[", "]"],
// The following is faulty
[["${"], "}"]
]
}
```
To fix the file, you need to revert it back to a previous working state (e.g. using the Timeline, or an external Text Editor).
| 732 |
||
223219
|
watch variables not announced if they're persistent
|
2024-07-23 03:05:05+00:00
|
2024-07-24 20:02:55+00:00
|
1. add some watch variables to the debug view
2. reload the window
3. with a screen reader enabled, hit a breakpoint that causes the variable to change
4. 🐛 the change isn't announced
|
completed
|
watch variables not announced if they're persistent 1. add some watch variables to the debug view
2. reload the window
3. with a screen reader enabled, hit a breakpoint that causes the variable to change
4. 🐛 the change isn't announced
| 56 |
223157
|
Workspace Trust doc link broken
|
2024-07-22 23:54:49+00:00
|
Type: <b>Bug</b>
Welcome - Learn the Fyndamentals
Safely browse and edit code
Workspace Trust Link
https://github.com/microsoft/vscode-docs/blob/workspaceTrust/docs/editor/workspace-trust.md
404 - page not found
VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:06:49.809Z)
OS version: Windows_NT x64 10.0.22631
Modes: Restricted
<!-- generated by issue reporter -->
|
Workspace Trust doc link broken Type: <b>Bug</b>
Welcome - Learn the Fyndamentals
Safely browse and edit code
Workspace Trust Link
https://github.com/microsoft/vscode-docs/blob/workspaceTrust/docs/editor/workspace-trust.md
404 - page not found
VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:06:49.809Z)
OS version: Windows_NT x64 10.0.22631
Modes: Restricted
<!-- generated by issue reporter -->
| 157 |
||
223134
|
In insiders vscode.dev our extension cannot load files into the workspace anymore
|
2024-07-22 21:33:10+00:00
|
2024-07-22 23:54:40+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
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: Current insiders.vscode.dev
- OS Version: Web issue only (repro)
The repro steps for this are entering via the VS Code for education route for insiders.vscode.dev
Steps to Reproduce:
1. Login to ppe.vscodeedu.com with MS credentials
2. From the courses list, select the 'Getting Started' course
3. insiders.vscode.dev should be launched with our extension and course loaded
4. At this point you can already see the errors in the dev console
5. But to see the specific issue select the "Coding Challenge" section
In this section a code editor file should have been opened up in the editor, but it is missing.
We see the following in the dev console when the course is loaded. I don't have a full bead on exactly what is happening here, but we have not been changing the extension this sprint, so it seems to be a recent new issue that is just in insiders and not in stable (which works fine still and does not have the errors).
I took a look at recent issues and this one comment appeared here that might be related? https://github.com/microsoft/vscode/issues/220171#issuecomment-2219842702
|
completed
|
In insiders vscode.dev our extension cannot load files into the workspace anymore <!-- ⚠️⚠️ 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
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: Current insiders.vscode.dev
- OS Version: Web issue only (repro)
The repro steps for this are entering via the VS Code for education route for insiders.vscode.dev
Steps to Reproduce:
1. Login to ppe.vscodeedu.com with MS credentials
2. From the courses list, select the 'Getting Started' course
3. insiders.vscode.dev should be launched with our extension and course loaded
4. At this point you can already see the errors in the dev console
5. But to see the specific issue select the "Coding Challenge" section
In this section a code editor file should have been opened up in the editor, but it is missing.
We see the following in the dev console when the course is loaded. I don't have a full bead on exactly what is happening here, but we have not been changing the extension this sprint, so it seems to be a recent new issue that is just in insiders and not in stable (which works fine still and does not have the errors).
I took a look at recent issues and this one comment appeared here that might be related? https://github.com/microsoft/vscode/issues/220171#issuecomment-2219842702
| 668 |
223062
|
Terminal suggest: Some times a lot of completions don't show up when requested
|
2024-07-22 13:41:20+00:00
|
2024-07-22 19:40:16+00:00
|
Repro:
1. Suggest on
2. Windows/pwsh
3. Type `git `
4. Press ctrl+space, 🐛 often completions don't show up but they definitely come in as seen in Pty Host trace log
|
completed
|
Terminal suggest: Some times a lot of completions don't show up when requested Repro:
1. Suggest on
2. Windows/pwsh
3. Type `git `
4. Press ctrl+space, 🐛 often completions don't show up but they definitely come in as seen in Pty Host trace log
| 124 |
223025
|
CommentController.activeCommentThread seems to be the raw object instead of a proxy
|
2024-07-22 09:57:03+00:00
|
CommentController.activeCommentThread looks like:
I expected:
|
CommentController.activeCommentThread seems to be the raw object instead of a proxy CommentController.activeCommentThread looks like:
I expected:
| 123 |
||
223021
|
CommentController.activeCommentThread not updated when navigating from ruler or Comments panel
|
2024-07-22 09:54:59+00:00
|
2024-07-25 11:16:59+00:00
|
CommentThread.reveal() and clicking into the comment triggers an update of CommentController.activeCommentThread, but it doesn't update when I expand a comment from the left editor ruler or the Comments panel.
|
completed
|
CommentController.activeCommentThread not updated when navigating from ruler or Comments panel CommentThread.reveal() and clicking into the comment triggers an update of CommentController.activeCommentThread, but it doesn't update when I expand a comment from the left editor ruler or the Comments panel.
| 73 |
222554
|
Terminal suggest: git.exe should appear as the top suggestion for string "git"
|
2024-07-21 18:58:26+00:00
|
2024-07-21 19:22:41+00:00
|
Needs Windows/pwsh/suggest on. Make sure the other git executables show up below.
|
completed
|
Terminal suggest: git.exe should appear as the top suggestion for string "git" Needs Windows/pwsh/suggest on. Make sure the other git executables show up below.
| 90 |
222475
|
powershell auto complete opens when terminating a program with ctrl+c
|
2024-07-21 16:48:47+00:00
|
2024-07-22 19:16:15+00:00
|
<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version:
- OS Version:
Steps to Reproduce:
1. Run a program which launches in the terminal and waits for input
2. press ctrl+c to escape the program
:bug: auto complete opens
|
completed
|
powershell auto complete opens when terminating a program with ctrl+c <!-- ⚠️⚠️ 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. Run a program which launches in the terminal and waits for input
2. press ctrl+c to escape the program
:bug: auto complete opens
| 415 |
222233
|
Terminal suggest: Don't rewrite whole line when it's not needed
|
2024-07-19 19:40:36+00:00
|
2024-07-19 22:01:24+00:00
|
1. Most noticeable on mac
2. In vscode repo
3. Type ./script
4. Enter, 🐛 `./script` is deleted first, then `./scripts/` is typed
|
completed
|
Terminal suggest: Don't rewrite whole line when it's not needed 1. Most noticeable on mac
2. In vscode repo
3. Type ./script
4. Enter, 🐛 `./script` is deleted first, then `./scripts/` is typed
| 115 |
222230
|
Terminal suggest: Completions for folders should add the trailing `\`
|
2024-07-19 19:02:09+00:00
|
2024-07-19 20:07:03+00:00
|
`./sc<tab>` in Windows/pwsh
Windows Terminal:
VS Code via suggest:
It should have the trialing `\` like the way tab completion does
|
completed
|
Terminal suggest: Completions for folders should add the trailing `\` `./sc<tab>` in Windows/pwsh
Windows Terminal:
VS Code via suggest:
It should have the trialing `\` like the way tab completion does
| 141 |
222228
|
Terminal suggest: Results should prefer shorter completions
|
2024-07-19 18:25:50+00:00
|
2024-07-19 20:07:03+00:00
|
This is a case that conflicts a lot with my muscle memory:
When suggest is off, `./sc<tab>c<tab>` completes to `./scripts/code` as `code` is a common prefix for all completions that start with `c`.
|
completed
|
Terminal suggest: Results should prefer shorter completions This is a case that conflicts a lot with my muscle memory:
When suggest is off, `./sc<tab>c<tab>` completes to `./scripts/code` as `code` is a common prefix for all completions that start with `c`.
| 116 |
222227
|
Terminal suggest: ./ should show results for .\ on Windows
|
2024-07-19 18:22:38+00:00
|
2024-07-25 13:56:59+00:00
|
Hides on `/`:
Works for `\`:
|
completed
|
Terminal suggest: ./ should show results for .\ on Windows 
Hides on `/`:
Works for `\`:
| 153 |
222199
|
Extension page doesn't open in application when attempting to install from the browser
|
2024-07-19 15:45:46+00:00
|
<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.91.1
- OS Version: MacOS 14.5 (23F79)
Steps to Reproduce:
1. Close all VS Code windows but don't exit the application.
2. Go to an extension page in the VS Code Marketplace in your browser.
3. Click install on the extension page and allow your browser to open VS Code when prompted.
4. VS Code will open but it will show the welcome page rather than the extension page for the extension you're trying to install.
This does not occur if I keep a VS Code application window open or if I exit the application entirely before clicking install from the browser.
|
Extension page doesn't open in application when attempting to install from the browser <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.91.1
- OS Version: MacOS 14.5 (23F79)
Steps to Reproduce:
1. Close all VS Code windows but don't exit the application.
2. Go to an extension page in the VS Code Marketplace in your browser.
3. Click install on the extension page and allow your browser to open VS Code when prompted.
4. VS Code will open but it will show the welcome page rather than the extension page for the extension you're trying to install.
This does not occur if I keep a VS Code application window open or if I exit the application entirely before clicking install from the browser.
| 441 |
||
222191
|
Terminal suggest: Problems when typing quickly when completions are requested
|
2024-07-19 14:21:43+00:00
|
Repro:
1. mac/pwsh
2. suggest enabled
3. type `git co -b tyriar` quickly
|
Terminal suggest: Problems when typing quickly when completions are requested Repro:
1. mac/pwsh
2. suggest enabled
3. type `git co -b tyriar` quickly
| 91 |
||
222187
|
Terminal suggest: Only files/dirs starting with . show when typing ./
|
2024-07-19 14:05:24+00:00
|
2024-07-25 15:45:33+00:00
|
Repro:
1. mac or linux/pwsh
2. suggest enabled
3. Type `./s`, 🐛 should show `./scripts` as an option
<img width="760" alt="Screenshot 2024-07-19 at 7 03 49 AM" src="https://github.com/user-attachments/assets/68f8950c-cfff-47a5-938a-f9eacb4332a3">
|
completed
|
Terminal suggest: Only files/dirs starting with . show when typing ./ Repro:
1. mac or linux/pwsh
2. suggest enabled
3. Type `./s`, 🐛 should show `./scripts` as an option
<img width="760" alt="Screenshot 2024-07-19 at 7 03 49 AM" src="https://github.com/user-attachments/assets/68f8950c-cfff-47a5-938a-f9eacb4332a3">
| 125 |
222184
|
Terminal suggest: Completions may show after running a command
|
2024-07-19 13:54:18+00:00
|
2024-07-19 14:21:10+00:00
|
Repro:
1. macOS/pwsh
2. Run a command
|
completed
|
Terminal suggest: Completions may show after running a command Repro:
1. macOS/pwsh
2. Run a command
| 85 |
222170
|
Deprecated settings do not show in settings UI even when configured by the user
|
2024-07-19 11:06:43+00:00
|
<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
VS Code Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:08:12.169Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.5.0-41-generic
Steps to Reproduce:
1. Deprecate an existing setting using either `deprecateMessage` or `markdownDeprecationMessage`.
2. Modify the setting either in the workspace or user settings JSON files.
3. Open the settings UI.
4. Expect to see the setting, but it's not there.
The [docs](https://github.com/microsoft/vscode-docs/blob/d7fa4a3ee512344e347d6ebd2ba881ce770617d8/api/references/contribution-points.md?plain=1#L331) say that the setting to be visible in the settings UI when modified by the user (emphasis mine):
> If you set `deprecationMessage`, or `markdownDeprecationMessage`, the setting will get a warning underline with your specified message. Also, the setting will be hidden from the settings UI **_unless it is configured by the user_**.
|
Deprecated settings do not show in settings UI even when configured by the user <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
VS Code Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:08:12.169Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.5.0-41-generic
Steps to Reproduce:
1. Deprecate an existing setting using either `deprecateMessage` or `markdownDeprecationMessage`.
2. Modify the setting either in the workspace or user settings JSON files.
3. Open the settings UI.
4. Expect to see the setting, but it's not there.
The [docs](https://github.com/microsoft/vscode-docs/blob/d7fa4a3ee512344e347d6ebd2ba881ce770617d8/api/references/contribution-points.md?plain=1#L331) say that the setting to be visible in the settings UI when modified by the user (emphasis mine):
> If you set `deprecationMessage`, or `markdownDeprecationMessage`, the setting will get a warning underline with your specified message. Also, the setting will be hidden from the settings UI **_unless it is configured by the user_**.
| 658 |
||
222165
|
Integrated terminal results in vscode freezing when increasing scrollback to 10000 lines
|
2024-07-19 10:11:08+00:00
|
2024-07-21 16:29:47+00:00
|
- VS Code Version: 1.91.1
- OS Version: Darwin arm64 23.5.0
When I set the scrollback to 10000 lines the whole IDE becomes laggy or freezes whenever I resize the terminal or whenever I run `clear` command in the terminal. It seems to me that modern hw should handle 10000 lines just fine and for example the default Mac OS terminal has no issue with that. I need the larger scrollback since I get a lot of logs when debugging.
|
completed
|
Integrated terminal results in vscode freezing when increasing scrollback to 10000 lines - VS Code Version: 1.91.1
- OS Version: Darwin arm64 23.5.0
When I set the scrollback to 10000 lines the whole IDE becomes laggy or freezes whenever I resize the terminal or whenever I run `clear` command in the terminal. It seems to me that modern hw should handle 10000 lines just fine and for example the default Mac OS terminal has no issue with that. I need the larger scrollback since I get a lot of logs when debugging.
| 119 |
222134
|
Incorrect sticky scroll line, only occurs when file is first opened
|
2024-07-19 00:55:06+00:00
|
<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
Version: 1.91.1 (user setup)
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:06:49.809Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22631
I'm seeing a mysterious incorrect sticky scroll line which only occurs the first time I open a file. Seems like a bug, since it should be consistent. I originally repro'ed this with the C/C++ extension, having changed the sticky scroll mode to `foldingProviderModel`, and confirmed that only a single range was being generated by the provider. Indenting the line causes it no longer be a sticky line, then removing the indentation causes it to be picked up again. It seems like when the file is initially opened, both indent-level and folding-provider stick scroll modes are being applied.
https://github.com/user-attachments/assets/2db2d554-5e51-40c6-b3e7-56a273059adb
|
Incorrect sticky scroll line, only occurs when file is first opened <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
Version: 1.91.1 (user setup)
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:06:49.809Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22631
I'm seeing a mysterious incorrect sticky scroll line which only occurs the first time I open a file. Seems like a bug, since it should be consistent. I originally repro'ed this with the C/C++ extension, having changed the sticky scroll mode to `foldingProviderModel`, and confirmed that only a single range was being generated by the provider. Indenting the line causes it no longer be a sticky line, then removing the indentation causes it to be picked up again. It seems like when the file is initially opened, both indent-level and folding-provider stick scroll modes are being applied.
https://github.com/user-attachments/assets/2db2d554-5e51-40c6-b3e7-56a273059adb
| 602 |
||
222089
|
Terminal suggest: Accepting a completion can open the suggest widget again
|
2024-07-18 12:56:23+00:00
|
2024-07-18 20:27:46+00:00
|
|
completed
|
Terminal suggest: Accepting a completion can open the suggest widget again
| 67 |
222076
|
Terminal suggest can sometimes appear when navigating history
|
2024-07-18 11:54:13+00:00
|
2024-07-18 13:20:08+00:00
|
Repro:
1. Enable terminal suggest
2. Open pwsh
4. run `git add .`
5. press up
|
completed
|
Terminal suggest can sometimes appear when navigating history Repro:
1. Enable terminal suggest
2. Open pwsh
4. run `git add .`
5. press up
| 91 |
222075
|
Terminal sticky scroll can show up for 1 frame when using page down in a pager
|
2024-07-18 11:47:59+00:00
|
Repro:
1. On Windows
2. Enable sticky scroll
3. Open pwsh
4. Run `git diff` with more than a page of changes
5. Page up+down, 🐛 sticky scroll will show up for 1 frame every time page down is used
It rarely shows up in the gif due to low recording framerate
|
Terminal sticky scroll can show up for 1 frame when using page down in a pager Repro:
1. On Windows
2. Enable sticky scroll
3. Open pwsh
4. Run `git diff` with more than a page of changes
5. Page up+down, 🐛 sticky scroll will show up for 1 frame every time page down is used
It rarely shows up in the gif due to low recording framerate
| 140 |
||
222071
|
Unexpected showing docker related extension recommendation
|
2024-07-18 11:28:06+00:00
|
<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.91.1 (Universal)
- OS Version: Darwin arm64 23.5.0
Steps to Reproduce:
1. Install OrbStack
2. Uninstall OrbStack
3. The commands `docker` and `kubectl` should be remove since I run `which *` and neither of them show its path.
4. Open VSCode, it kept recommending `Docker`, `Dev Containers` and `Kubernetes`, when I hover on them, they show ` This extension is recommended because you have Kubernetes installed.` But I didn't.
I simply want's to know in which way VSCode decide there's a Kubernetes installed on my Mac? So I can completely removed it.
<img width="979" alt="image" src="https://github.com/user-attachments/assets/8bba6a9d-0d3e-4a91-a743-5ef815c81c36">
<img width="660" alt="image" src="https://github.com/user-attachments/assets/2530e7cc-16e4-4754-b5ab-36ea339201a4">
|
Unexpected showing docker related extension recommendation <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.91.1 (Universal)
- OS Version: Darwin arm64 23.5.0
Steps to Reproduce:
1. Install OrbStack
2. Uninstall OrbStack
3. The commands `docker` and `kubectl` should be remove since I run `which *` and neither of them show its path.
4. Open VSCode, it kept recommending `Docker`, `Dev Containers` and `Kubernetes`, when I hover on them, they show ` This extension is recommended because you have Kubernetes installed.` But I didn't.
I simply want's to know in which way VSCode decide there's a Kubernetes installed on my Mac? So I can completely removed it.
<img width="979" alt="image" src="https://github.com/user-attachments/assets/8bba6a9d-0d3e-4a91-a743-5ef815c81c36">
<img width="660" alt="image" src="https://github.com/user-attachments/assets/2530e7cc-16e4-4754-b5ab-36ea339201a4">
| 575 |
||
222050
|
TerminalShellExecutionEndEvent - `execution.cwd` is not set
|
2024-07-18 09:36:46+00:00
|
2024-07-18 12:12:24+00:00
|
```ts
const { execution, exitCode } = e;
const [executable, subcommand] = execution.commandLine.value.split(/\s+/);
console.log(e.execution.cwd);
console.log(e.shellIntegration.cwd);
```
|
completed
|
TerminalShellExecutionEndEvent - `execution.cwd` is not set ```ts
const { execution, exitCode } = e;
const [executable, subcommand] = execution.commandLine.value.split(/\s+/);
console.log(e.execution.cwd);
console.log(e.shellIntegration.cwd);
```
| 97 |
221964
|
Extension walkthroughs do not launch upon install
|
2024-07-17 17:20:39+00:00
|
2024-07-25 21:36: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/**No**, this is an extension-related issue that arises across extensions with walkthroughs
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.91.1
- OS Version: Windows 11
Extension walkthroughs are not launching upon install. Expected behavior: walkthrough launches automatically upon install.
Tested on C# Dev Kit extension and Python extension. Seemed to work in 1.90.0 but does not work in 1.91.1.
Steps to Reproduce [Windows Sandbox]:
1. Launch a Windows Sandbox
2. Open Edge and download VS Code (stable) from the VS Code website
3. Install the C# Dev Kit extension.
*Note:* Upon install the walkthrough is supposed to launch automatically. This is not happening, but I can manually open the walkthrough using these steps.
4. Open command palette.
5. Use command 'Welcome: Open Walkthrough'
6. Select 'Get Started with C# Dev Kit'
7. Repeated steps 3-7 with the Python extension. Same behavior.
Steps to Reproduce [VS Code stable and VS Code insider]:
1. Open VS Code
2. Uninstall C# Dev Kit (if you have it installed)
3. Reload VS Code
4. Install C# Dev Kit extension.
5. *Note:* Upon install the walkthrough is supposed to launch automatically. This is not happening, but I can manually open the walkthrough using these steps.
4. Open command palette.
5. Use command 'Welcome: Open Walkthrough'
6. Select 'Get Started with C# Dev Kit'
7. Repeated steps 2-7 with the Python extension. Same behavior.
|
completed
|
Extension walkthroughs do not launch upon install <!-- ⚠️⚠️ 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**, this is an extension-related issue that arises across extensions with walkthroughs
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.91.1
- OS Version: Windows 11
Extension walkthroughs are not launching upon install. Expected behavior: walkthrough launches automatically upon install.
Tested on C# Dev Kit extension and Python extension. Seemed to work in 1.90.0 but does not work in 1.91.1.
Steps to Reproduce [Windows Sandbox]:
1. Launch a Windows Sandbox
2. Open Edge and download VS Code (stable) from the VS Code website
3. Install the C# Dev Kit extension.
*Note:* Upon install the walkthrough is supposed to launch automatically. This is not happening, but I can manually open the walkthrough using these steps.
4. Open command palette.
5. Use command 'Welcome: Open Walkthrough'
6. Select 'Get Started with C# Dev Kit'
7. Repeated steps 3-7 with the Python extension. Same behavior.
Steps to Reproduce [VS Code stable and VS Code insider]:
1. Open VS Code
2. Uninstall C# Dev Kit (if you have it installed)
3. Reload VS Code
4. Install C# Dev Kit extension.
5. *Note:* Upon install the walkthrough is supposed to launch automatically. This is not happening, but I can manually open the walkthrough using these steps.
4. Open command palette.
5. Use command 'Welcome: Open Walkthrough'
6. Select 'Get Started with C# Dev Kit'
7. Repeated steps 2-7 with the Python extension. Same behavior.
| 684 |
221953
|
Terminal suggestions are highlighting for the completion text, not the label
|
2024-07-17 15:19:07+00:00
|
2024-07-18 11:32:58+00:00
|
Repro:
1. Open pwsh
2. Create a `test` folder
3. Type `yarn t`
This is happening because the actual completion that will happen is `.\test` where the highlights would make more sense.
|
completed
|
Terminal suggestions are highlighting for the completion text, not the label Repro:
1. Open pwsh
2. Create a `test` folder
3. Type `yarn t`
This is happening because the actual completion that will happen is `.\test` where the highlights would make more sense.
| 106 |
221883
|
connection to serve-web hanging indefinitely
|
2024-07-17 04:56:31+00:00
|
2024-07-18 14: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:
Version: 1.92.0-insider
Commit: 06f8ef165cc37104bc78b7f36209d95333474348
Date: 2024-07-16T05:03:41.928Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
- OS Version: Linux x64 4.18.0-513.18.1.el8_9.x86_64
Steps to Reproduce:
1. start serve-web (via systemctl user service, if that matters). exact start command: `code-insiders serve-web --host 127.0.0.1 --port 59005 --without-connection-token`
2. try to connect via google chrome (locally or via ssh connection with port forwarded appropriately)
The feature is working fine with the latest non-insider release, v1.91.1, both locally (via localhost) and port forwarded ssh connection.
code-insiders launches fine locally, only when trying to use serve-web on insider v1.92 do i run into the issue.
The symptom: when I try to connect via chrome (eg localhost:59005 on the host machine), it tries to load and never completes. if i stop serve-web on the host, trying to connect via the browser immediately fails (expected. I just say this to confirm the host & port are correct).
One other thing to note: the service log/status (`systemctl --user status code-insiders`) shows no errors, and prints the URL to connect to as I'd expect).
|
completed
|
connection to serve-web hanging indefinitely <!-- ⚠️⚠️ 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.92.0-insider
Commit: 06f8ef165cc37104bc78b7f36209d95333474348
Date: 2024-07-16T05:03:41.928Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
- OS Version: Linux x64 4.18.0-513.18.1.el8_9.x86_64
Steps to Reproduce:
1. start serve-web (via systemctl user service, if that matters). exact start command: `code-insiders serve-web --host 127.0.0.1 --port 59005 --without-connection-token`
2. try to connect via google chrome (locally or via ssh connection with port forwarded appropriately)
The feature is working fine with the latest non-insider release, v1.91.1, both locally (via localhost) and port forwarded ssh connection.
code-insiders launches fine locally, only when trying to use serve-web on insider v1.92 do i run into the issue.
The symptom: when I try to connect via chrome (eg localhost:59005 on the host machine), it tries to load and never completes. if i stop serve-web on the host, trying to connect via the browser immediately fails (expected. I just say this to confirm the host & port are correct).
One other thing to note: the service log/status (`systemctl --user status code-insiders`) shows no errors, and prints the URL to connect to as I'd expect).
| 686 |
221852
|
The button to expand and collabs the replace portion of the find all dialog box is unlabeled
|
2024-07-16 19:19:56+00:00
|
Steps to reproduce:
1. in any document, press controll+shift+f to open the find all functionality.
1. press tab (4 times) until you hear "button" or "button expanded".
Issues:
1. JAWS does not announce that the button is an expandable one, and that it is in the collapsed state. This appears to be a regression in the insiders build when compared with the latest stable release, where the button is announced as collapsed or expanded.
2. JAWS does not have any label for the button. It is just announced as "button".
|
The button to expand and collabs the replace portion of the find all dialog box is unlabeled Steps to reproduce:
1. in any document, press controll+shift+f to open the find all functionality.
1. press tab (4 times) until you hear "button" or "button expanded".
Issues:
1. JAWS does not announce that the button is an expandable one, and that it is in the collapsed state. This appears to be a regression in the insiders build when compared with the latest stable release, where the button is announced as collapsed or expanded.
2. JAWS does not have any label for the button. It is just announced as "button".
| 153 |
||
221826
|
When replacing text in a large enough file, the old selection is incorrectly preserved
|
2024-07-16 15:32:13+00:00
|
Repro:
1. Open https://github.com/microsoft/vscode/blob/739f145f893d090d0a6f48ac457cd27cdf674c89/src/vs/workbench/contrib/terminalContrib/suggest/test/browser/recordings/windows11_pwsh_input_ls_complete_ls.ts
2. Select `\"ResultType\":`
3. Ctrl+h
4. Replace all, 🐛 the old selection is retained but it's not valid anymore as the original text was removed
|
When replacing text in a large enough file, the old selection is incorrectly preserved Repro:
1. Open https://github.com/microsoft/vscode/blob/739f145f893d090d0a6f48ac457cd27cdf674c89/src/vs/workbench/contrib/terminalContrib/suggest/test/browser/recordings/windows11_pwsh_input_ls_complete_ls.ts
2. Select `\"ResultType\":`
3. Ctrl+h
4. Replace all, 🐛 the old selection is retained but it's not valid anymore as the original text was removed
| 213 |
||
221820
|
Issue Reporter: Repository link issues
|
2024-07-16 15:11:31+00:00
|
- When I open the issue reporter using inline chat (`Report Issue`) and press on the repository link at the bottom of the page, the repository website opens 3 times. It seems that the event listener is being added to the `issueRepoName` DOM element multiple times as it is registered inside an update method.
- When I open the issue reporter using the menu at the top and select an extension, the link to the repository is not created
|
Issue Reporter: Repository link issues - When I open the issue reporter using inline chat (`Report Issue`) and press on the repository link at the bottom of the page, the repository website opens 3 times. It seems that the event listener is being added to the `issueRepoName` DOM element multiple times as it is registered inside an update method.
- When I open the issue reporter using the menu at the top and select an extension, the link to the repository is not created
| 111 |
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 136