jiebi/CodeConvo huggingface dataset:
Change:
if (success.status === 200) { try { const obj = JSON.parse(success.responseText); <del> if (obj && Array.isArray(obj)) { const results = <{ package: SearchPackageInfo; }[]>obj; </del> <ins> if (obj && obj.objects && Array.isArray(obj.objects)) { const results = <{ package: SearchPackageInfo; }[]>obj.objects; </ins> for (const result of results) { this.processPackage(result.package, addValue, isLast, collector); }

Discussion:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --Hi So I noticed that the autocomplete is slow to update or can sometimes return wrong/outdated information. For example: if a package releases a patch / new version, it can take hours, maybe days until the autocompletion also suggests that version. My second concern about this is that it's actually using which is not run by npm and they have a separate which users are not aware of when using this VS Code extension. Source code From a privacy policy perspective / GDPR and also reliability issues it seems appropriate to remove all usage of this third-party API and only use npm's. Relevant past issues about npms from this repository (I found many more in other repositories):
To verify, check that code completion in dependencies of work as expected. run VSCode in a environment where is not on the path, and use hovers over dependencies of . as dependency and verify that the hover shows the actual latest version (currently 15)
Change:
"native-is-elevated": "0.4.3", "native-keymap": "^3.3.2", "native-watchdog": "^1.4.1", <del> "node-pty": "0.11.0-beta31", </del> <ins> "node-pty": "0.11.0-beta32", </ins> "spdlog": "^0.13.0", "tas-client-umd": "0.1.6", "v8-inspect-profiler": "^0.1.0",

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:
readonly minimap: ModelDecorationMinimapOptions | null; readonly glyphMarginClassName: string | null; readonly linesDecorationsClassName: string | null; <ins> readonly firstLineDecorationClassName: string | null; </ins> readonly marginClassName: string | null; readonly inlineClassName: string | null; readonly inlineClassNameAffectsLetterSpacing: boolean;

Discussion:
When a section is wrapped after folding. Fold its parent with itself unfolded will display several wrong fold indicators.
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.724 --- <!-- score: 0.616 --- <!-- score: 0.606 --- <!-- score: 0.575 --- <!-- score: 0.569 --<!-- potentialduplicatescomment --
!
Change:
} const raw = await readfile(templatePath, 'utf8'); <del> return raw.replace(/^s*#.*$n?/gm, '').trim(); </del> <ins> return raw.trim(); </ins> } catch (err) { return '';

Discussion:
VSCode Version: 1.1.1 OS Version: OS X Steps to Reproduce: into a merge conflict accepting Git's default message. It's equal to is no way to do that!
Will mention that it's also equivalent to and saving the default message that shows up in your editor - hence a very common workflow
My workaround is to invoke from a terminal. Maybe if the commit message field is empty, VSCode could just call as well and leave it up to user's configuration what happens (in my case, it would open a text editor from my system variable, which is fine).
Has the pull request been reviewed yet? Can it be pulled in?
Verification: When having a merge commit, VS Code should now automatically populate the input box with the default git merge commit message, so the user can just accept it.
Change:
debug!(self.logger, "Starting server with command... {:?}", cmd); <ins> // On Windows spawning a code-server binary will run cmd.exe /c C:pathtocode-server.cmd... // This spawns a cmd.exe window for the user, which if they close will kill the code-server process // and disconnect the tunnel. To prevent this, pass the CREATE_NO_WINDOW flag to the Command // only on Windows. // Original issue: https://github.com/microsoft/vscode/issues/184058 // Partial fix: https://github.com/microsoft/vscode/pull/184621 #[cfg(target_os = "windows")] let cmd = cmd.creation_flags(winapi::um::winbase::CREATE_NO_WINDOW); </ins> let child = cmd .stderr(std::process::Stdio::piped()) .stdout(std::process::Stdio::piped())

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: code-cli insiders 1.81.0 (commit ) OS Version: Windows 10 21H2 .3086 I believe is only partially fixed, even in code-cli 1.81.0 (commit ). The window does not appear when only or code- (the cli) is running, however, as soon as a tunnel is connected to, a window appears (as code- is run). If the user closes the window, the tunnel connection is dropped. I believe the fix is to pass CREATENOWINDOW to creationflags in spawnserverprocess as seen here: However, without the proprietary "mixin" , it seems my builds of code cli are not able to properly run code-server, failing with [2023-06-28 19:09:25] info [rpc.3] Starting server... [2023-06-28 19:09:25] debug [rpc.3] Starting server with command... Command { std: "C:Usersredacted.vscode-insiderscliserversStable-serverbincode-" "--connection-token=redacted" "--accept-server-license-terms" "--start-server" "--enable-remote-auto-shutdown" "--socket-path=.pipecode-oss--ab53-485a-bc7d-", killon_drop: false } [2023-06-28 19:09:25] trace [rpc.3] [codeserver.13] The syntax of the command is incorrect.

[2023-06-28 19:09:26] debug [tunnels::connections::ws] received liveness pong To reproduce the issue, on a windows machine: an arbitrary tunnel to authorize the machine: code- tunnel --name test the tunnel with the code at the tunnel service with code- service tunnel install that no is visable, and code- is running in the background connect to the tunnel again a appear on the desktop, close the and observe the tunnel disconnect on
Thanks for the issue. Please feel free to put in the PR, I can edit it if needed so that you get the credit for the fix :)
Confirming this fix is working in . On tunnel connect a does not appear.
Change:
get viewModel(): ViewModel { return this._viewModel; } private listLabels!: ResourceLabels; private inputRenderer!: InputRenderer; <ins> private actionButtonRenderer!: ActionButtonRenderer; </ins> private readonly disposables = new DisposableStore(); constructor(

Discussion:
This should not be a valid state: ! It should automatically switch to this: ! is how the SCM Input does it.
I am seeing this state when I am navigating using up/down buttons. Is it expected? ! !
That is probably unexpected, but I will let confirm that.
Yeah, just like the text box. The list doesn't support completely disabling it at the model layer. We can only disable it at the click operation.
Change:
} private async prepareTopFrame(subject: InspectSubject, callFrames: ITestMessageStackFrame[]) { <ins> // ensure the messageContainer is in the DOM so renderers can calculate the // dimensions before it's rendered in the list. this.messageContainer.style.visibility = 'hidden'; this.stackContainer.appendChild(this.messageContainer); </ins> const topFrame = this.currentTopFrame = this.instantiationService.createInstance(MessageStackFrame, this.messageContainer, this.followupWidget, subject); topFrame.showHeader.set(callFrames.length > 0, undefined); const provider = await findAsync(this.contentProviders, p => p.update(subject));

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/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --Version: 1.92.0 (Universal) Commit: Date: 2024-07-31T23:26:45.634Z Electron: 30.1.2 ElectronBuildId: Chromium: 124.0.6367.243 20.14.0 V8: 12.4.254.20-electron.0 OS: Darwin arm64 23.5.0 Steps to Reproduce: this snippet in the test-provider-sample project running the test, both the editor peek view and test result view do not render correctly. !
Sorry, this got lost in the shuffle of the call stack UI :(
Verification steps: out the of vscode-extension-samples into and F5 the "easy math" test in Open the error messages for all the tests that fail and verify they're all visible
Change:
f1: true, keybinding: { weight: KeybindingWeight.WorkbenchContrib + 100, <del> primary: KeyCode.Escape </del> <ins> primary: KeyCode.Escape, when: AnyScopedVoiceChatInProgress </ins> }, icon: spinningLoading, precondition: GlobalVoiceChatInProgress, // need global context here because of `f1: true`

Discussion:
Type: <bBug</bI ccould not close inline chats or quick picks anymore. Looks like captured all esc shortcuts. I had used voice input during the session. VS Code version: Code - Insiders 1.90.0-insider (, 2024-05-17T17:53:51.447Z) OS version: Darwin x64 23.4.0 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (64)</summaryExtensionVersion ------ html-snippets0.2.1 tsl-problem-matcher0.6.2 emojisense0.10.0 github-markdown-preview0.3.0 markdown-checkbox0.4.0 markdown-emoji0.3.0 markdown-footnotes0.1.1 markdown-mermaid1.23.0 markdown-preview-github-styles2.0.4 markdown-yaml-preamble0.1.0 mermaid-markdown-syntax-highlighting1.6.3 vscode-tailwindcss0.11.68 esbuild-problem-matchers0.0.3 vscode-eslint2.4.4 kusto0.4.4 EditorConfig0.16.4 prettier-vscode10.4.0 auto-close-tag0.5.15 auto-rename-tag0.1.10 codespaces1.16.22 copilot1.194.885 copilot-chat0.16. copilot-nes0.0.1 remotehub0.63. vscode-github-actions0.26.2 vscode-pull-request-github0.89. headwind1.7.0 debug-tracker-vscode0.0.15 peripheral-viewer1.4.6 vscode-azureresourcegroups0.9.0 vscode-docker1.29.1 vscode-dotnet-runtime2.0.5 debugpy2024.7. isort2023.13. python2024.7. vscode-pylance2024.5.101 jupyter2024.4. jupyter-keymap1.1.2 jupyter-renderers1.0.17 remote-containers0.366.0 remote-ssh0.112. remote-ssh-edit0.86.0 remote-wsl0.88.2 anycode0.0.73 azure-repos0.39.

cpptools1.20.5 live-server0.4.13 remote-repositories0.40.0 remote-server1.6. vscode-github-issue-notebooks0.0.130 vscode-markdown-notebook0.0.26 vscode-selfhost-test-provider0.3.25 vscode-speech0.9. vscode-typescript-next5.5. prisma5.14.0 vscode-xml0.26.1 vscode-yaml1.14.0 kuskus-kusto-syntax-highlighting2.0.2 svg-preview2.8.3 pdf1.2.2 vscode-mdx1.8.5 volar2.0.10 gitblame10.11.0 markdown-all-in-one3.6.2 (3 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
are you certain its that command? It is only enabled when a voice chat session is active. When you set the log level to trace, please check what is printed when you trigger in the chat widget:
Happened again on a different machines. The main step of the STR seems to be using voice input (I mostly demo the hold down key usage) Both times I did troubleshooting and it pointed to the stop listening command.
I need some steps to reproduce that you lead you to the issue and the precise location in the UI where this happens (globally anywhere or when you are in a chat input field?)
Change:
// History item change historyItemChanges.push({ uri: historyItemUri, <del> originalUri: toGitUri(change.originalUri, ref1), modifiedUri: toGitUri(change.originalUri, ref2), </del> <ins> originalUri: toGitUri(change.originalUri, originalRef), modifiedUri: toGitUri(change.originalUri, modifiedRef), </ins> renameUri: change.renameUri, });

Discussion:
Testing Although technically correct, we should use the actual commit's short hash, not the syntax, for left side: !
Change:
return true; } <ins> private handleOverrides(overrides: ISetting[], configurationRegistry: IStringDictionary<IRegisteredConfigurationPropertySchema>, markerData: IMarkerData[]): void { for (const setting of overrides || []) { const configuration = configurationRegistry[setting.key]; if (configuration) { if (configuration.scope !== ConfigurationScope.LANGUAGE_OVERRIDABLE) { markerData.push({ severity: MarkerSeverity.Hint, tags: [MarkerTag.Unnecessary], ...setting.range, message: nls.localize('unsupportLanguageOverrideSetting', "This setting cannot be applied because it is not registered as language override setting.") }); } } else { markerData.push(this.gemerateUnknownConfigurationMarker(setting)); } } } </ins> private handleLocalUserConfiguration(setting: ISetting, configuration: IConfigurationPropertySchema, markerData: IMarkerData[]): void { if (!this.userDataProfileService.currentProfile.isDefault) { if (isEqual(this.userDataProfilesService.defaultProfile.settingsResource, this.settingsEditorModel.uri) && configuration.scope !== ConfigurationScope.APPLICATION) {

Discussion:
Add an unrecognized setting to See that it is correctly dimmed with no warning underline Add it to a language-specific settings block There is a warning, "This setting does not support per-language configuration which is misleading" !
Yeah, this feature is not supported for language specific settings.
To verify: Open and have following snippetMake sure first two settings and are shown dimmed with proper message.
<!-- 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:
} // Otherwise try in next group that has editors <ins> const handledGroups = new Set<number>(); </ins> let currentGroup: IEditorGroup | undefined = this.editorGroupService.activeGroup; <del> while (currentGroup) { </del> <ins> while (currentGroup && !handledGroups.has(currentGroup.id)) { </ins> currentGroup = this.editorGroupService.findGroup({ location: GroupLocation.NEXT }, currentGroup, true); if (currentGroup) { <ins> handledGroups.add(currentGroup.id); </ins> const groupEditors = currentGroup.getEditors(EditorsOrder.SEQUENTIAL); if (groupEditors.length > 0) { return { editor: groupEditors[0], groupId: currentGroup.id };

Discussion:
Steps: open 2 empty groups pick "Open Previous Editor" or "Open Next Editor" Endless loop.
Change:
* See also: https://www.w3.org/TR/wai-aria/states_and_properties#aria-label */ getAriaLabel(tree: ITree, element: any): string; <ins> getPosInSet?(tree: ITree, element: any): string; getSetSize?(): string; </ins> } export /* abstract */ class ContextMenuEvent {

Discussion:
The tree/list is virtualized and as such a screen reader cannot make a correct statement on the number of entries. We should leverage and for that purpose within the tree and list widgets. The widgets know the number of elements to render and the currently selected items position in the set. /cc
Makes sense, I can look into it in june
Accidently closed this by PR which only address the list widget, still gotta do it for the tree
After looking into this with we have fixed this issue for the , however for the tree the situation is a bit more complex: It is not exactly specified what the and should be with respect to the tree structure. Should they be absolute or only relative to the siblings. In both of the cases we have an issue that the tree smartly chooses the minimal set of elements that need to be re-rendered, so if an element A gets removed and element B is above it, B will not get re-rendered and will still have the wrong attribute. Due to that we would need a bigger refactoring in order to fix this for the tree. So renaming this issue and pushing it to backlog for now.
The originating issue -- -- came in w.r.t. the Command Palette that displays a list. perhaps the root issue is that the implementation of the Command Palette uses a tree to display a list and that makes it difficult to express the list to Screen Readers ?
+1 for making the command palette use the list. I could also look into this when I get cycles if does not mind.
yeah +1 for using list for quick open, that would be very nice . I hope there are no things in tree that quick open depends on.
I have created this issue to track it
Change:
private readonly isAlertEnabledCache = new Cache((event: { readonly cue: AudioCue; readonly userGesture?: boolean }) => { const settingObservable = observableFromEvent( Event.filter(this.configurationService.onDidChangeConfiguration, (e) => <del> e.affectsConfiguration(event.cue.settingsKey) </del> <ins> e.affectsConfiguration(event.cue.alertSettingsKey!) </ins> ), () => event.cue.alertSettingsKey ? this.configurationService.getValue<true | false | 'userGesture' | 'always' | 'never'>(event.cue.alertSettingsKey) : false ); return derived(reader => { <del> /** @description audio cue enabled */ </del> <ins> /** @description alert enabled */ </ins> const setting = settingObservable.read(reader); if ( !this.screenReaderAttached.read(reader)

Discussion:
When using the command, Roberto did not know there was a configure action available. He said: It works, but in all my time using the editor, it never occurred to me to try using the tab key in that list. I always assumed it was read only. Originally posted by in
also this discoverability issue. Additionally, he found that has to be pressed twice to reach the settings gear when running .
He suggested we use checkboxes instead and combine with .
Need to assess which other actions we need to fix
I think it is possible using the quick pick api to render checkboxes for this. Let me un-assign Tyler and in case you need help with the API feel free to reach out to me and we can find the right usage.
Change:
return false; } <del> if (picksFilter.length > 0 && this.options?.noResultsPick) { </del> <ins> // We show the no results pick if we have no input to prevent completely empty pickers #172613 if ((picksFilter.length > 0 || picker.hideInput) && this.options?.noResultsPick) { </ins> items = [this.options.noResultsPick]; } }

Discussion:
<img width="731" alt="image" src="https://user-"- open a new empty window bring up the recently opened picker without input field ("quick nav") I use :
possibly related to but we probably should have some sort of nice empty state fior this Quick Access Provider.
I remember that back in the old days we just opened quick pick with an input field in those cases where we had no entries. So this seems like a regression to me, not sure how recent though.
a regression from I really think we should fix this as users will see a broken / non-existing quick open widget.
Change:
'out-build/vs/base/node/ps.sh', // Terminal shell integration <del> 'out-build/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh', 'out-build/vs/workbench/contrib/terminal/browser/media/.zshrc', </del> 'out-build/vs/workbench/contrib/terminal/browser/media/shellIntegration.ps1', <ins> 'out-build/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh', 'out-build/vs/workbench/contrib/terminal/browser/media/shellIntegration.zsh', </ins> '!**/test/**' ];

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/No Yes. <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.65.0-insider OS Version: MacOS12.2.2 Steps to Reproduce: with setting new terminal <img width="1440" alt="image" src="https://user-"
Thanks, we're aware of this issue and have been working toward its resolution