jiebi/CodeConvo huggingface dataset:
Change:
Type: <bBug</bPython installed settings and look at the setting Bug The setting description is hard to read because there is no space between the paragraph elements and code blocks ! VS Code version: Code - Insiders 1.75.0-insider (Universal) (, 2023-01-25T05:23:34.922Z) OS version: Darwin x64 22.2.0 Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<!-- generated by issue reporter --

Discussion:
.settings-editor > .settings-body .settings-tree-container .setting-item-contents .setting-item-markdown * { margin: 0px; } <ins> .settings-editor > .settings-body .settings-tree-container .setting-item-contents .setting-item-markdown *:not(:last-child) { margin-bottom: 8px; } </ins> .settings-editor > .settings-body .settings-tree-container .setting-item-contents .edit-in-settings-button { opacity: 0.9;
Change:
Type: <bBug</bstick scroll to high contrast down in a file Bug There is no contrast between the stick scroll content and the normal editor content: ! Related VS Code version: Code - Insiders 1.75.0-insider (Universal) (, 2023-01-26T05:22:17.192Z) OS version: Darwin x64 22.2.0 Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<!-- generated by issue reporter --
For verification: sticky scroll, switch to high-contrast and scroll down the file. should see a border on the bottom of the sticky scroll widget
I see it in dark theme but not light high contrast: !

Discussion:
*--------------------------------------------------------------------------------------------*/ .monaco-editor .sticky-line { <del> color : var(--vscode-editorLineNumber-foreground); overflow : hidden; white-space : nowrap; display : inline-block; </del> <ins> color: var(--vscode-editorLineNumber-foreground); overflow: hidden; white-space: nowrap; display: inline-block; </ins> } .monaco-editor .sticky-line-number { <del> text-align : right; float : left; </del> <ins> text-align: right; float: left; </ins> } .monaco-editor .sticky-line-root { <del> background-color : inherit; overflow : hidden; white-space : nowrap; width : 100%; </del> <ins> background-color: inherit; overflow: hidden; white-space: nowrap; width: 100%; } .monaco-editor.hc-black .sticky-widget, .monaco-editor.hc-white .sticky-widget { border-bottom: 1px solid var(--vscode-contrastBorder); </ins> } .monaco-editor .sticky-line-root:hover { background-color: var(--vscode-editorStickyScrollHover-background); <del> cursor : pointer; </del> <ins> cursor: pointer; </ins> } .monaco-editor .sticky-widget { <del> width : 100%; box-shadow : var(--vscode-scrollbar-shadow) 0 3px 2px -2px; z-index : 11; background-color : var(--vscode-editorStickyScroll-background); </del> <ins> width: 100%; box-shadow: var(--vscode-scrollbar-shadow) 0 3px 2px -2px; z-index: 11; background-color: var(--vscode-editorStickyScroll-background); </ins> } .monaco-editor .sticky-widget.peek { <del> background-color : var(--vscode-peekViewEditorStickyScroll-background); </del> <ins> background-color: var(--vscode-peekViewEditorStickyScroll-background); </ins> }

} const editorLineHeight = this._editor.getOption(EditorOption.lineHeight); const widgetHeight: number = this._lineNumbers.length * editorLineHeight + this._lastLineRelativePosition; <ins> this._rootDomNode.style.display = widgetHeight > 0 ? 'block' : 'none'; </ins> this._rootDomNode.style.height = widgetHeight.toString() + 'px'; const minimapSide = this._editor.getOption(EditorOption.minimap).side; if (minimapSide === 'left') {
Change:
Type: <bBug</bstick scroll to high contrast down in a file Bug There is no contrast between the stick scroll content and the normal editor content: ! Related VS Code version: Code - Insiders 1.75.0-insider (Universal) (, 2023-01-26T05:22:17.192Z) OS version: Darwin x64 22.2.0 Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<!-- generated by issue reporter --
For verification: sticky scroll, switch to high-contrast and scroll down the file. should see a border on the bottom of the sticky scroll widget
I see it in dark theme but not light high contrast: !

Discussion:
} .monaco-editor.hc-black .sticky-widget, <del> .monaco-editor.hc-white .sticky-widget { </del> <ins> .monaco-editor.hc-light .sticky-widget { </ins> border-bottom: 1px solid var(--vscode-contrastBorder); }
Change:
Ref Unchecked and unfocused checkboxes in the Settings editor currently do not have much contrast between the checkbox background colour and the checkbox border colour for both Light+ v2 and Dark+ v2 themes. !

Discussion:
"button.secondaryForeground": "#cccccc", "button.secondaryHoverBackground": "#ffffff15", "checkbox.background": "#313131", <del> "checkbox.border": "#ffffff15", </del> <ins> "checkbox.border": "#ffffff1f", </ins> "debugToolBar.background": "#181818", "descriptionForeground": "#8b949e", "diffEditor.insertedLineBackground": "#23863633",

"diffEditor.removedLineBackground": "#da363333", "diffEditor.removedTextBackground": "#da36334d", "dropdown.background": "#313131", <del> "dropdown.border": "#ffffff17", </del> <ins> "dropdown.border": "#ffffff1f", </ins> "dropdown.foreground": "#cccccc", "dropdown.listBackground": "#313131", "editor.background": "#1f1f1f",

"foreground": "#cccccc", "icon.foreground": "#cccccc", "input.background": "#ffffff0f", <del> "input.border": "#ffffff17", </del> <ins> "input.border": "#ffffff1f", </ins> "input.foreground": "#cccccc", "input.placeholderForeground": "#ffffff79", "inputOption.activeBackground": "#2489db82",

"scrollbarSlider.background": "#6e768133", "scrollbarSlider.hoverBackground": "#6e768145", "settings.dropdownBackground": "#313131", <del> "settings.dropdownBorder": "#ffffff17", </del> <ins> "settings.dropdownBorder": "#ffffff1f", </ins> "settings.headerForeground": "#ffffff", "settings.modifiedItemIndicator": "#bb800966", "sideBar.background": "#181818",

"button.secondaryForeground": "#3b3b3b", "button.secondaryHoverBackground": "#00000034", "checkbox.background": "#f8f8f8", <del> "checkbox.border": "#0000001a", </del> <ins> "checkbox.border": "#CECECE", </ins> "descriptionForeground": "#3b3b3b", "diffEditor.insertedLineBackground": "#23863633", "diffEditor.insertedTextBackground": "#2386364d", "diffEditor.removedLineBackground": "#da363333", "diffEditor.removedTextBackground": "#da36334d", "dropdown.background": "#ffffff", <del> "dropdown.border": "#0000001a", </del> <ins> "dropdown.border": "#CECECE", </ins> "dropdown.foreground": "#3b3b3b", "dropdown.listBackground": "#ffffff", "editor.background": "#ffffff",

"foreground": "#3b3b3b", "icon.foreground": "#3b3b3b", "input.background": "#ffffff", <del> "input.border": "#0000001a", </del> <ins> "input.border": "#CECECE", </ins> "input.foreground": "#3b3b3b", "input.placeholderForeground": "#00000079", "inputOption.activeBackground": "#005fb841",

"scrollbarSlider.hoverBackground": "#6e768145", "searchEditor.textInputBorder": "#CECECE", "settings.dropdownBackground": "#ffffff", <del> "settings.dropdownBorder": "#0000001a", </del> <ins> "settings.dropdownBorder": "#CECECE", </ins> "settings.headerForeground": "#1f1f1f", "settings.modifiedItemIndicator": "#bb800966", "settings.numberInputBorder": "#CECECE",
Change:
<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.

Discussion:
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]; } }
Change:
Steps: start to drag an item from the tree see how it does not have any background shows its this commit range: !
Works on Linux, but I can reproduce on Windows

