jiebi/CodeConvo huggingface dataset:
Change:
Type: <bBug</bThe new incoming/outgoing does not not work propery. The sections cannot be expanded to show the contents. The count icon matches. VS Code version: Code 1.85.0 (Universal) (, 2023-12-06T18:18:04.614Z) OS version: Darwin x64 22.6.0 Modes: Remote OS version: Linux x64 5.15.0-91-generic Remote OS version: Linux x64 5.15.0-91-generic Remote OS version: Linux x64 5.15.0-91-generic Remote OS version: Linux x64 5.15.0-91-generic Remote OS version: Linux x64 5.15.0-91-generic Remote OS version: Linux x64 5.15.0-91-generic Remote OS version: Linux x64 5.15.0-91-generic Remote OS version: Linux x64 5.15.0-91-generic <details<summarySystem Info</summary </details<details<summaryExtensions (38)</summaryExtensionVersion ------ remotehub0.62.0 better-cpp-syntax1.17.2 better-objc-syntax0.2.0 better-objcpp-syntax0.2.0 autoconf0.2.0 jupyter-keymap1.1.2 remote-containers0.327.0 remote-ssh0.107.1 remote-ssh-edit0.86.0 remote-explorer0.4.1 remote-repositories0.40.0 remote-server1.5.0 lit-html1.11.1 githistory0.6.20 vscode-pull-request-github0.76.1 vscode-embedded-css-template-strings0.5.1 githd2.3.3 rest-client0.25.1 gitsweep1.0.0 git-tree-compare1.16.0 vscode-antlr42.4.4 hexeditor1.9.12 sqltools0.28.1 sqltools-driver-pg0.5.2 gradle-language0.2.3 inline-html0.3.9 java1.26. code-spell-checker3.0.1 intellicode-api-usage-examples0.2.8 vscodeintellicode1.2.30 vscode-gradle3.13. vscode-java-debug0.55.0 vscode-java-dependency0.23.3 vscode-java-pack0.25.15 vscode-java-test0.40.1 vscode-maven0.43.0 gitblame10.5.1 jar-viewer1.2.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Here is a screenshot: <img width="460" alt="image" src=""
I have the same issue, but it works locally, it is only broken on my remote development sessions through ssh.
When I try to toggle the incoming/outgoing dropdown I see the following in the Git log output: It seems that argument was in git v2.31.0 On my remote dev machine I have so that tracks.

Discussion:
const args = ['log', `--format=${COMMIT_FORMAT}`, '-z']; if (options?.shortStats) { <del> args.push('--shortstat', '--diff-merges=first-parent'); </del> <ins> args.push('--shortstat'); if (this._git.compareGitVersionTo('2.31') !== -1) { args.push('--diff-merges=first-parent'); } </ins> } if (options?.reverse) {
Change:
We'd been having a bug report where some of our dialogs in our extension were not showing the buttons correctly. Digging through, we realized this was a regression caused by Our extension was mistakenly setting isCloseAffordance on all buttons to be displayed. Before the above PR, all the buttons would work, and it would just be the last one passed that would be set as the cancel button. However after that PR, due to any buttons that had isCloseAffordance set to true wouldn't be to the buttons list, and instead would just overwrite the single cancel button. I'd be nice if we could get some release notes about this regression, and maybe a change to spit out a warning in the debugger if multiple buttons with isCloseAffordance are to a dialog. Currently its very hard to debug if this is occurring, because the buttons just don't show up, and its not clear why.

Discussion:
} const commands: { title: string; isCloseAffordance: boolean; handle: number }[] = []; <ins> let hasCloseAffordance = false; </ins> for (let handle = 0; handle < items.length; handle++) { const command = items[handle];

} else if (typeof command === 'object') { const { title, isCloseAffordance } = command; commands.push({ title, isCloseAffordance: !!isCloseAffordance, handle }); <ins> if (isCloseAffordance) { if (hasCloseAffordance) { this._logService.warn(`[${extension.identifier}] Only one message item can have 'isCloseAffordance':`, command); } else { hasCloseAffordance = true; } } </ins> } else { <del> this._logService.warn('Invalid message item:', command); </del> <ins> this._logService.warn(`[${extension.identifier}] Invalid message item:`, command); </ins> } }
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. --VS Code has always been able to clear Terminal only by binding shortcuts or shortcut menus. When debugging server logs, we will often need to clear the logs, and Chrome DevTools provides a separate button for that as well. I can submit a PR for this. ! !
This is actually already a feature but recently regressed. Clear Terminal is in the overflow menu, and in the next release you'll be able to right click to show it in the panel again: !

