jiebi/CodeConvo huggingface dataset:
Change:
When I disable the "Show raw keys" option (showKeys) in the VS Code settings, the editor no longer shows the shortcuts either. If the "showKeybingings" option is enabled it should show the shortcuts. This is not behaving the way expected. !
When I set these settings: <img width="652" alt="image" src=""I still see the command if I hit . You don't see it?
Unfortunately it doesn't work for me in this same configuration. Version: 1.85.1 Commit: Date: 2023-12-13T09:47:11.635Z Electron: 25.9.7 ElectronBuildId: Chromium: 114.0.5735.289 18.15.0 V8: 11.4.183.29-electron.0 OS: Linux x64 6.5.0-14-generic
I found something strange. Some commands works fine, like "Ctrl + N", "Ctrl + P", "Ctrl + Shit + P", "Ctrl + Tab". But it still doesn't work with commands like: "Ctrl + C", "Ctrl + V", "Ctrl + A", "Ctrl + X", "Alt + Arrows", "Ctrl + Arrows". Could you please test the commands when editing code?
Sadly this is this: A big chunk of our internal commands simply do not have good descriptions. It requires a large change over the code base. Feel free to send a PR my way which adds descriptions to the few that you are dependent on, if this is important.
Ok, but I would like it to show commands such as "Ctrl + C" even without a description and that is not happening. If I set it to show only the commands it continues to behave the same way, without showing the commands in the editor part. I remember that when I sent the commit that fixed some problems in the screencast, it was working perfectly, but now it no longer works. ! It still doesn't work in this configuration.
You simply closed the issue and didn't even understand the problem I brought up. I see that these are two different problems. This is very frustrating...
You're right, sorry for jumping the gun there, and thanks for the additional explanation. Fix coming.