Discussion:
const dragImage = $('.monaco-drag-image'); dragImage.textContent = label; <del> document.body.appendChild(dragImage); </del> <ins> const getDragImageContainer = (e: HTMLElement | null) => { while (e && !e.classList.contains('monaco-workbench')) { e = e.parentElement; } return e || document.body; }; const container = getDragImageContainer(this.domNode); container.appendChild(dragImage); </ins> event.dataTransfer.setDragImage(dragImage, -10, -10); <del> setTimeout(() => document.body.removeChild(dragImage), 0); </del> <ins> setTimeout(() => container.removeChild(dragImage), 0); </ins> } this.domNode.classList.add('dragging');
Change:
It looks like the move of the fibonacci numbers to a web worker fails on In the console I see: The code points to this: <img width="814" alt="image" src="https://user-"I found this only because the web perf bot no longer finishes, waiting for the startup timings console log message that we do here: I cannot step over this method, it seems to throw.
also happens in desktop
Looks like minification removes the function name and therefore it fails <img width="831" alt="Screenshot 2023-01-27 at 11 45 10" src="https://user-"
I confirm the error on Windows, for the latest Insiders and Exploration builds.
Works

Discussion:
// we use fibonacci numbers to have a performance baseline that indicates // how slow/fast THIS machine actually is. <del> const jsSrc = (function computeBaseline(this: WindowOrWorkerGlobalScope) { </del> <ins> const jsSrc = (function (this: WindowOrWorkerGlobalScope) { </ins> // the following operation took ~16ms (one frame at 64FPS) to complete on my machine. We derive performance observations // from that. We also bail if that took too long (>1s) let tooSlow = false;

}).toString(); <del> const blob = new Blob([`${jsSrc};ncomputeBaseline();`], { type: 'application/javascript' }); </del> <ins> const blob = new Blob([`(${jsSrc})();`], { type: 'application/javascript' }); </ins> const blobUrl = URL.createObjectURL(blob); const worker = createBlobWorker(blobUrl, { name: 'perfBaseline' });
Change:
I like how the sashes are now connected even for diff editor and joined editors, but this does not seem to work when the split editor is split horizontally: !
I didn't even know this was possible!