Discussion:
title: localize('workbench.action.terminal.clearLong', "Clear Terminal"), icon: Codicon.clearAll }, <del> group: 'execute', </del> <ins> group: 'navigation', </ins> order: 4, when: ContextKeyExpr.equals('view', TERMINAL_VIEW_ID), isHiddenByDefault: true

title: localize('workbench.action.terminal.runActiveFile', "Run Active File"), icon: Codicon.run }, <del> group: 'execute', </del> <ins> group: 'navigation', </ins> order: 5, when: ContextKeyExpr.equals('view', TERMINAL_VIEW_ID), isHiddenByDefault: true

title: localize('workbench.action.terminal.runSelectedText', "Run Selected Text"), icon: Codicon.selection }, <del> group: 'execute', </del> <ins> group: 'navigation', </ins> order: 6, when: ContextKeyExpr.equals('view', TERMINAL_VIEW_ID), isHiddenByDefault: true
Change:
I am trying to a file in the one root folder and into another root folder and nothing happens anymore. Is this known? I am using multi-root folder setup. !
I can replicate this issue in VS Code 1.85.1. Cannot copy-paste with both remote folders over SSH as well as local folders. Tried both drag-drop as well as and .

Discussion:
const previouslyCutItems = this.cutItems; this.cutItems = cut ? items : undefined; await this.clipboardService.writeResources(items.map(s => s.resource)); <del> if (items.length === 1) { await this.clipboardService.writeText(items[0].name); } </del> this.view?.itemsCopied(items, cut, previouslyCutItems); }

if (!this.hasFocus() || this.readonlyContext.get()) { return; } <del> await this.commandService.executeCommand('filesExplorer.paste', event.clipboardData?.files); </del> <ins> if (event.clipboardData?.files?.length) { await this.commandService.executeCommand('filesExplorer.paste', event.clipboardData?.files); } </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/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.85.0 x64 OS Version: Steps to Reproduce: a new floating window with (or any of the other ones) a few split editors in the main view and the floating view a split in floating window the floating view, execute floating window editor size doesn't change, it happens in the main one
Good catch, these commands should not be available in floating windows.

Discussion:
super({ id: 'workbench.action.increaseViewSize', title: { value: localize('increaseViewSize', "Increase Current View Size"), original: 'Increase Current View Size' }, <del> f1: true </del> <ins> f1: true, precondition: IsAuxiliaryWindowFocusedContext.toNegated() </ins> }); }

super({ id: 'workbench.action.increaseViewWidth', title: { value: localize('increaseEditorWidth', "Increase Editor Width"), original: 'Increase Editor Width' }, <del> f1: true </del> <ins> f1: true, precondition: IsAuxiliaryWindowFocusedContext.toNegated() </ins> }); }

super({ id: 'workbench.action.increaseViewHeight', title: { value: localize('increaseEditorHeight', "Increase Editor Height"), original: 'Increase Editor Height' }, <del> f1: true </del> <ins> f1: true, precondition: IsAuxiliaryWindowFocusedContext.toNegated() </ins> }); }

super({ id: 'workbench.action.decreaseViewSize', title: { value: localize('decreaseViewSize', "Decrease Current View Size"), original: 'Decrease Current View Size' }, <del> f1: true </del> <ins> f1: true, precondition: IsAuxiliaryWindowFocusedContext.toNegated() </ins> }); }

super({ id: 'workbench.action.decreaseViewWidth', title: { value: localize('decreaseEditorWidth', "Decrease Editor Width"), original: 'Decrease Editor Width' }, <del> f1: true </del> <ins> f1: true, precondition: IsAuxiliaryWindowFocusedContext.toNegated() </ins> }); }

