jiebi/CodeConvo huggingface dataset:
Change:
this._accessibleView = this._register(this._instantiationService.createInstance(AccessibleView)); } this._accessibleView.show(provider); } next(): void { this._accessibleView?.next();

Discussion:
Testing Press alt+F2, VoiceOver starts reading the response Press alt+], the view shows the next response but VoiceOver is still reading that response and it never reads the next response Maybe related, but sometimes, it also doesn't read the response when I press alt+F2. It will say "you are now on a text area" and just sit there. Then, it only wants to read the text a single character at a time when I move the cursor.
Actually, I believe this might be working as expected - I have to move the cursor for the screen reader to move on to the next content. and could you pls let us know if this is a bug or working as expected?
Unfortunately, this is a voiceover issue, but I believe last time we something like this it was resolved my slightly increasing the wait time for certain focus event. I don't remember the full context and cannot find the issue right now. does it sound familiar? It was related to the opening and closing of the contextual help I believe.
Great recall the issue you are talking about is
Correct. I believe it could be the same underlying cause. By the way, having to move the cursor to read content is totally fine as you described. the real issue is that Voiceover is not announcing the change of context.
Makes sense - because without that announcement, you wouldn't know to move your cursor
I wonder if we have a way to calculate the total number of responses. if we do, we could issue an alert announcing position information when we move back and forth. This would resolve the lack of context for macOs and improve the experience in the other platforms. Thoughts?
Yes that makes sense to me - I linked an issue where this is a request for the notification a11y view and we could also support this for the responses
It might have to be an August thing - I'll investigate.
this is also an issue for notifications
I think we have to go with what you suggested i tried a bunch of hacks and setTimeouts and it didn't work
I think it could make the feature more helpful for all platforms. Moving between suggestions is right now a bit confusing because I can't tell for sure if the one on focus is the last one, or if it truly moved to a different one after pressing the command.

In the copilot chat panel, for example, I find much more practical and easier to simply move to the list of responses and go on from there. In addition, hacking assistive technology rarely justifies the effort, and often leads to undesirable outcomes that are not easy to anticipate.
it seems focus still gets trapped initially - even alert isn't taking precedent. i'm hoping it's just what I'm experiencing. about to make a PR with a change that does this for notifications and chat responses
What do you mean it gets trapped? Do you want me to review something. I have half an hour until next meeting.
yes, the linked PR please sorry I have been doing a lot atm
Verified by with the follow up item of to be addressed in August
Change:
private addFallbackHandlers(): void { // File Menu Items <del> this.fallbackMenuHandlers['workbench.action.files.newUntitledFile'] = (menuItem, win, event) => this.windowsMainService.openEmptyWindow({ context: OpenContext.MENU, contextWindowId: win.id }); this.fallbackMenuHandlers['workbench.action.newWindow'] = (menuItem, win, event) => this.windowsMainService.openEmptyWindow({ context: OpenContext.MENU, contextWindowId: win.id }); </del> <ins> this.fallbackMenuHandlers['workbench.action.files.newUntitledFile'] = (menuItem, win, event) => this.windowsMainService.openEmptyWindow({ context: OpenContext.MENU, contextWindowId: win?.id }); this.fallbackMenuHandlers['workbench.action.newWindow'] = (menuItem, win, event) => this.windowsMainService.openEmptyWindow({ context: OpenContext.MENU, contextWindowId: win?.id }); </ins> this.fallbackMenuHandlers['workbench.action.files.openFileFolder'] = (menuItem, win, event) => this.electronMainService.pickFileFolderAndOpen(undefined, { forceNewWindow: this.isOptionClick(event), telemetryExtraData: { from: telemetryFrom } }); this.fallbackMenuHandlers['workbench.action.openWorkspace'] = (menuItem, win, event) => this.electronMainService.pickWorkspaceAndOpen(undefined, { forceNewWindow: this.isOptionClick(event), telemetryExtraData: { from: telemetryFrom } });

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --Versions VSCode Version: 1.46.0 OS Version: macOS 10.15.5 (Darwin x64 19.5.0) Overview In v1.46, the new file & new window menu items do not do anything when all windows are closed. The behaviour is the same with the keyboard shortcuts (Cmd+N, Cmd+Shift+N). The bug is not present in v1.45.1. The bug is present in the insiders build. Steps to Reproduce Visual Studio Code all windows the File menu, choose either "New File" or "New Window" Expected Result new file or window is opened Actual Result happens <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Duplicate of but this one has a better title and clearer description, and reports the problem occurring from menu options as well as keybindings. I was not able to reproduce it on Windows, so it seems to be macOS-specific.
Yep it's the same issue. I'm afraid I didn't find that one while searching for duplicates.
I haven't found out the cause yet, but I can repro.
Looks like it was introduced by this change. win is undefined when no window is open
Is this still unresolved? I can't seem to reproduce this issue.
thanks for the fix, yes this was a regression I introduced. I filed because the TypeScript types are not catching this issue.
Change:
"elliptic": "^6.5.3", "nwmatcher": "^1.4.4" } <del> } </del>  No newline at end of file <ins> } </ins>

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.73.1 OS Version: Ubuntu 22.04 Steps to Reproduce: multiple terminals to last created, write something to any other than the last one the beginning of a command and press tab for autocompletion After a while, the characters reappear if you run any command again. I found this issue , but according to the description it is not entirely clear which input the author means Here is what I was able to reproduce (In each terminal I enter the same command and press ): ! !
I cannot repro on mac, maybe something has been fixed?
also can't repro on WSL
I believe this is already fixed, can you see if you can reproduce in the ? /label info-needed
Hi I don't know if the problem occurs on MacOS I tried to reproduce this error in the Insider build (Visual Studio Code CLI 1.74.0) and got the same result. !
I also recorded a video of how I reproduced the bug, I hope this helps https://user-
issue I saw your problem and it seems that there is something different from mine. The problem with me was that if I first run the vscode after booting and type in my native language, Korean, some letters disappeared from the input. There is no problem when typing in English. For example, if I type '' in a markdown or any file, some of the inputs disappear and become ''. It disappears even though I typed ", " Isn't your problem that the terminal input disappears?
Is this issue the same as the issue I opened?