Discussion:
// Splitview widget this.splitview = this.splitviewDisposables.add(new SplitView(parent, { orientation: this.orientation })); this.splitviewDisposables.add(this.splitview.onDidSashReset(() => this.splitview?.distributeViewSizes())); <del> this.splitview.orthogonalEndSash = this._boundarySashes?.bottom; </del> <ins> if (this.orientation === Orientation.HORIZONTAL) { this.splitview.orthogonalEndSash = this._boundarySashes?.bottom; } else { this.splitview.orthogonalStartSash = this._boundarySashes?.left; this.splitview.orthogonalEndSash = this._boundarySashes?.right; } </ins> // Figure out sizing let leftSizing: number | Sizing = Sizing.Distribute;
Change:
This is a valid bug. To repro: Open an empty window Open the explorer view. Make sure you have welcome page opened in the editor. Click on link the empty view Select a folder to open You will see above error trace in the console
No Folder Opened view () is removed when folder is opened. When removed this view is disposed. Following listener is getting invoked even after view is disposed It is because, view is being removed/disposed by listening to the same event It seems, once an event is fired all its listeners are invoked even if one of the listeners is disposed in the middle. This is causing the listener to be called even if it is disposed. Assigning to you also because it is related welcome view.
What link should I click? !
You have to make sure welcome page is opened <img width="955" alt="image" src="https://user-"

Discussion:
static readonly ID: string = 'workbench.explorer.emptyView'; static readonly NAME = nls.localize('noWorkspace', "No Folder Opened"); <ins> private _disposed: boolean = false; </ins> constructor( options: IViewletViewOptions,

} private refreshTitle(): void { <ins> if (this._disposed) { return; } </ins> if (this.contextService.getWorkbenchState() === WorkbenchState.WORKSPACE) { this.updateTitle(EmptyView.NAME); } else { this.updateTitle(this.title); } } <ins> override dispose(): void { this._disposed = true; super.dispose(); } </ins> }
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: 1.74.3 OS Version: linux Steps to Reproduce: a codespace on github in Web (browser), and uninstall extension if it installed. in terminal. It will be fail. (What I expect is success.) in terminal. It will be success.
<img width="762" alt="image" src="https://user-"
It works for me - I mean I can install the extension in codespace . Can you please provide a sample codespace where I can repro this?
Thanks for your reply! I going to provide 2 ways to reproduce this bug. in browser. . . It will be fail. <img width="1447" alt="image" src="https://user-"<img width="665" alt="image" src="https://user-"We can reproduce by running this , because this repo is fork from vscode. in the terminal of your computer. in your browser. . It will be fail. <img width="697" alt="image" src="https://user-"
If begins with , such as , it will be fail. If not begins with , such as , it will be success. <img width="686" alt="image" src="https://user-"
This seems to happen when you open codespace in web

