jiebi/CodeConvo huggingface dataset:
Change:
Type: <bBug</bOn the right panel, where the opened files are listed, when you have a file selected and hover on another file it appears a close(x) icon, if you click that (x) the editor window that is closed is the file that is selected and not the file where you clicked (x). I keep repoen closed editor because of this recent issue. VS Code version: Code 1.82.2 (Universal) (, 2023-09-14T05:59:47.790Z) OS version: Darwin arm64 22.1.0 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (61)</summaryExtensionVersion ------ better-comments3.0.2 alpine-js-intellisense1.2.0 laravel-extra-intellisense0.6.3 sidebar-markdown-notes1.2.0 laravel-blade-spacer2.1.3 laravel-docs1.10.0 tailwind-docs2.1.0 vscode-intelephense-client1.9.5 vscode-tailwindcss0.10.0 vscode-coloured-status-bar-problems0.2.0 vscode-better-align1.4.2 laravel-goto-view1.3.9 save-commands0.5.1 vscode-notes1.1.0 githistory0.6.20 gitlens14.3.0 vscode-html-css1.13.1 prettier-vscode10.1.0 restore-terminals1.1.8 php-intellisense2.3.14 auto-rename-tag0.1.10 code-runner0.12.0 vscode-google-translate1.4.13 html-preview-vscode0.2.5 copilot1.113.423 copilot-chat0.7.1 copilot-labs0.15.1019 gitlab-workflow3.77.1 githd2.3.3 vscode-peacock4.2.2 vscode-inline-svg0.9.4 rainbow-csv3.7.1 php-namespace-resolver1.1.9 git-graph1.30.0 dotenv1.0.1 theme-monokai-pro-vscode1.2.1 empty-directory-extension0.0.6 test-adapter-converter0.1.8 resourcemonitor1.0.7 laravel-goto-components1.2.0 sftp1.16.3 vscode-configurable-shortcuts1.0.3 laravel-blade1.34.0 laravel5-snippets1.17.0 material-icon-theme4.30.1 vscode-thunder-client2.12.0 vscode-yaml1.14.0 laravel-artisan0.0.31 vue-vscode-snippets3.1.1 vscode-blade-formatter0.23.1 svg-preview2.8.3 vscode-fileutils3.10.3 git-prefix1.3.1 workspace-explorer2.3.0 luna-paint0.16.0 remove-empty-lines1.0.1 vscode-icons12.5.0 volar1.8.11 vscode-typescript-vue-plugin1.8.11 vuetify-vscode0.2.0 php-debug1.33.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
/gifPlease
Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, files are preferred as they are displayed inline on GitHub. You may find helpful as a browser-based gif recording tool. If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording ( in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue. Happy coding!
Sure. !
Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from:
Bisecting shows that is the trouble. It reproduces easily when you have focus in an open editor and click X on another editor.

Discussion:
if (focus) { const selection: Array<IEditorIdentifier | IEditorGroup> = list.getSelectedElements().filter(onlyEditorGroupAndEditor); <del> if (selection.length > 0) { </del> <ins> if (selection.length > 1) { </ins> return selection.map(elementToContext); }
Change:
Hi, similar to this issue but in my case the line numbers are within parenthesis and are not recognized. ! Current behavior: The file is recognized and I can click on it to open it but will not consider the linenumber Expected behavior: When the file is opened after click, it takes me to the right line number <!-- 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.82.2 <-- LATEST OS Version: Win 10 Steps to Reproduce: a cpp file with some syntax error that cpp file with FastBuild Note: reopening this issue after updating to latest version and verifying the bug is still there.
any more info on reproducing this? ! Do you get an underline when you hover it without holding ctrl? Is there something special about the path, like is it a remote mounted path or using symlinks?
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
Yes there is an underline on hover. No special paths, no mounted path, no symlinks.
Is the line number included in the underline? If you hover it without holding ctrl or cmd do you get a hover appearing?
I notice 2 cases: hover the entire line is underlined including the text to the right of the line number, and on click it takes me to a random line ! hover only the filepath and number are underlined (not including text to the right of line number), and on click it works fine ! I also noticed that the filepath slashes are forward slashes in normal prints and backward slashes in error prints, not sure if that is relevant so mentioning just in case.
I think I can reproduce: ! This is only on the prompt line of , the line with (5) works fine. It's weird that it happens sometimes but not others.
Pretty hard to reproduce consistently
On Windows sometimes weird stuff happens with line wrapping due to pty emulation, when the line is wrapped, it ends up matching this regex for an eslint-style multi-line link: !
Ok got the repro: Open pwsh Run (or some other file that exists) Run This makes the upwards scan succeed as it found which matches eslint's link format.

Discussion:
// Eslint: //   /some/file //     16:5  error ... <del> / *(?<link>(?<line>d+):(?<col>d+)?)/ </del> <ins> /^ *(?<link>(?<line>d+):(?<col>d+)?)/ </ins> ]; const gitDiffMatchers = [
Change:
<!-- 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?: No - relates to plugin activation. <!-- 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.81.1 (server) OS Version: Ubuntu frontend, Windows frontend Steps to Reproduce: have a plugin that uses the activation event and launches a walkthrough as part of its activation using the command . run with VSCode Server, this will occasionally cause an error like this to appear: ! It seems that what must be happening is that the plugin is executing its command before is run to register the URI handling for the special URI that . That raises a question about the activation event. I would consider startup to be finished only when all have been instantiated, but that condition doesn't seem to be enforced. The error is more frequent when the window in which the editor is running is in the background, presumably because it's allocated fewer resources and getting through fewer of the s that the application activation sequence runs through before the backend declares (unilaterally?) that startup has finished - in fact, it will just declare victory , even if the other (exclusively backend?) events it's waiting for don't complete.
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.82.2. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
Thanks, but it doesn't appear that any changes have been made in the code in this area since 1.81, so I believe the problem still exists.
I can't repro the original issue, but verified by code review.
Reverted this change due to: Will work on this in February

Discussion:
}); Registry.as<IWorkbenchContributionsRegistry>(WorkbenchExtensions.Workbench) <del> .registerWorkbenchContribution(StartupPageContribution, LifecyclePhase.Restored); </del> <ins> .registerWorkbenchContribution(StartupPageContribution, LifecyclePhase.Starting); </ins>
Change:
We have a color that draws at the end of the last pinned tab: ! For multi-row scenario, this color should probably hide.

Discussion:
private redrawTabBorders(tabIndex: number, tabContainer: HTMLElement): void { const isTabSticky = this.tabsModel.isSticky(tabIndex); const isTabLastSticky = isTabSticky && this.tabsModel.stickyCount === tabIndex + 1; <ins> const showLastStickyTabBorderColor = this.tabsModel.stickyCount !== this.tabsModel.count; </ins> // Borders / Outline <del> const borderRightColor = ((isTabLastSticky ? this.getColor(TAB_LAST_PINNED_BORDER) : undefined) || this.getColor(TAB_BORDER) || this.getColor(contrastBorder)); </del> <ins> const borderRightColor = ((isTabLastSticky && showLastStickyTabBorderColor ? this.getColor(TAB_LAST_PINNED_BORDER) : undefined) || this.getColor(TAB_BORDER) || this.getColor(contrastBorder)); </ins> tabContainer.style.borderRight = borderRightColor ? `1px solid ${borderRightColor}` : ''; tabContainer.style.outlineColor = this.getColor(activeContrastBorder) || ''; }
Change:
<!-- 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. --- VS Code Version: OS Version: Steps to Reproduce: Python issue reporter selects (, instead of )

Discussion:
if (extensionsSelector) { const { selectedExtension } = this.issueReporterModel.getData(); reset(extensionsSelector, this.makeOption('', localize('selectExtension', "Select extension"), true), ...extensionOptions.map(extension => makeOption(extension, selectedExtension))); <del> extensionsSelector.selectedIndex = 0; </del> <ins> if (!selectedExtension) { extensionsSelector.selectedIndex = 0; } </ins> this.addEventListener('extension-selector', 'change', (e: Event) => { const selectedExtensionId = (<HTMLInputElement>e.target).value;
Change:
<!-- 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: OS Version (in docker): building and running the following dockerfile gives the following: changing the command in the docker file to gives the following: creating a non-sudo user in the docker container and running it from that works, but that leads to a headache of problems with other parts of my docker image. ideally, the fix suggested by code in the first example would solve this but it doesnt.
related to
doesn't apply to . That's an option for electron, and doesn't run electron. Just omit that argument and run the command.
omitting just makes it complain about being unexpected. no combination of arguments fixes this as far as i can tell causes causes causes causes
What code print?
i put the output of at the top of my issue, but here it is again:
would it be possible to reopen this? it seems like there is no solution based on whats been said so far
Looks like a workaround would be setting when you call . But the better solution is just to use the CLI () instead of the full desktop install. This will be fixed when the desktop install uses the native CLI as its primary entrypoint.
Works with . The is important, otherwise it will be misinterpreted.
I still get the same error: adding CANRUNAS_ROOT=1 did not make a difference.
I cannot repro, can you share the exact command you ran?
All is good, sorry, I tested against an old version!
This issue will be closed because it appears to be verified

Discussion:
for i in "$@" do case "$i" in <del> --user-data-dir | --user-data-dir=* | --file-write ) </del> <ins> --user-data-dir | --user-data-dir=* | --file-write | tunnel | serve-web ) </ins> CAN_LAUNCH_AS_ROOT=1 ;; esac
Change:
open a file from a pull request get an error saying id cannot be read from undefined
this is a regression from
Yes, I too saw this when testing day before yesterday, but as soon as I updated this went away.

Discussion:
/** * Remove all falsy values from `array`. The original array IS modified. */ <del> export function coalesceInPlace<T>(array: Array<T | undefined | null>): void { </del> <ins> export function coalesceInPlace<T>(array: Array<T | undefined | null>): asserts array is Array<T> { </ins> let to = 0; for (let i = 0; i < array.length; i++) { if (!!array[i]) {

override setActions(_primary: readonly IAction[], _secondary: readonly IAction[] = [], menuIds?: readonly MenuId[]): void { this._sessionDisposables.clear(); <del> const primary = _primary.slice(); </del> <ins> const primary: Array<IAction | undefined> = _primary.slice(); // for hiding and overflow we set some items to undefined </ins> const secondary = _secondary.slice(); const toggleActions: IAction[] = []; let toggleActionsCheckedCount: number = 0; <del> const extraSecondary: IAction[] = []; </del> <ins> const extraSecondary: Array<IAction | undefined> = []; </ins> let someAreHidden = false; // unless disabled, move all hidden items to secondary group or ignore them

// hidden items move into overflow or ignore if (action.hideActions.isHidden) { someAreHidden = true; <del> primary[i] = undefined!; </del> <ins> primary[i] = undefined; </ins> if (this._options?.hiddenItemStrategy !== HiddenItemStrategy.Ignore) { extraSecondary[i] = action; }

// count for max if (this._options?.overflowBehavior !== undefined) { <del> const exemptedIds = intersection(new Set(this._options.overflowBehavior.exempted), Iterable.map(primary, a => a.id)); </del> <ins> const exemptedIds = intersection(new Set(this._options.overflowBehavior.exempted), Iterable.map(primary, a => a?.id)); </ins> const maxItems = this._options.overflowBehavior.maxItems - exemptedIds.size; let count = 0;

continue; } if (count >= maxItems) { <del> primary[i] = undefined!; </del> <ins> primary[i] = undefined; </ins> extraSecondary[i] = action; } } } <ins> // coalesce turns Array<IAction|undefined> into IAction[] </ins> coalesceInPlace(primary); coalesceInPlace(extraSecondary); super.setActions(primary, Separator.join(extraSecondary, secondary));
Change:
vscode window (given you have setting to put debug controls in the command center notice how the command center includes debug controls and then right away disappear See:

Discussion:
hoverDelegate: IHoverDelegate, @IInstantiationService instantiationService: IInstantiationService, @IQuickInputService quickInputService: IQuickInputService, <del> @IKeybindingService keybindingService: IKeybindingService </del> ) { this.element.classList.add('command-center');

import { debugToolBarBackground, debugToolBarBorder } from 'vs/workbench/contrib/debug/browser/debugColors'; import { CONTINUE_ID, CONTINUE_LABEL, DISCONNECT_AND_SUSPEND_ID, DISCONNECT_AND_SUSPEND_LABEL, DISCONNECT_ID, DISCONNECT_LABEL, FOCUS_SESSION_ID, FOCUS_SESSION_LABEL, PAUSE_ID, PAUSE_LABEL, RESTART_LABEL, RESTART_SESSION_ID, REVERSE_CONTINUE_ID, STEP_BACK_ID, STEP_INTO_ID, STEP_INTO_LABEL, STEP_OUT_ID, STEP_OUT_LABEL, STEP_OVER_ID, STEP_OVER_LABEL, STOP_ID, STOP_LABEL } from 'vs/workbench/contrib/debug/browser/debugCommands'; import * as icons from 'vs/workbench/contrib/debug/browser/debugIcons'; <del> import { CONTEXT_DEBUG_STATE, CONTEXT_FOCUSED_SESSION_IS_ATTACH, CONTEXT_MULTI_SESSION_DEBUG, CONTEXT_STEP_BACK_SUPPORTED, CONTEXT_SUSPEND_DEBUGGEE_SUPPORTED, CONTEXT_TERMINATE_DEBUGGEE_SUPPORTED, IDebugConfiguration, IDebugService, State, VIEWLET_ID } from 'vs/workbench/contrib/debug/common/debug'; </del> <ins> import { CONTEXT_DEBUG_STATE, CONTEXT_FOCUSED_SESSION_IS_ATTACH, CONTEXT_IN_DEBUG_MODE, CONTEXT_MULTI_SESSION_DEBUG, CONTEXT_STEP_BACK_SUPPORTED, CONTEXT_SUSPEND_DEBUGGEE_SUPPORTED, CONTEXT_TERMINATE_DEBUGGEE_SUPPORTED, IDebugConfiguration, IDebugService, State, VIEWLET_ID } from 'vs/workbench/contrib/debug/common/debug'; </ins> import { IWorkbenchLayoutService } from 'vs/workbench/services/layout/browser/layoutService'; import { Codicon } from 'vs/base/common/codicons';

title: 'Debug', icon: Codicon.debug, order: 1, <del> when: ContextKeyExpr.and(CONTEXT_DEBUG_STATE.notEqualsTo('inactive'), ContextKeyExpr.equals('config.debug.toolBarLocation', 'commandCenter')) </del> <ins> when: ContextKeyExpr.and(CONTEXT_IN_DEBUG_MODE, ContextKeyExpr.equals('config.debug.toolBarLocation', 'commandCenter')) </ins> }); registerDebugToolBarItem(CONTINUE_ID, CONTINUE_LABEL, 10, icons.debugContinue, CONTEXT_DEBUG_STATE.isEqualTo('stopped'));
Change:
<!-- 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. --In the Source Control panel, "Reveal in Explorer View" of context menu is above "Reveal in File Explorer". <img src="" width="300"But context menu of the tabs, "Reveal in Explorer View" is below "Reveal in File Explorer". <img src="" width="300"It's not consistent. It will occur mis-clicking.
Could you triage the issue?
would you be up to swap the order you contribute from the git extension?

Discussion:
"group": "inline@2" }, { <del> "command": "git.revealInExplorer", "when": "scmProvider == git && scmResourceGroup == merge", "group": "2_view@1" }, { </del> "command": "git.revealFileInOS.linux", "when": "scmProvider == git && scmResourceGroup == merge && remoteName == '' && isLinux", <del> "group": "2_view@2" </del> <ins> "group": "2_view@1" </ins> }, { "command": "git.revealFileInOS.mac", "when": "scmProvider == git && scmResourceGroup == merge && remoteName == '' && isMac", <del> "group": "2_view@2" </del> <ins> "group": "2_view@1" </ins> }, { "command": "git.revealFileInOS.windows", "when": "scmProvider == git && scmResourceGroup == merge && remoteName == '' && isWindows", <ins> "group": "2_view@1" }, { "command": "git.revealInExplorer", "when": "scmProvider == git && scmResourceGroup == merge", </ins> "group": "2_view@2" }, {

"group": "inline@2" }, { <del> "command": "git.revealInExplorer", "when": "scmProvider == git && scmResourceGroup == index", "group": "2_view@1" }, { </del> "command": "git.revealFileInOS.linux", "when": "scmProvider == git && scmResourceGroup == index && remoteName == '' && isLinux", <del> "group": "2_view@2" </del> <ins> "group": "2_view@1" </ins> }, { "command": "git.revealFileInOS.mac", "when": "scmProvider == git && scmResourceGroup == index && remoteName == '' && isMac", <del> "group": "2_view@2" </del> <ins> "group": "2_view@1" </ins> }, { "command": "git.revealFileInOS.windows", "when": "scmProvider == git && scmResourceGroup == index && remoteName == '' && isWindows", <ins> "group": "2_view@1" }, { "command": "git.revealInExplorer", "when": "scmProvider == git && scmResourceGroup == index", </ins> "group": "2_view@2" }, {

"group": "1_modification@3" }, { <del> "command": "git.revealInExplorer", "when": "scmProvider == git && scmResourceGroup == workingTree", "group": "2_view@1" }, { </del> "command": "git.revealFileInOS.linux", "when": "scmProvider == git && scmResourceGroup == workingTree && remoteName == '' && isLinux", <del> "group": "2_view@2" </del> <ins> "group": "2_view@1" </ins> }, { "command": "git.revealFileInOS.mac", "when": "scmProvider == git && scmResourceGroup == workingTree && remoteName == '' && isMac", <del> "group": "2_view@2" </del> <ins> "group": "2_view@1" </ins> }, { "command": "git.revealFileInOS.windows", "when": "scmProvider == git && scmResourceGroup == workingTree && remoteName == '' && isWindows", <ins> "group": "2_view@1" }, { "command": "git.revealInExplorer", "when": "scmProvider == git && scmResourceGroup == workingTree", </ins> "group": "2_view@2" }, {
Change:
I don't have precise repro steps, but maybe: search for something scroll all the way down clear search searching animation persists
I'm unable to repro the issue. Let me know if there's any devtools errors next time it occurs.
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
just reproduced this and will give us the logs
In the case of JooYoung, the search wasn't performed at all.
just reproduced myself
The error likely means there's an array that's undefined, but I'll probably have to reproduce the issue on OSS to actually see what's going on Example REPL run
it takes much longer than expected to stop - is there a long happening for input change or... ?
I'm unable to repro on the latest Insiders on Windows or macOS. For me, clearing the search stops it immediately.

Discussion:
} } <ins> if (!enumToUse && (prop.enumItemLabels || enumDescriptions || enumDescriptionsAreMarkdown)) { console.error(`The setting ${key} has enum-related fields, but doesn't have an enum field. This setting may render improperly in the Settings editor.`); } </ins> result.push({ key, value,

enum: enumToUse, enumDescriptions: enumDescriptions, enumDescriptionsAreMarkdown: enumDescriptionsAreMarkdown, <ins> enumItemLabels: prop.enumItemLabels, </ins> uniqueItems: prop.uniqueItems, tags: prop.tags, disallowSyncIgnore: prop.disallowSyncIgnore,

deprecationMessage: prop.markdownDeprecationMessage || prop.deprecationMessage, deprecationMessageIsMarkdown: !!prop.markdownDeprecationMessage, validator: createValidator(prop), <del> enumItemLabels: prop.enumItemLabels, </del> allKeysAreBoolean, editPresentation: prop.editPresentation, order: prop.order,

setting.descriptionRanges.push({ startLineNumber: this.lineCountWithOffset, startColumn: this.lastLine.indexOf(line) + 1, endLineNumber: this.lineCountWithOffset, endColumn: this.lastLine.length }); } <del> if (setting.enumDescriptions && setting.enumDescriptions.some(desc => !!desc)) { </del> <ins> if (setting.enum && setting.enumDescriptions?.some(desc => !!desc)) { </ins> setting.enumDescriptions.forEach((desc, i) => { const displayEnum = escapeInvisibleChars(String(setting.enum![i])); const line = desc ?