Hi I think not, my problem is reproduced only in the terminal, there are no problems in the files.
Hi I wonder if the cause of your problem and the cause of my problem are the same. What's your idea?
Can't say with certainty
Different issues, thanks for the additional info
Happened to me just now: ! webgl renderer Version: 1.74.0-insider (user setup) Commit: Date: 2022-11-18T05:25:18.342Z Electron: 19.1.3 Chromium: 102.0.5005.167 16.14.2 V8: 10.2.154.15-electron.0 OS: Windows_NT x64 10.0. Sandboxed: Yes
Created a PR fixing it
I saw sometimes, though I never found a reproduction for it. However I have not seen it this week, thus marking verified.
Change:
"elliptic": "^6.5.3", "nwmatcher": "^1.4.4" } <del> } </del>  No newline at end of file <ins> } </ins>

Discussion:
Use insiders-1.78 or run out of source start a terminal the name is "kernel_task" start a long running task, like , press and see it's not terminating https://user-
same question <img width="1024" alt="image" src="https://user-"
Same issue on my brand new Apple M2 Mac Mini. Running latest Insiders. I thought I was going crazy.
Works fine on latest version of insiders.
Yeah fixed now. Thanks everybody!
Not working for me. I am using
Not working for me after updating today (May 09, 2023) Version: 1.78.0 (Universal) Commit: Date: 2023-05-03T20:11:00.813Z Electron: 22.4.8 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Darwin x64 18.7.0 Sandboxed: Yes
That doesn't kill the process. It just suspends it. Just be aware of that (if you do it a lot ;)
same for me, no control-c or any kill commands will work: Version: 1.78.1 Commit: Date: 2023-05-04T09:57:42.343Z (5 days ago) Electron: 22.5.1 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Darwin x64 18.7.0 Sandboxed: No
It stopped working for me due to an extension which had created a key binding starting with so I removed the key binding and it started working. helped me.
what extension was causing the issue?
I forgot the name but you can check your keyboard bindings.
I don't have the same extensions as you?
Hi, this "Ctrl+C" (terminate task) feature suddenly stopped working a few days ago for us as well: the "^C" still displays in the terminal but without any effect and there is not a single shortcut associated to Ctrl+C and no way to add one This is a huge pain as we simply cannot work anymore using vs-code, this was such a central feature There is just so much content on the topic online, yet no simple solution: What happened?