Discussion:
append(keyboardMarker, $('span.title', {}, `${commandAndGroupLabel} `)); } <del> if ((options.showKeys ?? true) || (commandDetails && (options.showKeybindings ?? true))) { </del> <ins> if ((options.showKeys ?? true) || ((options.showKeybindings ?? true) && this._isKbFound(shortcut))) { </ins> // Fix label for arrow keys keyLabel = keyLabel?.replace('UpArrow', '↑') ?.replace('DownArrow', '↓')
Change:
Repro: some typescript file with = 1 levels of sticky scroll visible in the editor window -:bug: Version: 1.86.0-insider Commit: Date: 2023-12-20T05:47:39.317Z Electron: 27.1.3 ElectronBuildId: Chromium: 118.0.5993.159 18.17.1 V8: 11.8.172.18-electron.0 OS: Darwin arm64 23.2.0 cc since you mentioned sticky scroll during planning call
you should listen on the tokenization changed/finished event.

Discussion:
} setState(_state: StickyScrollWidgetState | undefined, foldingModel: FoldingModel | null, _rebuildFromLine?: number): void { <del> if ((!this._previousState && !_state) || (this._previousState && this._previousState.equals(_state))) { </del> <ins> if (_rebuildFromLine === undefined && ((!this._previousState && !_state) || (this._previousState && this._previousState.equals(_state))) ) { </ins> return; } const isWidgetHeightZero = this._isWidgetHeightZero(_state);
Change:
[X] Notebooks (.ipynb files) [ ] Interactive Window and/or Cell Scripts (.py files with #%% markers) Using triple backticks with language specifiers (e.g., "bash") displays two additional lines (before and after the code block) starting with a vertical bar (sort of opening and closing parentheses) For example, the following markdown: It is displayed with the additional markers; see screenshot: <img width="494" alt="image" src=""In Jupyter (or Jupyter-Lab) these markers are not displayed Version: 1.85.1 (user setup) Commit: Date: 2023-12-13T09:49:37.021Z Electron: 25.9.7 ElectronBuildId: Chromium: 114.0.5735.289 18.15.0 V8: 11.4.183.29-electron.0 OS: WindowsNT x64 10.0. v2023.11. No response Python 3.11 python: v2023.22.1 No response Remote
It also doesn't look great with the language removed, those bars are still rendered but on the same lines: !
I believe this has already been fixed in VS Code insiders: !
Oh actually still broken for notebooks but fixed for normal markdown. Will also port fix to notebooks
<img width="733" alt="image" src=""looks good!

Discussion:
linkify: true, highlight: (str: string, lang?: string) => { if (lang) { <del> return `<code class="vscode-code-block" data-vscode-code-block-lang="${markdownIt.utils.escapeHtml(lang)}">${markdownIt.utils.escapeHtml(str)}</code>`; </del> <ins> return `<div class="vscode-code-block" data-vscode-code-block-lang="${markdownIt.utils.escapeHtml(lang)}">${markdownIt.utils.escapeHtml(str)}</div>`; </ins> } <del> return `<code>${markdownIt.utils.escapeHtml(str)}</code>`; </del> <ins> return markdownIt.utils.escapeHtml(str); </ins> } }); markdownIt.linkify.set({ fuzzyLink: false });

pre code { line-height: 1.357em; white-space: pre-wrap; <ins> padding: 0; </ins> } li p {
Change:
There are countless entries for this kind of error !
/duplicate of
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for . See also our . Happy Coding!

Discussion:
private _stopAll(): void { // Remove any existing decorations <ins> // TODO: @Yoyokrazy - this triggers as notebooks scroll, causing highlights to disappear momentarily. </ins> this._removeAllDecorations(); // Cancel any renderDecorationsTimer

private _run(): void { let workerRequestIsValid; <del> if (!this.editor.hasWidgetFocus()) { // no focus (new nb cell, etc) </del> <ins> if (!this.editor.hasTextFocus()) { // no focus (new nb cell, etc) </ins> if (WordHighlighter.query === null) { // no previous query, nothing to highlight return;
Change:
Type: <bBug</bCreate and write then press enter. No tab or spaces inserted. Here is . <details<summarySettings</summary</detailsVS Code version: Code 1.85.1 (Universal) (, 2023-12-13T09:48:06.308Z) OS version: Darwin arm64 23.2.0 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (8)</summaryExtensionVersion ------ codespaces1.16.5 vscode-docker1.28.0 python2023.22.1 vscode-pylance2023.12.1 remote-ssh0.107.1 remote-ssh-edit0.86.0 remote-explorer0.4.1 hardhat-solidity0.7.3 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --

Discussion:
["(", ")"], [""", """], ["'", "'"] <del> ] } </del>  No newline at end of file <ins> ], "indentationRules": { "increaseIndentPattern": "^s*.*(:|-) ?(&amp;w+)?({[^}"']*|([^)"']*)?$", "decreaseIndentPattern": "^s+}$" } } </ins>
Change:
diff Lightbulb / Sparkle to show (For example click on method name which is in a diff) / Sparkle Icon shows with a background color even though it should probably be transparent. <img width="770" alt="image" src=""

Discussion:
width: 100%; height: 100%; opacity: 0.3; <del> background-color: var(--vscode-editor-background); </del> z-index: 1; }
Change:
extra padding right to the dropdown in terminal in insider release as shown in image below ! in stable release I don't see it !
also the terminal action also not work when I open the insiders window if create a one more terminal and then these actions start working !
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for . See also our . Happy Coding!
Looks like regression by
Thanks for reporting these issues I created a separate issue for the second bug you mentioned here:

