jiebi/CodeConvo huggingface dataset:
Change:
On Windows: something with a rich hover in a tree view, like an extension or an item in the activity bar +tab off the window back to VS Code the hover is still there and stays around around until you hover something else with a rich hover, or click on it and hit escape

Discussion:
} }); <ins> // Hide when the window loses focus this._register(dom.addDisposableListener(window, 'blur', () => this.dispose())); </ins> const rowElement = $('div.hover-row.markdown-hover'); const contentsElement = $('div.hover-contents'); if (typeof options.content === 'string') {
Change:
Saw while playing around in code OSS <img width="1251" alt="image" src="https://user-"
I also just ran into this. Here is the complete stack trace:
What are some verification steps for this issue?
I'll mark this as verified just because I was seeing this multiple times daily and am not seeing it anymore.

Discussion:
private readonly widget = this._register(this.instantiationService.createInstance(InlineSuggestionHintsContentWidget, this.editor, true)); private sessionPosition: Position | undefined = undefined; <ins> private isDisposed = false; </ins> constructor( private readonly editor: ICodeEditor,

this.update(); } <ins> override dispose(): void { this.isDisposed = true; super.dispose(); } </ins> private update(): void { <ins> if (this.isDisposed) { return; } </ins> const options = this.editor.getOption(EditorOption.inlineSuggest); if (options.showToolbar !== 'always' || !this.model.ghostText) { this.widget.update(null, 0, undefined, []);
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. --Version: 1.75.0 (Universal) Commit: Date: 2023-02-01T15:24:42.903Z Electron: 19.1.9 Chromium: 102.0.5005.194 16.14.2 V8: 10.2.154.23-electron.0 OS: Darwin arm64 22.3.0 Sandboxed: No Steps to Reproduce: SCM tab at the left side at the border of the Commit & Push combo box The inconsistency is more visible in non-default themes like "Bearded Theme Monokai Reversed" <img width="717" alt="vscodescmcp1" src="https://user-"but also slightly in the "Default Dark+ Experimental" for example <img width="656" alt="vscodescmcp2" src="https://user-"

Discussion:
} .monaco-button-dropdown > .monaco-button.monaco-dropdown-button { <ins> border: 1px solid var(--vscode-button-border, transparent); </ins> border-left-width: 0 !important; border-radius: 0 2px 2px 0; }
Change:
"Running Extensions" tab extensions with uncaught errors 's a barely visible piece of a "report issue" button ! !
I could use some help here. Change it such that the action bar is always shown: The "Report Issue" action label is cut short to be 22x22px : <img width="268" alt="image" src="https://user-"
Looks like the default styling of the action items is icon only (codicon) and that comes with a fixed width... I will look into a fix
I got the message to show in VS Code stable, but I couldn't get it to show in insiders. Maybe I'm holding it wrong though so I will leave someone else to verify.
<!-- 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!
Nope. The button "Report Issue" is still hidden in .
Well, there was an attempt... While fixing I just patched the aforementioned lines but what kind of error does your extension throw to be reported there? Can you share your sample?
In :

Discussion:
data.actionbar.clear(); const slowExtensionAction = this._createSlowExtensionAction(element); if (slowExtensionAction) { <del> data.actionbar.push(slowExtensionAction, { icon: true, label: true }); </del> <ins> data.actionbar.push(slowExtensionAction, { icon: false, label: true }); </ins> } if (isNonEmptyArray(element.status.runtimeErrors)) { const reportExtensionIssueAction = this._createReportExtensionIssueAction(element); if (reportExtensionIssueAction) { <del> data.actionbar.push(reportExtensionIssueAction, { icon: true, label: true }); </del> <ins> data.actionbar.push(reportExtensionIssueAction, { icon: false, label: true }); </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.75.0 (Universal) OS Version: macOS 13.2 About Window Contents: Steps to Reproduce: new v2 themes. a rendered HTML file with Code segments in it (e.g. the Releases notes for 1.75.0) markdown segments have a poor contrast compared to the other text. The contrast was a lot better in the old dark/light themes. <img width="905" alt="dark mode" src="https://user-"<img width="899" alt="light mode" src="https://user-"
I wanted to report the exact same issue

Discussion:
"textCodeBlock.background": "#6e768166", "textLink.activeForeground": "#40A6FF", "textLink.foreground": "#40A6FF", <del> "textPreformat.foreground": "#8b949e", </del> <ins> "textPreformat.foreground": "#f85149", </ins> "textSeparator.foreground": "#21262d", "titleBar.activeBackground": "#181818", "titleBar.activeForeground": "#ffffffc5",

"textCodeBlock.background": "#6e768166", "textLink.activeForeground": "#005FB8", "textLink.foreground": "#005FB8", <del> "textPreformat.foreground": "#8b949e", </del> "textSeparator.foreground": "#21262d", "titleBar.activeBackground": "#f8f8f8", "titleBar.activeForeground": "#1e1e1e",
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 <!-- 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.75.0 OS Version: win 11 Steps to Reproduce: -analyzer inlay hints' padding look weird. The inlay type hint for has no round padding on right side, while the type hint looks normal. !
I think it might have something to do with type hint being ctrl-clickable. The non-clickable types like is fine. Also, for other languages that does not support ctrl-click on inlay hints, the rendering is also fine.
Any update for this issue?
I can reproduce, but only with Rust Analyzer. This issue is that it returns a label part that's empty. When rending we add the padding/border to that element but because its empty, it never gets rendered <img width="560" alt="Screenshot 2023-12-04 at 12 54 56" src=""

Discussion:
if (typeof hint.label === 'string') { result.label = hint.label; } else { <del> result.label = hint.label.map(part => { const result: languages.InlayHintLabelPart = { label: part.value }; result.tooltip = typeConvert.MarkdownString.fromStrict(part.tooltip); </del> <ins> const parts: languages.InlayHintLabelPart[] = []; result.label = parts; for (const part of hint.label) { if (!part.value) { console.warn('INVALID inlay hint, empty label part', this._extension.identifier.value); continue; } const part2: languages.InlayHintLabelPart = { label: part.value, tooltip: typeConvert.MarkdownString.fromStrict(part.tooltip) }; </ins> if (Location.isLocation(part.location)) { <del> result.location = typeConvert.location.from(part.location); </del> <ins> part2.location = typeConvert.location.from(part.location); </ins> } if (part.command) { <del> result.command = this._commands.toInternal(part.command, disposables); </del> <ins> part2.command = this._commands.toInternal(part.command, disposables); </ins> } <del> return result; }); </del> <ins> parts.push(part2); } </ins> } return result; }
Change:
Type: <bBug</bIn addition to , , these elements are also hard to see in the Light+ V2 theme. [ ] Active (focused) workspace search results on methods: ! [x] Fixed ! ! VS Code version: Code - Insiders 1.76.0-insider (, 2023-02-06T05:24:21.999Z) OS version: Linux x64 5.15.0-58-generic Modes: Sandboxed: Yes
do you know what the notebook output token would be? I don't think I changed anything specific to notebooks in these new themes.
I checked it with the webview developer tool and it was , so I think it was fixed in
Perfect, thanks for checking. Feel free to close if it looks all good in the next Insiders update.
as pointed out we are using terminal colors.
Even worse for unsued python imports !
The variable for the active workspace search results is , and its opacity or saturation should be reduced to something like . (The current value is .)
Yep, this ended up just being a bad color assignment. Should be fixed now.

Discussion:
"dropdown.foreground": "#3b3b3b", "dropdown.listBackground": "#ffffff", "editor.background": "#ffffff", <del> "editor.findMatchBackground": "#9e6a03", </del> "editor.foreground": "#3b3b3b", "editor.inactiveSelectionBackground": "#E5EBF1", "editor.selectionHighlightBackground": "#ADD6FF80",
Change:
Type: <bBug</bOkay this is not actually an error but... I was working with a video file and it's name is ".ogg" is a video and audio file format/extension. In the explorer's tab the VS Code app says its an audio file, but it is not. The working of the file is proper in the browser but when you try to open it from VS Code itself it shows an error as "An error occurred while loading the audio file. Open file using VS Code standard text/binary editor?". According to me the app VS Code is not able to distinguish between if the file is an audio file of a video one. Lookng forward to this conversation, and hoping it gets fixed in the next VS Code update. Thank You in advance. Vishnu Soni VS Code version: Code 1.75.0 (, 2023-02-01T15:23:45.584Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (1)</summaryExtensionVersion ------ LiveServer5.7.9 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Although is a general container file format, I think is now recommended for audio content (or the more explicit ). If you want though, you can configure so that opens with the video preview instead of the audio one:
But what if want it to open both (audio and video) simultaneously
Reply

Discussion:
- `.mp3` - `.wav` <del> - `.ogg` </del> <ins> - `.ogg`, `.oga` </ins> ### Supported video formats <del> - `.mp4` (does not support `aac` audio track) </del> <ins> - `.mp4` (does not support `aac` audio tracks) </ins> - `.webm` (vp8 only)

"priority": "builtin", "selector": [ { <del> "filenamePattern": "*.{mp3,wav,ogg}" </del> <ins> "filenamePattern": "*.{mp3,wav,ogg,oga}" </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.75.0 OS Version: Windows 10 Browser: Firefox 109.0.1 Commit: Date: 2023-02-01T15:20:55.110Z Steps to Reproduce: in Firefox Extensions (Ctrl+Shift+X) an extension to display details Additional Details: Webviews do not display in Firefox version 109.0.1. There are several errors that appear in the browser's console. Here's a copy of my logs: Additionally, each time a webview is opened, the following warning appears in the console: This seems to impact all webviews. The easiest place to see the bug is in the extensions interface. Here I have tried to view details about an extension, but the webview that displays those details does not load: Extension details in Firefox 109.0.1 <img width="1792" alt="Screen Shot 2023-02-06 at 4 43 30 PM" src="https://user-"Expected behavior (Google Chrome) <img width="1792" alt="Screen Shot 2023-02-06 at 4 47 08 PM" src="https://user-"
This also affects the markdown file preview, and started Feb 3rd.

Discussion:
</head> <body style="margin: 0; overflow: hidden; width: 100%; height: 100%" role="document"> <ins> <!-- TODO: Remove additional script tag once Firefox is fixed https://bugzilla.mozilla.org/show_bug.cgi?id=1737882 --> <script></script> </ins> <script async type="module"> // @ts-check /// <reference lib="dom" />
Change:
Maybe this already exists, but it would be good if <kbdctrl</kbdrendered this in markdown: <img width="35" alt="image" src="https://user-"We could then add nicely styled keybindings to various hovers: <img width="125" alt="image" src="https://user-"cc

Discussion:
import { Emitter } from 'vs/base/common/event'; import { IMarkdownString, MarkdownStringTrustedOptions } from 'vs/base/common/htmlContent'; import { DisposableStore, IDisposable } from 'vs/base/common/lifecycle'; <ins> import 'vs/css!./renderedMarkdown'; </ins> import { applyFontInfo } from 'vs/editor/browser/config/domFontInfo'; import { ICodeEditor } from 'vs/editor/browser/editorBrowser'; import { EditorOption } from 'vs/editor/common/config/editorOptions';

const disposables = new DisposableStore(); const rendered = disposables.add(renderMarkdown(markdown, { ...this._getRenderOptions(markdown, disposables), ...options }, markedOptions)); <ins> rendered.element.classList.add('rendered-markdown'); </ins> return { element: rendered.element, dispose: () => disposables.dispose()

<ins> /*--------------------------------------------------------------------------------------------- *  Copyright (c) Microsoft Corporation. All rights reserved. *  Licensed under the MIT License. See License.txt in the project root for license information. *--------------------------------------------------------------------------------------------*/ .monaco-editor .rendered-markdown kbd { background-color: var(--vscode-keybindingLabel-background); color: var(--vscode-keybindingLabel-foreground); border-style: solid; border-width: 1px; border-radius: 3px; border-color: var(--vscode-keybindingLabel-border); border-bottom-color: var(--vscode-keybindingLabel-bottomBorder); box-shadow: inset 0 -1px 0 var(--vscode-widget-shadow); vertical-align: middle; padding: 1px 3px; } </ins>

<meta charset="UTF-8"> <meta http-equiv="Content-Security-Policy" <del> content="default-src 'none'; script-src 'sha256-RaCvj6SRgHm+2C3LKzSAamDwa3Bp4u4iQ1Y2Sm+97tE=' 'self'; frame-src 'self'; style-src 'unsafe-inline';"> </del> <ins> content="default-src 'none'; script-src 'sha256-f/XuzcTyXb1X6po1otWlqfEUBjHOsprrTOZknXfbS9I=' 'self'; frame-src 'self'; style-src 'unsafe-inline';"> </ins> <!-- Disable pinch zooming --> <meta name="viewport"

} kbd { <del> color: var(--vscode-editor-foreground); </del> <ins> background-color: var(--vscode-keybindingLabel-background); color: var(--vscode-keybindingLabel-foreground); border-style: solid; border-width: 1px; </ins> border-radius: 3px; <ins> border-color: var(--vscode-keybindingLabel-border); border-bottom-color: var(--vscode-keybindingLabel-bottomBorder); box-shadow: inset 0 -1px 0 var(--vscode-widget-shadow); </ins> vertical-align: middle; padding: 1px 3px; <del> background-color: hsla(0,0%,50%,.17); border: 1px solid rgba(71,71,71,.4); border-bottom-color: rgba(88,88,88,.4); box-shadow: inset 0 -1px 0 rgba(88,88,88,.4); } .vscode-light kbd { background-color: hsla(0,0%,87%,.5); border: 1px solid hsla(0,0%,80%,.7); border-bottom-color: hsla(0,0%,73%,.7); box-shadow: inset 0 -1px 0 hsla(0,0%,73%,.7); </del> } ::-webkit-scrollbar {
Change:
Type: <bBug</bAfter updating to the latest VS Code version, I noticed two issues in the jupyter notebook: a) in the output cell, both the content and the text "Outputs are collapsed" overlap. This text disappears once I collapse the output and show it again. ! b) in the code cell, if I'm writing something and then scroll up/down, the content of this cell is no longer visible Thanks VS Code version: Code 1.75.0 (, 2023-02-01T15:23:45.584Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (9)</summaryExtensionVersion ------ rainbow-csv3.5.0 isort2022.8.0 python2023.2.0 vscode-pylance2023.2.10 jupyter2023.1. jupyter-keymap1.0.0 jupyter-renderers1.0.14 vscode-jupyter-cell-tags0.1.6 vscode-jupyter-slideshow0.1.5 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Happens to me all the time, not sure exactly what are the steps to reproduce, it has something to do with collapsing cells and then running them again, or something to do with restarting the kernel... !
Issue "a)" happened to me already before the last update as well, but the issue "b)" happens to me only since the last version and is quite incapacitating.
This issue should be fixed now in latest Insiders and will be released with next Stable recovery build.

Discussion:
const editorHeight = this.calculateInitEditorHeight(); this.initializeEditor(editorHeight); this._renderedInputCollapseState = false; // editor is always expanded initially <del> DOM.show(this.templateData.editorPart); // however the editor part display might not be cleared on template </del> this.registerViewCellLayoutChange(); this.registerCellEditorEventListeners();

this._outputContainerRenderer.render(); this._renderedOutputCollapseState = false; // the output is always rendered initially // Need to do this after the intial renderOutput <del> if (this.viewCell.isOutputCollapsed === undefined && this.viewCell.isInputCollapsed === undefined) { this.initialViewUpdateExpanded(); this.viewCell.layoutChange({}); } </del> <ins> this.initialViewUpdateExpanded(); </ins> this._register(this.viewCell.onLayoutInfoRead(() => { this.cellParts.prepareLayout();

private initialViewUpdateExpanded(): void { this.templateData.container.classList.toggle('input-collapsed', false); <del> this._showInput(); </del> <ins> DOM.show(this.templateData.editorPart); DOM.hide(this.templateData.cellInputCollapsedContainer); </ins> this.templateData.container.classList.toggle('output-collapsed', false); this._showOutput(true); <del> this.relayoutCell(); </del> } private layoutEditor(dimension: IDimension): void {
Change:
I see this from time to time, it is not just happening reproducible. I wonder if it could be caused by more CSS getting loaded: !
The CSS rule triggering this seems to be: ! I wonder how that is possible. //cc
Related: ,
While trying to reproduce today, I also came to strange scenarios where the stylesheet for a list would contain rules for the suggest widget list.
Ok, found the problem

Discussion:
}; function overrideStyles<T>(override: IStyleOverride<T>, styles: T): any { <ins> const result = { ...styles } as { [P in keyof T]: string | undefined }; </ins> for (const key in override) { const val = override[key]; <del> (<any>styles)[key] = val !== undefined ? asCssVariable(val) : undefined; </del> <ins> result[key] = val !== undefined ? asCssVariable(val) : undefined; </ins> } <del> return styles; </del> <ins> return result; </ins> } export const defaultKeybindingLabelStyles: IKeybindingLabelStyles = {
Change:
Repro: Get in this state: <img width="869" alt="image" src="https://user-"Close the right editor group: <img width="864" alt="image" src="https://user-"Version: 1.76.0-insider (user setup) Commit: Date: 2023-02-08T12:47:14.528Z Electron: 19.1.9 Chromium: 102.0.5005.194 16.14.2 V8: 10.2.154.23-electron.0 OS: Windows_NT x64 10.0. Sandboxed: Yes
Actually seems like a generic webview issue
Fixed webview layout issue but now it seems like we also need a fix to the markdown extension
Actually not a bug. If you have two editors and side but side with a preview below , closing switches focus to the preview tab. However the preview stays for the content of This is now a duplicate of . To verify this issue: two editors and side by side a markdown preview below the entire group and confirm that the preview still shows its contents

Discussion:
) { super(WebviewEditor.ID, telemetryService, themeService, storageService); <del> this._register(editorGroupsService.onDidScroll(() => { </del> <ins> this._register(Event.any( editorGroupsService.onDidScroll, editorGroupsService.onDidAddGroup, editorGroupsService.onDidRemoveGroup, editorGroupsService.onDidMoveGroup, )(() => { </ins> if (this.webview && this._visible) { this.synchronizeWebviewContainerDimensions(this.webview); }

} private synchronizeWebviewContainerDimensions(webview: IOverlayWebview, dimension?: DOM.Dimension) { <del> if (!this._element) { </del> <ins> if (!this._element?.isConnected) { </ins> return; } const rootContainer = this._workbenchLayoutService.getContainer(Parts.EDITOR_PART);