Why did vs-code team do this? How is there not a simple option in Keyboard Shortcuts (JSON) to add it back? Thanks in advance to those currently working on a solution
what is shown in the vscode status bar when you press ?
it was a bug we introduced and fixed shortly afterwards, see One of the downsides of using Insiders is occasionally things like this slip in.
Never knew I was on those buggy Insiders builds. Hot damn. You need better wording on your main site. In any case, there is still no fix for this for Insiders and I am not really looking forward to installing and setting everything up from scratch with Universal.
Change:
const disposable = combinedDisposable(changeDisposable, removeDisposable); this.repositoryDisposables.add(disposable); <ins> this.tryFocusRepositoryBasedOnActiveEditor(Iterable.single(repository)); </ins> } private onDidRemoveRepository(repository: ISCMRepository): void {

Discussion:
Issue Type: <bBug</bI'm working with a multi-root workspace where each project has its own git repository. On startup VSCode restores my last session with all the open files and the tree-view updates correctly, selecting the file which has the focus in the editor. But the SCM status bar does not switch to the right repository, but shows the status of the repository from the first folder in the workspace. Steps to reproduce (or see the attached screencast): VSCode with a (multi-root)-workspace with two projects (projecta, projectb) the focus of files correcly selects the corresponding repository VSCode while the focus is on a file from the second project (projectb) VSCode restores the last session (open editor tabs, tree-view, etc.) correctly SCM status bar stays with the repository projecta, although the file in focus belongs to projectb Expected behaviour: I would expect that when restoring a session, the correct repository to the file that is in focus in the editor would be selected automatically. The problem here is only occurs when restoring the session. As soon as I actively change the focus in the editor, the associated repositories are correctly selected. https://user- VS Code version: Code 1.62.2 (, 2021-11-11T20:51:30.084Z) OS version: Linux x64 5.4.0-54-generic Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (9)</summaryExtensionVersion ------ gitlens11.6.1 vscode-docker1.18.0 python2021.11. vscode-pylance2021.11.1 remote-containers0.205.2 remote-ssh0.66.1 remote-ssh-edit0.66.1 hexeditor1.8.2 material-theme3.13.2 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
I think this is just a refresh issue with the SCM status bar. When I open VSCode, the status bar assumes that I am working on the first repository in my workspace. However, all open editors only refer to files from another repository (the file tree is also expanded correctly).

Sometimes for example, the status bar shows a branch that I already deleted a few days ago, but since it assumes the wrong repository, it suggests publishing the "new" branch.
Any updates on this? I'm facing the same issue on Mac and find it quite annoying.
sorry for not getting back to you on this until now. I do have a repro for this, and I have couple of ideas on how to address this problem, though there is some complexity around the way repositories are discovered. I will try to have a fix for this later this week or next week.
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
Change:
this._openerService.open(link.text, { allowTunneling: this._isRemote, allowContributedOpeners: true, <ins> openExternal: true </ins> }); } }