Discussion:
.monaco-workbench .pane-composite-part > .title.has-composite-bar > .title-actions .monaco-action-bar .action-item, .monaco-workbench .pane-composite-part > .title.has-composite-bar > .global-actions .monaco-action-bar .action-item { <del> padding-right: 4px; /* Use padding instead of margin for width computation to be correct #200515 */ </del> <ins> margin-right: 4px; </ins> } .monaco-workbench .pane-composite-part > .title.has-composite-bar > .title-actions .monaco-action-bar .action-item .action-label {

if (!activePane || !this.toolBar) { return 0; } <del> return this.toolBar.getItemsWidth() + 5 + (this.globalToolBar?.getItemsWidth() ?? 0); // 5px toolBar padding-left </del> <ins> // Each toolbar item has 4px margin in the panel toolbar const toolBarWidth = this.toolBar.getItemsWidth() + this.toolBar.getItemsLength() * 4; const globalToolBarWidth = this.globalToolBar ? this.globalToolBar.getItemsWidth() + this.globalToolBar.getItemsLength() * 4 : 0; return 5 + toolBarWidth + globalToolBarWidth; // 5px toolBar padding-left </ins> } private onTitleAreaContextMenu(event: StandardMouseEvent): void {
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: Windows 10 Steps to Reproduce: to Settings UI, then search for "CSS: Custom Data" for this setting needs a few improvements in the CSS terms

Discussion:
"displayName": "CSS Language Features", "description": "Provides rich language support for CSS, LESS and SCSS files.", "css.title": "CSS", <del> "css.customData.desc": "A list of relative file paths pointing to JSON files following the [custom data format](https://github.com/microsoft/vscode-css-languageservice/blob/master/docs/customData.md).nnVS Code loads custom data on startup to enhance its CSS support for the custom CSS properties, at directives, pseudo classes and pseudo elements you specify in the JSON files.nnThe file paths are relative to workspace and only workspace folder settings are considered.", </del> <ins> "css.customData.desc": "A list of relative file paths pointing to JSON files following the [custom data format](https://github.com/microsoft/vscode-css-languageservice/blob/master/docs/customData.md).nnVS Code loads custom data on startup to enhance its CSS support for CSS custom properties (variables), at-rules, pseudo-classes, and pseudo-elements you specify in the JSON files.nnThe file paths are relative to workspace and only workspace folder settings are considered.", </ins> "css.completion.triggerPropertyValueCompletion.desc": "By default, VS Code triggers property value completion after selecting a CSS property. Use this setting to disable this behavior.", "css.completion.completePropertyWithSemicolon.desc": "Insert semicolon at end of line when completing CSS properties.", "css.lint.argumentsInColorFunction.desc": "Invalid number of parameters.",
Change:
Accepting suggestion/completion with is removing completion suffix. Given is cursor Typing in and accepting completion results in in 1.85.1, now it results in ( is removed). Version: 1.86.0-insider Commit: Date: 2024-01-09T10:06:54.001Z Electron: 27.2.1 ElectronBuildId: Chromium: 118.0.5993.159 18.17.1 V8: 11.8.172.18-electron.0 OS: Darwin arm64 23.2.0 TS 5.3.2
Unsure if this is a bug and new/changed (the 2nd video has a different code sample) but debugging shows that insert and replace ranges are about replacing the current word. <img width="1352" alt="Screenshot 2024-01-10 at 15 43 24" src=""
Reproed with the same code both in stable & insiders: /
Copyright (c) Microsoft Corporation and GitHub. All rights reserved.
-------------/ const example = { foo: 1, bar: 2, jar: 3, }; for (const { foo, |bar } of [example]) { (foo, bar); }
isn't this just a editor setting? completion.replace vs insert or something
completion.replace vs insert or something I copied my current settings in insiders to stable and still behavior was different between them.
This happens on an empty profile, and does not require actually accepting the suggestion (see my linked issue)

Discussion:
// If TS returns an explicit replacement range, we should use it for both types of completion return { <del> inserting: replaceRange, </del> <ins> inserting: new vscode.Range(replaceRange.start, this.position), </ins> replacing: replaceRange, }; }
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. --I'd like to have a theme setting that would allow me to change the foreground of the text in red next to the shortcuts. I've reached out to the dev tools and wasn't able to track the setting. I searched Google, SO, ChatGPT and I've tested a bunch of foregrounds and nothing works. <img width="1012" alt="Screenshot 2024-01-10 at 16 21 18" src=""
I a new color . It is derived from the

Discussion:
"--vscode-editorWarning-background", "--vscode-editorWarning-border", "--vscode-editorWarning-foreground", <ins> "--vscode-editorWatermark-foreground", </ins> "--vscode-editorWhitespace-foreground", "--vscode-editorWidget-background", "--vscode-editorWidget-border",

import { CommandsRegistry } from 'vs/platform/commands/common/commands'; import { ContextKeyExpr, ContextKeyExpression, IContextKeyService } from 'vs/platform/contextkey/common/contextkey'; import { defaultKeybindingLabelStyles } from 'vs/platform/theme/browser/defaultStyles'; <ins> import { editorForeground, registerColor, transparent } from 'vs/platform/theme/common/colorRegistry'; registerColor('editorWatermark.foreground', { dark: transparent(editorForeground, 0.6), light: transparent(editorForeground, 0.68), hcDark: editorForeground, hcLight: editorForeground }, localize('editorLineHighlight', 'Foreground color for the labels in the editor watermark.')); </ins> interface WatermarkEntry { readonly text: string;

display: table-row; opacity: .8; cursor: default; <ins> color: var(--vscode-editorWatermark-foreground); </ins> } .monaco-workbench .part.editor > .content .editor-group-container > .editor-group-watermark > .shortcuts dt {

vertical-align: middle; } <del> .monaco-workbench .part.editor > .content .editor-group-container > .editor-group-watermark > .shortcuts dt, .monaco-workbench .part.editor > .content .editor-group-container > .editor-group-watermark > .shortcuts dl { color: rgba(0,0,0,.68); } .monaco-workbench.vs-dark .part.editor > .content .editor-group-container .editor-group-watermark > .shortcuts dt, .monaco-workbench.vs-dark .part.editor > .content .editor-group-container .editor-group-watermark > .shortcuts dl { color: rgba(255,255,255,.6); } .monaco-workbench.hc-black .part.editor > .content .editor-group-container .editor-group-watermark > .shortcuts dt, .monaco-workbench.hc-light .part.editor > .content .editor-group-container .editor-group-watermark > .shortcuts dt { color: var(--vscode-editor-foreground); } .monaco-workbench.hc-black .part.editor > .content .editor-group-container .editor-group-watermark > .shortcuts dl, .monaco-workbench.hc-light .part.editor > .content .editor-group-container .editor-group-watermark > .shortcuts dl { color: var(--vscode-editor-foreground); opacity: 1; } </del> /* Title */ .monaco-workbench .part.editor > .content .editor-group-container > .title {
Change:
Type: <bBug</bThe actions and the more menu for source control is not always visible. I always have to expand the sidebar to access the settings. Previously, the title of the pull request was cut off. Unfortunately, this no longer happens. ! ! ! Old behaviour on VSCode stable with other extensions): ! VS Code version: Code - Insiders 1.86.0-insider (, 2024-01-11T05:46:26.380Z) OS version: Darwin arm64 23.2.0 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (83)</summaryExtensionVersion ------ better-comments3.0.2 codesnap1.3.4 vscode-m3u1.0.0 TabOut0.2.2 Bookmarks13.4.2 project-manager12.7.0 flutter-snippets3.0.0 toggle-excluded-files2.0.0 clipboard-history1.0.7 melos-code1.1.1 vscode-intelephense-client1.10.2 ccs-flutter-color1.2.2 gitignore0.9.0 dbclient-jdbc1.3.4 vscode-mysql-client26.9.10 vscode-mac-color-picker1.1.0 markdown-table-prettify3.6.0 dart-code3.81. flutter3.80.0 vscode-markdownlint0.53.0 githistory0.6.20 gitlens14.6.1 bloc6.6.5 mason0.1.11 flutter-coverage0.0.4 shell-format7.2.5 build-runner0.8.0 copilot1.148.0 copilot-chat0.12. vscode-github-actions0.26.2 vscode-pull-request-github0.78.1 todo-tree0.0.226 terraform2.29.1 json-to-dart3.5.8 rest-client0.25.1 pubspec-assist2.3.2 shortcut-menu-bar3.0.4 intellij-idea-keybindings1.5.12 build-runner2.1.1 chatgpt-helper4.1.0 vscode-gutter-preview0.30.0 indent-to-bracket1.2.2 flutter-intl1.19.3 syntax-project-pbxproj0.1.3 flutter-snippets1.0.5 Kotlin1.7.1 rainbow-csv3.11.0 git-graph1.30.0 dart-barrel-file-generator6.2.1 diff-merge0.7.0 vscode-docker1.28.0 vscode-language-pack-de1.85. remote-containers0.331.0 live-server0.4.13 vsliveshare1.0.5900 vsliveshare-pack0.4.0 vscode-flutter-freezed-helper0.1.0 sqltools0.28.1 sqltools-driver-mysql0.6.0 awesome-flutter-snippets4.0.1 vscode-streamdeck4.1.6 vscode-yaml-sort6.5.10 vscode-versionlens1.9.2 material-icon-theme4.33.0 remove-comments1.2.2 postman-for-vscode0.17.0 vscode-yaml1.14.0 vscode-sort-json1.20.0 command-variable1.61.0 flutter-riverpod-snippets1.2.2 vscode-coverage-gutters2.11.1 lcov-lang1.0.1 swift-lang1.7.2 freezed-model-gen1.0.1 better-search0.0.6 errorlens3.16.0 vscode-lldb1.10.0 vscode-wakatime24.4.0 vscode-todo-highlight1.0.5 php-debug1.34.0 vscode-surround1.5.0 markdown-all-in-one3.6.1 material-theme3.16.2 (3 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --

Discussion:
align-items: center; } <ins> .scm-view .scm-provider > .actions > .monaco-toolbar > .monaco-action-bar > .actions-container > .action-item:nth-child(1) { min-width: 20px; } </ins> .scm-view .scm-provider > .actions > .monaco-toolbar > .monaco-action-bar > .actions-container  > .action-item > .action-label, .scm-view .scm-provider > .actions > .monaco-toolbar > .monaco-action-bar > .actions-container  > .action-item > .monaco-dropdown > .dropdown-label > .action-label { display: flex;
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: Ubuntu 23.04 Steps to Reproduce: the keybindings editor () the keybindings editor opening and closing the keybindings editor a few more times that the number of , , event listeners increases each time: ~The in doesn't seem to be registered like other disposables:~ ~Disposing the ActionBar could perhaps fix the memory leak / the leaking event listeners.~ Edit: The ActionBar is actually properly disposed 40 lines below in the function.
Thank for you the issue and proposed fix! Very much appreciated!

Discussion:
} renderElement(keybindingItemEntry: IKeybindingItemEntry, index: number, templateData: ISourceColumnTemplateData, height: number | undefined): void { <ins> templateData.disposables.clear(); </ins> if (isString(keybindingItemEntry.keybindingItem.source)) { templateData.extensionContainer.classList.add('hide'); templateData.sourceLabel.element.classList.remove('hide');
Change:
Found this stack in my insiders, did some contribution move to such an early phase even before editors are created maybe?
I think from Can we keep the phase and fix the issue differently?

Discussion:
}); Registry.as<IWorkbenchContributionsRegistry>(WorkbenchExtensions.Workbench) <del> .registerWorkbenchContribution(StartupPageContribution, LifecyclePhase.Starting); </del> <ins> .registerWorkbenchContribution(StartupPageContribution, LifecyclePhase.Restored); </ins>
Change:
Type: <bBug</bSticky Scroll area becomes blank when I scroll through deeply nested results and cover a lot of space (I use it in Panel area). At first, I was thinking it's related to container height (as resize might hide content if height reduced) but same behavior reproducible in Side Bar as well. Steps to reproduce: for term that would produce deeply nester results e.g. in VS Code repo down to encounter deeply nested results that Sticky Scroll area becomes blank but still takes a lot of space to increase panel height, and scroll back and forth to have Sticky Scroll area properly rendered (but still relatively deeply nested) panel height to see that Sticky Scroll area becomes blank again <details<summaryErrors from DevTools console</summarynot sure if logs below are relevan as they might appear without an error from above </details<details<summaryRecording (18.5 MB) </detailsVS Code version: Code - Insiders 1.86.0-insider (, 2024-01-17T07:04:28.837Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </detailsExtensions: none <!-- generated by issue reporter --
just to double label check should be with or ? My expectation was later.
After rereading your issue, it appears this may be related to the tree sticky scroll instead. Pinging about it.
Thanks for reporting this Newly we started to compress nodes when the maximum number of sticky nodes was reached. The bug was caused due to trying to compress nodes which are not compressible (for example files can't be compressed with folders currently). I fixed it in
Works as expected now. Thanks!

Discussion:
const compressedNode = this.modelProvider().getCompressedTreeNode(stickyNode.node.element); if (compressedNode.element) { <ins> if (compressedNode.element.incompressible) { break; } </ins> elements.push(...compressedNode.element.elements); } }