Discussion:
private async getGalleryExtensions(extensions: InstallExtensionInfo[]): Promise<Map<string, IGalleryExtension>> { const galleryExtensions = new Map<string, IGalleryExtension>(); const preRelease = extensions.some(e => e.installOptions.installPreReleaseVersion); <del> const result = await this.extensionGalleryService.getExtensions(extensions.map(e => ({ ...e, preRelease })), CancellationToken.None); </del> <ins> const targetPlatform = await this.extensionManagementService.getTargetPlatform(); const result = await this.extensionGalleryService.getExtensions(extensions.map(e => ({ ...e, preRelease })), { targetPlatform }, CancellationToken.None); </ins> for (const extension of result) { galleryExtensions.set(extension.identifier.id.toLowerCase(), extension); }
Change:
<img width="960" alt="Screenshot 2023-01-31 at 15 55 04" src="https://user-"It looks like the command has the wrong description.

Discussion:
constructor() { super({ id: HideInlineCompletion.ID, <del> label: nls.localize('action.inlineSuggest.acceptNextWord', "Accept Next Word Of Inline Suggestion"), alias: 'Accept Next Word Of Inline Suggestion', </del> <ins> label: nls.localize('action.inlineSuggest.hide', "Hide Inline Suggestion"), alias: 'Hide Inline Suggestion', </ins> precondition: GhostTextController.inlineSuggestionVisible, kbOpts: { weight: 100,
Change:
Type: <bBug</bto an existing branch from . Control Side panel then shows Sync Changes button. , clicking on Sync button causes to commits from previous branch to merge into current branch VS Code version: Code 1.74.3 (, 2023-01-09T16:59:02.252Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: No Remote OS version: Linux x64 5.15.79.1-microsoft-standard-WSL2 <details<summarySystem Info</summary </details<details<summaryExtensions (13)</summaryExtensionVersion ------ laravel-blade1.1.2 jupyter-keymap1.0.0 remote-wsl0.72.0 alignment0.3.0 vscode-log-viewer0.12.2 vscode-intelephense-client1.9.4 gitlens13.2.0 cmake-tools1.13.44 cpptools1.13.9 cpptools-extension-pack1.3.0 laravel-blade1.32.0 cmake0.0.17 php-debug1.30.0 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --

Discussion:
interface ActionButtonState { readonly HEAD: Branch | undefined; <ins> readonly isCheckoutInProgress: boolean; </ins> readonly isCommitInProgress: boolean; readonly isMergeInProgress: boolean; readonly isRebaseInProgress: boolean;

readonly postCommitCommandCenter: CommitCommandsCenter) { this._state = { HEAD: undefined, <ins> isCheckoutInProgress: false, </ins> isCommitInProgress: false, isMergeInProgress: false, isRebaseInProgress: false,

l10n.t({ message: 'Publish Branch', comment: ['{Locked="Branch"}', 'Do not translate "Branch" as it is a git term'] })), arguments: [this.repository.sourceControl], }, <del> enabled: !this.state.isSyncInProgress </del> <ins> enabled: !this.state.isCheckoutInProgress && !this.state.isSyncInProgress </ins> }; }

arguments: [this.repository.sourceControl], }, description: `${icon}${behind}${ahead}`, <del> enabled: !this.state.isSyncInProgress </del> <ins> enabled: !this.state.isCheckoutInProgress && !this.state.isSyncInProgress </ins> }; } private onDidChangeOperations(): void { <ins> const isCheckoutInProgress = this.repository.operations.isRunning(OperationKind.Checkout) || this.repository.operations.isRunning(OperationKind.CheckoutTracking); </ins> const isCommitInProgress = this.repository.operations.isRunning(OperationKind.Commit) || this.repository.operations.isRunning(OperationKind.PostCommitCommand) ||

this.repository.operations.isRunning(OperationKind.Push) || this.repository.operations.isRunning(OperationKind.Pull); <del> this.state = { ...this.state, isCommitInProgress, isSyncInProgress }; </del> <ins> this.state = { ...this.state, isCheckoutInProgress, isCommitInProgress, isSyncInProgress }; </ins> } private onDidChangeSmartCommitSettings(): void {
Change:
When I run all tests, the label resets back to after all tests were run. This is very confusing. !
This was a result of a bad filter function that caused all test runs to be treated extension-triggered. The "real" test run would then never have results, or get any output. More importantly, this results in "show test output" usually showing nothing. Taking this as a candidate. Essentially the sequence is: is triggered from the UI, so we prepare TestResults for incoming data and send the TestRunRequest precursor over to the EH EH doesn't associate that request with the existing run calls from its , which gets treated as a brand new run, so we make new TestResults for that run run and states get updated... 's resolves automatically marks the UI-triggered run as complete since the runHandler returned and there are no ongoing TestRuns latest completed TestResults is now the empty one that core created and was never updated so things that use the last result, like "show test output", are empty The code path in is meant to only be taken by the new Continuous Test runs, where the request is long-lived and doesn't have a single associated set of TestResults.

Discussion:
testIds: string[]; } <del> export const isStartControllerTests = (t: ICallProfileRunHandler | IStartControllerTests): t is IStartControllerTests => 'runIn' in t; </del> <ins> export const isStartControllerTests = (t: ICallProfileRunHandler | IStartControllerTests): t is IStartControllerTests => ('runId' as keyof IStartControllerTests) in t; </ins> /** * Request from the main thread to run tests for a single controller.
Change:
Steps: configure close all editors reload window open -click of line 11 -click -click pick "Go back in navigation locations" from commands as long as you can you cannot reach back into
this is caused by

Discussion:
this.handleActiveEditorChange(activeEditorGroup, activeEditorPane); // Listen to selection changes if the editor pane <del> // is having a selection concept. We use `accumulate` // on the event to reduce the pressure on the editor // to reduce input latency. </del> <ins> // is having a selection concept. </ins> if (isEditorPaneWithSelection(activeEditorPane)) { <del> this.activeEditorListeners.add(Event.accumulate(activeEditorPane.onDidChangeSelection)(e => this.handleActiveEditorSelectionChangeEvents(activeEditorGroup, activeEditorPane, e))); </del> <ins> this.activeEditorListeners.add(activeEditorPane.onDidChangeSelection(e => this.handleActiveEditorSelectionChangeEvent(activeEditorGroup, activeEditorPane, e))); </ins> } // Context keys

this.handleActiveEditorChangeInNavigationStacks(group, editorPane); } <del> private handleActiveEditorSelectionChangeEvents(group: IEditorGroup, editorPane: IEditorPaneWithSelection, events: IEditorPaneSelectionChangeEvent[]): void { for (const event of events) { this.handleActiveEditorSelectionChangeInNavigationStacks(group, editorPane, event); } </del> <ins> private handleActiveEditorSelectionChangeEvent(group: IEditorGroup, editorPane: IEditorPaneWithSelection, event: IEditorPaneSelectionChangeEvent): void { this.handleActiveEditorSelectionChangeInNavigationStacks(group, editorPane, event); </ins> } private move(event: FileOperationEvent): void {
Change:
to the setting in the Settings editor. to the dark high contrast theme. over the list items. :bug: No visual indication appears other than the pencil and close icons showing up on the right. This problem does not occur on the light high contrast theme.

Discussion:
export const listInactiveSelectionIconForeground = registerColor('list.inactiveSelectionIconForeground', { dark: null, light: null, hcDark: null, hcLight: null }, nls.localize('listInactiveSelectionIconForeground', "List/Tree icon foreground color for the selected item when the list/tree is inactive. An active list/tree has keyboard focus, an inactive does not.")); export const listInactiveFocusBackground = registerColor('list.inactiveFocusBackground', { dark: null, light: null, hcDark: null, hcLight: null }, nls.localize('listInactiveFocusBackground', "List/Tree background color for the focused item when the list/tree is inactive. An active list/tree has keyboard focus, an inactive does not.")); export const listInactiveFocusOutline = registerColor('list.inactiveFocusOutline', { dark: null, light: null, hcDark: null, hcLight: null }, nls.localize('listInactiveFocusOutline', "List/Tree outline color for the focused item when the list/tree is inactive. An active list/tree has keyboard focus, an inactive does not.")); <del> export const listHoverBackground = registerColor('list.hoverBackground', { dark: '#2A2D2E', light: '#F0F0F0', hcDark: null, hcLight: Color.fromHex('#0F4A85').transparent(0.1) }, nls.localize('listHoverBackground', "List/Tree background when hovering over items using the mouse.")); </del> <ins> export const listHoverBackground = registerColor('list.hoverBackground', { dark: '#2A2D2E', light: '#F0F0F0', hcDark: Color.white.transparent(0.1), hcLight: Color.fromHex('#0F4A85').transparent(0.1) }, nls.localize('listHoverBackground', "List/Tree background when hovering over items using the mouse.")); </ins> export const listHoverForeground = registerColor('list.hoverForeground', { dark: null, light: null, hcDark: null, hcLight: null }, nls.localize('listHoverForeground', "List/Tree foreground when hovering over items using the mouse.")); export const listDropBackground = registerColor('list.dropBackground', { dark: '#062F4A', light: '#D6EBFF', hcDark: null, hcLight: null }, nls.localize('listDropBackground', "List/Tree drag and drop background when moving items around using the mouse.")); export const listHighlightForeground = registerColor('list.highlightForeground', { dark: '#2AAAFF', light: '#0066BF', hcDark: focusBorder, hcLight: focusBorder }, nls.localize('highlight', 'List/Tree foreground color of the match highlights when searching inside the list/tree.'));