Discussion:
Type: <bBug</bContext I want to use vscode-URLs to directly drop into a debugging session. My script can be found at Expected behavior When cmd-clicking this link from inside VSCode, I would expect to be dropped into the debugging session <img width="1287" alt="Screenshot 2022-08-22 at 10 25 59" src="https://user-"Actual behavior Instead, the link gets opened in VS Code's search bar <img width="904" alt="Screenshot 2022-08-22 at 10 27 17" src="https://user-"Additional information I am sure the link itself is fine, because when I copy it from the console and paste it into Chrome's address bar, then VSCode opens my debugging session as expected. Also see VS Code version: Code 1.70.2 (, 2022-08-16T05:36:37.829Z) OS version: Darwin x64 21.6.0 Modes: Remote OS version: Linux x64 5.15.0-30-generic Remote OS version: Linux x64 5.15.0-30-generic <details<summarySystem Info</summary </details<details<summaryExtensions (7)</summaryExtensionVersion ------ better-cpp-syntax1.15.19 jupyter-keymap1.0.0 remote-ssh0.84.0 remote-ssh-edit0.80.0 llvm0.1.1 vscode-clangd0.1.21 vscode-lldb1.7.4 </details<!-- generated by issue reporter --
since the url would need to open a JS/browser debug session, would the JavaScript Debugger Companion Extension be of help here?
This is debugging with lldb, so it's not in the domain of js-debug
This is a request to essentially hook up the terminal link detector to whatever handles external custom protocol links. We may be able to just add vscode:// and vscode-insiders:// to the uri detection? This may need changes in the editor's link detector
Change:
"@microsoft/applicationinsights-web": "^2.6.4", "@parcel/watcher": "2.0.2", "@vscode/sqlite3": "4.0.12", <ins> "@vscode/sudo-prompt": "^9.3.0", </ins> "@vscode/vscode-languagedetection": "1.0.21", "applicationinsights": "1.0.8", "graceful-fs": "4.2.8",