super({ id: 'workbench.action.decreaseViewHeight', title: { value: localize('decreaseEditorHeight', "Decrease Editor Height"), original: 'Decrease Editor Height' }, <del> f1: true </del> <ins> f1: true, precondition: IsAuxiliaryWindowFocusedContext.toNegated() </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. --<!-- 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. --Unused import from from in
bruh

Discussion:
*  Licensed under the MIT License. See License.txt in the project root for license information. *--------------------------------------------------------------------------------------------*/ <del> import { Uri, Event, Disposable, ProviderResult, Command, CancellationToken, ThemeIcon } from 'vscode'; </del> <ins> import { Uri, Event, Disposable, ProviderResult, Command, CancellationToken } from 'vscode'; </ins> export { ProviderResult } from 'vscode'; export interface Git {
Change:
Followup from I wouldn't call the color . For the user it is not an editor, just a view. Either or

Discussion:
"--vscode-notificationsErrorIcon-foreground", "--vscode-notificationsInfoIcon-foreground", "--vscode-notificationsWarningIcon-foreground", <del> "--vscode-outputEditor-background", "--vscode-outputEditorStickyScroll-background", </del> <ins> "--vscode-outputView-background", "--vscode-outputViewStickyScroll-background", </ins> "--vscode-panel-background", "--vscode-panel-border", "--vscode-panel-dropBorder",

// < --- Output Editor --> <del> const OUTPUT_EDITOR_BACKGROUND = registerColor('outputEditor.background', { </del> <ins> const OUTPUT_VIEW_BACKGROUND = registerColor('outputView.background', { </ins> dark: null, light: null, hcDark: null, hcLight: null <del> }, localize('outputEditorBackground', "Output editor background color.")); </del> <ins> }, localize('outputViewBackground', "Output view background color.")); </ins> <del> registerColor('outputEditorStickyScroll.background', { dark: OUTPUT_EDITOR_BACKGROUND, light: OUTPUT_EDITOR_BACKGROUND, hcDark: OUTPUT_EDITOR_BACKGROUND, hcLight: OUTPUT_EDITOR_BACKGROUND }, localize('outputEditorStickyScrollBackground', "Output editor sticky scroll background color.")); </del> <ins> registerColor('outputViewStickyScroll.background', { dark: OUTPUT_VIEW_BACKGROUND, light: OUTPUT_VIEW_BACKGROUND, hcDark: OUTPUT_VIEW_BACKGROUND, hcLight: OUTPUT_VIEW_BACKGROUND }, localize('outputViewStickyScrollBackground', "Output view sticky scroll background color.")); </ins> // < --- Banner --- >

.monaco-workbench .part.panel > .content .pane-body.output-view .monaco-editor, .monaco-workbench .part.panel > .content .pane-body.output-view .monaco-editor .margin, .monaco-workbench .part.panel > .content .pane-body.output-view .monaco-editor .monaco-editor-background { <del> background-color: var(--vscode-outputEditor-background); </del> <ins> background-color: var(--vscode-outputView-background); </ins> } .monaco-workbench .part.panel > .content .pane-body.output-view .sticky-widget { <del> background-color: var(--vscode-outputEditorStickyScroll-background, var(--vscode-panel-background)); </del> <ins> background-color: var(--vscode-outputViewStickyScroll-background, var(--vscode-panel-background)); </ins> }
Change:
! It's those 3 options that don't work, until there are multiple shells running. Once you have two or more shells, those options start working, as below I'm showing me renaming successfully the 2nd shell: ! Originally posted by in
I think related to this
PR fixing it
moving the issue with to this issue as it's not a recent regression

Discussion:
}, delay); }; <ins> let isMouseDown = false; const mouseDownEmitter = dom.addDisposableListener(htmlElement, dom.EventType.MOUSE_DOWN, () => { isMouseDown = true; hideHover(true, true); }, true); const mouseUpEmitter = dom.addDisposableListener(htmlElement, dom.EventType.MOUSE_UP, () => { isMouseDown = false; }, true); const mouseLeaveEmitter = dom.addDisposableListener(htmlElement, dom.EventType.MOUSE_LEAVE, (e: MouseEvent) => { isMouseDown = false; hideHover(false, (<any>e).fromElement === htmlElement); }, true); </ins> const onMouseOver = () => { if (hoverPreparation) { return;

const toDispose: DisposableStore = new DisposableStore(); <del> const onMouseLeave = (e: MouseEvent) => hideHover(false, (<any>e).fromElement === htmlElement); toDispose.add(dom.addDisposableListener(htmlElement, dom.EventType.MOUSE_LEAVE, onMouseLeave, true)); const onMouseDown = () => hideHover(true, true); toDispose.add(dom.addDisposableListener(htmlElement, dom.EventType.MOUSE_DOWN, onMouseDown, true)); </del> const target: IHoverDelegateTarget = { targetElements: [htmlElement], dispose: () => { }

const mouseOverDomEmitter = dom.addDisposableListener(htmlElement, dom.EventType.MOUSE_OVER, onMouseOver, true); const onFocus = () => { <del> if (hoverPreparation) { </del> <ins> if (isMouseDown || hoverPreparation) { </ins> return; } const target: IHoverDelegateTarget = {

}, dispose: () => { mouseOverDomEmitter.dispose(); <ins> mouseLeaveEmitter.dispose(); mouseDownEmitter.dispose(); mouseUpEmitter.dispose(); </ins> focusDomEmitter.dispose(); hideHover(true, true); }
Change:
The examples in the and have a typo. The is missing as object property separator: should be
The API reference is generated from the VS Code product Moving to the VS Code product repo. After these typos are fixed there, the API reference will be updated next release at the beginning of February
Thanks for pointing out the typos! As mentioned above, the API reference will be updated when the 1.86 release goes out early February

Discussion:
/** * A set of file filters that are used by the dialog. Each entry is a human-readable label, <del> * like "TypeScript", and an array of extensions, e.g. </del> <ins> * like "TypeScript", and an array of extensions, for example: </ins> * ```ts * { <del> * 	'Images': ['png', 'jpg'] </del> <ins> * 	'Images': ['png', 'jpg'], </ins> * 	'TypeScript': ['ts', 'tsx'] * } * ```
Change:
I think we used to indent inline chat to the indentation level of the line: ! Steps: have an indented line press enter to be on an empty line (still indented) press to bring up inline chat

Discussion:
widgetPosition = this._editor.getSelection().getStartPosition().delta(-1); } <del> let needsMargin = false; </del> if (initialRender) { this._zone.value.setContainerMargins(); }

if (this._activeSession) { this._zone.value.updateBackgroundColor(widgetPosition, this._activeSession.wholeRange.value); } <del> if (this._strategy) { needsMargin = this._strategy.needsMargin(); } </del> if (!this._zone.value.position) { <del> this._zone.value.setWidgetMargins(widgetPosition, !needsMargin ? 0 : undefined); </del> <ins> this._zone.value.setWidgetMargins(widgetPosition); </ins> this._zone.value.show(widgetPosition); } else { this._zone.value.updatePositionAndHeight(widgetPosition);

abstract renderChanges(response: ReplyResponse): Promise<Position | undefined>; abstract hasFocus(): boolean; <del> abstract needsMargin(): boolean; </del> } export class PreviewStrategy extends EditModeStrategy {

hasFocus(): boolean { return this._zone.widget.hasFocus(); } <del> needsMargin(): boolean { return true; } </del> }

this._zone.widget.updateStatus(message); } <del> override needsMargin(): boolean { return true; } </del> private async _updateDiffZones() { const diff = await this._editorWorkerService.computeDiff(this._session.textModel0.uri, this._session.textModelN.uri, { ignoreTrimWhitespace: false, maxComputationTimeMs: 5000, computeMoves: false }, 'advanced'); if (!diff || diff.changes.length === 0) {

this._zone.widget.updateStatus(message); } <del> override needsMargin(): boolean { return true; } </del> hasFocus(): boolean { return this._zone.widget.hasFocus(); }

this.container.style.marginLeft = `${marginWithoutIndentation}px`; } <del> setWidgetMargins(position: Position, indentationWidth?: number): void { if (indentationWidth === undefined) { indentationWidth = this._calculateIndentationWidth(position); } </del> <ins> setWidgetMargins(position: Position): void { const indentationWidth = this._calculateIndentationWidth(position); </ins> if (this._indentationWidth === indentationWidth) { return; }
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.85.1 OS Version: Alpine 3.19 Steps to Reproduce: More info and fix in new version :

Discussion:
"@vscode/policy-watcher": "^1.1.4", "@vscode/proxy-agent": "^0.18.2", "@vscode/ripgrep": "^1.15.9", <del> "@vscode/spdlog": "^0.13.12", </del> <ins> "@vscode/spdlog": "^0.14.0", </ins> "@vscode/sqlite3": "5.1.6-vscode", "@vscode/sudo-prompt": "9.3.1", "@vscode/vscode-languagedetection": "1.0.21",

"@vscode/iconv-lite-umd": "0.7.0", "@vscode/proxy-agent": "^0.18.2", "@vscode/ripgrep": "^1.15.9", <del> "@vscode/spdlog": "^0.13.12", </del> <ins> "@vscode/spdlog": "^0.14.0", </ins> "@vscode/vscode-languagedetection": "1.0.21", "@vscode/windows-process-tree": "^0.5.0", "@vscode/windows-registry": "^1.1.0",

proxy-from-env "^1.1.0" yauzl "^2.9.2" <del> "@vscode/spdlog@^0.13.12": version "0.13.12" resolved "https://registry.yarnpkg.com/@vscode/spdlog/-/spdlog-0.13.12.tgz#8b8e3308468fd7d613c350ecd7fcfaa27064960a" integrity sha512-8Qw8VwBzFkH6AWVKh+ULeVDff0lwTh/PkEKUOwRpyuu7Mr7W2zQoc+oAaGmTWKb1NPmvVeXmo+qF9X+jXuBCOg== </del> <ins> "@vscode/spdlog@^0.14.0": version "0.14.0" resolved "https://registry.yarnpkg.com/@vscode/spdlog/-/spdlog-0.14.0.tgz#3cdf589ca59b9ce792ef58b5f773e29a732a360f" integrity sha512-mpblZa3v6AGEJC1qTwIkpgTc6NItdiiuTxufGxr6XD14srXCvVAUXFIYNqszxC6RY57qDQMX1d9Wd4/oZDxuUQ== </ins> dependencies: bindings "^1.5.0" mkdirp "^1.0.4"
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: 1.85.1 OS Version: macOS Sonoma 14.2.1 Steps to Reproduce: a python file or other file with a debugging extension installed Debug view and see the welcome view showing Run and Debug Actions. a diff Editor for the same file debug view now shows an Expected: Debug view shows the same welcome state as when not in diff view as this language has debug extension installed. <img width="694" alt="image" src=""Actual: !

Discussion:
import { WorkbenchStateContext } from 'vs/workbench/common/contextkeys'; import { OpenFolderAction, OpenFileAction, OpenFileFolderAction } from 'vs/workbench/browser/actions/workspaceActions'; import { isMacintosh, isWeb } from 'vs/base/common/platform'; <del> import { isCodeEditor } from 'vs/editor/browser/editorBrowser'; </del> <ins> import { isCodeEditor, isDiffEditor } from 'vs/editor/browser/editorBrowser'; </ins> import { IStorageService, StorageScope, StorageTarget } from 'vs/platform/storage/common/storage'; import { ITelemetryService } from 'vs/platform/telemetry/common/telemetry'; import { DisposableStore } from 'vs/base/common/lifecycle';

this.debugStartLanguageContext.set(lastSetLanguage); const setContextKey = () => { <del> const editorControl = this.editorService.activeTextEditorControl; </del> <ins> let editorControl = this.editorService.activeTextEditorControl; if (isDiffEditor(editorControl)) { editorControl = editorControl.getModifiedEditor(); } </ins> if (isCodeEditor(editorControl)) { const model = editorControl.getModel(); const language = model ? model.getLanguageId() : undefined;

this._register(editorService.onDidActiveEditorChange(() => { disposables.clear(); <del> const editorControl = this.editorService.activeTextEditorControl; </del> <ins> let editorControl = this.editorService.activeTextEditorControl; if (isDiffEditor(editorControl)) { editorControl = editorControl.getModifiedEditor(); } </ins> if (isCodeEditor(editorControl)) { disposables.add(editorControl.onDidChangeModelLanguage(setContextKey)); }