Discussion:
To recreate: Edit a file requiring sudo (eg ) When saving, VSCode will request sudo permissions and, after granting, gives the following error: I do NOT have Rosetta installed but understand VS Code is supposed to be M1 compatible. Here is the version info:
I cannot reproduce and I am on a M1 as well. thoughts? did you install the universal app?
For triggering we use a 3rd-party module which on macOS uses osascript saved as application bundle As a quick check, trigger a sudo prompt from vscode and open the OS temp directory and check for , following is the executable architecture So unless the user has rosetta installed this application will not be launched on M1 as reported here. you might have rosetta installed hence the failure was not seen, can be confirmed with
Not sure if that applet can be converted to universal, might also be worth looking at alternatives for sudo-prompt given that repo is now archived.
I would suggest to fork the module and convert that applet to universal if that is straightforward.
I don't see the source for the applet under the user repositories, will have to reach out to the author.
Maybe:
would you be able to test this scenario again from the following build that includes a potential fix:
Thanks for all your efforts on this (and . I discovered this on a new M1 Mac where I had not yet installed Rosetta but eventually caved in and installed it. Unfortunately it doesn't appear Rosetta can be easily uninstalled for testing. Happy to give this another go the next time I have a fresh Mac install but don't foresee that in the immediate future...
Verification on a mac with ARM chip without Rosetta 2 installed ([1]) use open try to edit (in the comment area!!!) from the error retry as sudo verify you get a prompt and save works [1] The presence of these files are a good indicator that you have Rosetta2 installed:
I take it you just re-compiled the applet for universal & updated the package with the base64 encoded string (is that right?)
yes! Here is what I did: decode the base64 encoded value unzip it open the apple script in apple script editor export it as application bundle (I have Rosetta 2 installed so it seems to export as universal bundle by default) zip it base64 encode it release as fork from
Change:
import { IEditorService } from 'vs/workbench/services/editor/common/editorService'; import { LifecyclePhase } from 'vs/workbench/services/lifecycle/common/lifecycle'; import { IStatusbarEntry, IStatusbarEntryAccessor, IStatusbarService, StatusbarAlignment } from 'vs/workbench/services/statusbar/browser/statusbar'; <del> import { ILanguageDetectionService } from 'vs/workbench/services/languageDetection/common/languageDetectionWorkerService'; </del> <ins> import { ILanguageDetectionService, LanguageDetectionHintConfig } from 'vs/workbench/services/languageDetection/common/languageDetectionWorkerService'; </ins> import { ThrottledDelayer } from 'vs/base/common/async'; import { ILanguageService } from 'vs/editor/common/languages/language'; import { IKeybindingService } from 'vs/platform/keybinding/common/keybinding';

Discussion:
The candidate fix for was to just disable language detection in notebooks by default. With a bit more time to work on it, a better solution should be derived.
is this fix insider released?
is it now :)
Change:
opacity: 1; } */ <ins> .monaco-workbench .notebookOverlay .cell-list-top-cell-toolbar-container:focus-within, .monaco-workbench .notebookOverlay .cell-list-top-cell-toolbar-container:hover, </ins> .monaco-workbench .notebookOverlay.notebook-editor-editable > .cell-list-container > .monaco-list > .monaco-scrollable-element > .monaco-list-rows > .monaco-list-row .cell-bottom-toolbar-container:hover, .monaco-workbench .notebookOverlay.notebook-editor-editable > .cell-list-container > .monaco-list > .monaco-scrollable-element > .monaco-list-rows > .monaco-list-row .cell-bottom-toolbar-container:focus-within { opacity: 1;

Discussion:
Issue Type: <bBug</bThe toolbar (hover or main) doesn't allow me to enter a cell above other cells. I have to select the first cell and hit 'a', or use the command palette and pick 'Insert Cell Above' VS Code version: Code - Insiders 1.59.0-insider (, 2021-07-28T19:37:22.975Z) OS version: WindowsNT x64 10.0. Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (14)</summaryExtensionVersion ------ vscode-eslint2.1.23 prettier-vscode8.1.0 python2021.8.-dev vscode-pylance2021.7.8-pre.1 jupyter2021.8. remote-containers0.190.0 remote-ssh0.65.7 remote-ssh-edit0.65.7 remote-wsl0.58.2 vscode-remote-extensionpack0.21.0 hexeditor1.8.2 js-debug-nightly2021.7.2717 live-server0.2.6 vscode-typescript-next4.4. (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
With our insert toolbar styling update, we didn't update the insert toolbar above the first cell, which is intended for inserting cells above first cell.
Fixed in both release and main branch.
closedWith
closedWith
Change:
let instantiationService: TestInstantiationService; let sessionSyncContribution: SessionSyncContribution; let fileService: FileService; <ins> let sandbox: sinon.SinonSandbox; </ins> const disposables = new DisposableStore(); <del> setup(() => { </del> <ins> suiteSetup(() => { sandbox = sinon.createSandbox(); </ins> instantiationService = new TestInstantiationService(); // Set up filesystem

Discussion:
Testing If there are no changes, we should not be able to create a new edit session. In this particular case, I would expect that an information message is being shown, and that the existing edit session is not being overwritten.
Change:
"when": "config.git.enabled && !git.missing && gitOpenRepositoryCount != 0" }, { <ins> "command": "git.stageAllMerge", "when": "config.git.enabled && !git.missing && gitOpenRepositoryCount != 0" }, { </ins> "command": "git.stageSelectedRanges", "when": "config.git.enabled && !git.missing && gitOpenRepositoryCount != 0" },

Discussion:
Issue Type: <bBug</bDuring a rebase (not sure if that's the only scenario), my SOURCE CONTROL tab display three sections, MERGE CHANGES, STAGED CHANGES and CHANGES. If I click the + button on the CHANGES section, in order to stage all items below CHANGES, VS Code also adds everything on MERGE CHANGES. VS Code version: Code - Insiders 1.45.0-insider (, 2020-04-29T05:33:59.143Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (19)</summaryExtensionVersion ------ markdown-mermaid1.5.0 better-toml0.3.2 vscode-eslint2.1.5 gitlens10.2.1 plantuml2.13.8 svg1.1.8 vscode-peacock3.7.0 chat0.33.0 rust-analyzer0.2.151 vscode-todo-parser1.9.1 remote-wsl0.44.2 vsliveshare1.0.2104 vsliveshare-audio0.1.85 vsliveshare-pack0.3.4 vscode-xml0.11.0 vscode-yaml0.7.2 crates0.4.9 vscode-hexdump1.7.2 markdown-all-in-one2.8.0 </details<!-- generated by issue reporter --
Hello I would like to work on this issue if no one else is. Regards.
hey could you please review the pr that I have opened and also could you please suggest any changes if required.
Hi I'm also working on this issue. You can check my PR
I have gone through your PR also left a comment.