jiebi/CodeConvo huggingface dataset:
Change:
Related issues:
Reopening to polish the setting and enable by default
This was tested last iteration, just flipped the default this time.

Discussion:
ShellIntegrationDecorationsEnabled = 'terminal.integrated.shellIntegration.decorationsEnabled', ShellIntegrationCommandHistory = 'terminal.integrated.shellIntegration.history', ShellIntegrationSuggestEnabled = 'terminal.integrated.shellIntegration.suggestEnabled', <del> ExperimentalImageSupport = 'terminal.integrated.experimentalImageSupport', </del> <ins> EnableImages = 'terminal.integrated.enableImages', </ins> SmoothScrolling = 'terminal.integrated.smoothScrolling' }

} private async _refreshImageAddon(): Promise<void> { <del> if (this._configHelper.config.experimentalImageSupport) { </del> <ins> if (this._configHelper.config.enableImages) { </ins> if (!this._imageAddon) { const AddonCtor = await this._getImageAddonConstructor(); this._imageAddon = new AddonCtor();

enabled: boolean; decorationsEnabled: boolean; }; <del> experimentalImageSupport: boolean; </del> <ins> enableImages: boolean; </ins> smoothScrolling: boolean; }

restricted: true, markdownDescription: localize('terminal.integrated.shellIntegration.suggestEnabled', "Enables experimental terminal Intellisense suggestions for supported shells when {0} is set to {1}. If shell integration is installed manually, {2} needs to be set to {3} before calling the script.", '`#terminal.integrated.shellIntegration.enabled#`', '`true`', '`VSCODE_SUGGEST`', '`1`'), type: 'boolean', <del> default: false, tags: ['experimental'] </del> <ins> default: false </ins> }, [TerminalSettingId.SmoothScrolling]: { markdownDescription: localize('terminal.integrated.smoothScrolling', "Controls whether the terminal will scroll using an animation."), type: 'boolean', default: false }, <del> [TerminalSettingId.ExperimentalImageSupport]: { </del> <ins> [TerminalSettingId.EnableImages]: { </ins> restricted: true, <del> markdownDescription: localize('terminal.integrated.experimentalImageSupport', "Enables experimental image support in the terminal. Both sixel and iTerm's inline image protocol are supported on Linux and macOS, Windows support will light up automatically when ConPTY passes through the sequences. Images will not be retained currently between window reloads/reconnects."), </del> <ins> markdownDescription: localize('terminal.integrated.enableImages', "Enables image support in the terminal. Both sixel and iTerm's inline image protocol are supported on Linux and macOS, Windows support will light up automatically when ConPTY passes through the sequences. Images will currently not be restored between window reloads/reconnects."), </ins> type: 'boolean', <del> default: false, tags: ['experimental'] </del> <ins> default: true </ins> }, } };
Change:
A regression in the condition in Set tab sizing to and see how the cut off tab should show fading, like here (not the ): ! //cc

Discussion:
// - in high contrast theme // - if we have a contrast border (which draws an outline - https://github.com/microsoft/vscode/issues/109117) // - on Safari (https://github.com/microsoft/vscode/issues/108996) <del> if (isHighContrast(theme.type) && !isSafari && !activeContrastBorderColor) { </del> <ins> if (!isHighContrast(theme.type) && !isSafari && !activeContrastBorderColor) { </ins> const workbenchBackground = WORKBENCH_BACKGROUND(theme); const editorBackgroundColor = theme.getColor(editorBackground); const editorGroupHeaderTabsBackground = theme.getColor(EDITOR_GROUP_HEADER_TABS_BACKGROUND);
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 (all extensions other than the reproduction extension) <!-- 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.78.2 OS Version: macOS 12.5.1 Over at the Tailwind CSS IntelliSense repo we are seeing multiple reports of issues with colour decorators since the release of v1.78. Some are related to the new setting which I think is a separate issue, but we are also seeing an issue where document colour requests are not being sent to the language server at all ( is in this case). I was able to create a small reproduction based on the LSP extension sample. Please see below. Steps to Reproduce: instructions from reproduction readme: When the same project is opened in v1.76.2, the count is logged repeatedly when editing the document.
Thanks a lot for the great steps to reproduce. I pushed a fix for the issue.

Discussion:
defaultProvider = provider; } else { try { <del> validDocumentColorProviderFound ||= await collector.compute(provider, model, token, colorData); </del> <ins> if (await collector.compute(provider, model, token, colorData)) { validDocumentColorProviderFound = true; } </ins> } catch (e) { onUnexpectedExternalError(e); }
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.78.2 OS Version: Steps to Reproduce: VSCode version 1.78.2 to open a GIT repo the "source control repositories" right click on the repo name "open in terminal" cmd opens instead of VSCode integrated terminal Issue only introduced since VSCode 1.78.0, in 1.77.3 was opening in integrated terminal with no issues
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.78.2. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
Issue appears in 1.78.2, starting from 1.78.0 it appears, last release not to have the issue was 1.77.3
the same issue
meanwhile waiting new release fix this. you can resolve by edit C:Users[username]AppDataLocalProgramsMicrosoft VS Coderesourcesappoutvsworkbench find then swap right after it. ! note: this will swap new function at
Possibly related on Stack Overflow:
Do you happen to know where this file is located on OSX?
it locate in /Applications/Visual Studio Code, right click Show package contents /Resources/app/out/vs/workbench Vào 14:54, Th 5, 25 thg 5, 2023 John viết:

Discussion:
} const commandService = accessor.get(ICommandService); <del> await commandService.executeCommand('openInTerminal', provider.rootUri); </del> <ins> await commandService.executeCommand('openInIntegratedTerminal', provider.rootUri); </ins> }); MenuRegistry.appendMenuItem(MenuId.SCMSourceControl, {
Change:
Two small UI issues with the filter input box in the test explorer: 's not enough right margin on the button cursor isn't aligned to center (oh, screenshot below can't capture it but basically the cursor isn't in the center vertically of the input box). <img width="647" alt="image" src=""
Fixed in
Seems better but not fixed? <img width="1090" alt="image" src=""I propose that we move this to next milestone, I can take a stab at fixing this For comparison, search input : <img width="1064" alt="image" src=""
I'm sorry to do this again, but the cursor is still not centered I think this is because the input widget has height of 20px while the container has height 23

Discussion:
max-width: none; } <del> .testing-filter-wrapper { height: 27px; } </del> .testing-filter-action-item .testing-filter-wrapper { flex-grow: 1; }
Change:
Two small UI issues with the filter input box in the test explorer: 's not enough right margin on the button cursor isn't aligned to center (oh, screenshot below can't capture it but basically the cursor isn't in the center vertically of the input box). <img width="647" alt="image" src=""
Fixed in
Seems better but not fixed? <img width="1090" alt="image" src=""I propose that we move this to next milestone, I can take a stab at fixing this For comparison, search input : <img width="1064" alt="image" src=""
I'm sorry to do this again, but the cursor is still not centered I think this is because the input widget has height of 20px while the container has height 23

Discussion:
public layout(width: number) { this.input.layout(new dom.Dimension( width - /* horizontal padding */ 24 - /* editor padding */ 8 - /* filter button padding */ 22, <del> /* line height */ 27 - /* editor padding */ 4, </del> <ins> 20, // line height from suggestEnabledInput.ts </ins> )); }
Change:
Type: <bBug</bExpected: ! Actual: ! Steps to Reproduce: a file. one configuration for any language. in ${} block and intellisense doesn't provide proper hints. More Info: bug is likely related to and . bug can be reproduced in 1.79.0-insider. VS Code version: Code 1.78.2 (, 2023-05-10T14:39:26.248Z) OS version: Windows_NT x64 10.0. Modes: Sandboxed: No <!-- generated by issue reporter --
Going way back to , this change seems right since the configuration-editing extension has contributions for these languages but the extension doesn't actually activate unless I add explicit activation events. I can't figure out why the auto activation event isn't kicking in?
Oh, sorry--we revised the event to only do auto activation if the extension also contributed a language definition for that language, since otherwise this led to extensions like Python being activated too eagerly. For debug we should restore the explicit activation events too.
I see, thanks

Discussion:
"icon": "images/icon.png", "activationEvents": [ "onProfile", <del> "onProfile:github" </del> <ins> "onProfile:github", "onLanguage:json", "onLanguage:jsonc" </ins> ], "enabledApiProposals": [ "profileContentHandlers"
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.79.0 OS Version: Windows 10, 22H2 Steps to Reproduce: a remote location (e.g. a WSL window) or something else that leads to the simple open file dialog being used a dotfile (e.g. ) an open file dialog with , you can use e.g. the "Create project from ST project" action from the embedded tools extension that the file is not available for selection (it can only be manually entered) Note: I originally reported this to the embedded-tools extension (see ), where the "Create project from ST project" dialog doesn't allow you to select the required files when working on WSL. They have however redirected me here.
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.78.2. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
Just to clarify: I have tested this with both the latest stable release, as well as with the latest insider version. Both exhibit the same broken behavior
I think this is you because it talks about the simple file picker.
I think you own . It looks like it doesn't recognize a file named as having an extension of . For now, I will just make the fix in the simple file picker, but should this change actually be made in ?

Discussion:
return sorted; } <ins> private extname(file: URI): string { const ext = resources.extname(file); if (ext.length === 0) { const basename = resources.basename(file); if (basename.startsWith('.')) { return basename; } } else { return ext; } return ''; } </ins> private filterFile(file: URI): boolean { if (this.options.filters) { <del> const ext = resources.extname(file); </del> <ins> const ext = this.extname(file); </ins> for (let i = 0; i < this.options.filters.length; i++) { for (let j = 0; j < this.options.filters[i].extensions.length; j++) { const testExt = this.options.filters[i].extensions[j];
Change:
The call stack indicates that the ExtensionService failed to find an extension despite having received the onDidInstallExtension event. Is there another service I should be using to fetch an extension right after install or to wait for the extension to be registered and available?
Extension installation and extension loading into extension host are two async things. Extension loading in extension host listens on extension installation event and adds extension to the extension host. Your listener to extension installation is may be called before extension is to extension host. If you want to read the commands from a running extension, I would recommend to listen to the event when extension is to extension host which is

Discussion:
} private registerListeners(): void { <del> this._register(this.extensionManagementService.onDidInstallExtensions(async (result) => { for (const ext of result) { const index = this.remoteExtensionMetadata.findIndex(value => ExtensionIdentifier.equals(value.id, ext.identifier.id)); </del> <ins> this._register(this.extensionService.onDidChangeExtensions(async (result) => { for (const ext of result.added) { const index = this.remoteExtensionMetadata.findIndex(value => ExtensionIdentifier.equals(value.id, ext.identifier)); </ins> if (index > -1) { this.remoteExtensionMetadata[index].installed = true; <del> this.remoteExtensionMetadata[index].remoteCommands = await this.getRemoteCommands(ext.identifier.id); </del> <ins> this.remoteExtensionMetadata[index].remoteCommands = await this.getRemoteCommands(ext.identifier.value); </ins> } } }));
Change:
Set a 2x2 layout and make the window smaller: <img width="1210" alt="image" src=""
Hmmm, points to: But I see nothing from you here actually, I wonder if it could possibly be the Electron 22 update?
Opening up for help from community if someone wants to investigate. Here is what it should look like when you go small: <img width="760" alt="image" src=""
Confirmed, this is coming from the Electron 22 update. I cannot see any changes to the CSS that would otherwise explain this, so either this is a bug in Chrome or we need to change the CSS to get the experience we want: The watermark should shrink when the available space gets little. Currently it seems to stay as it is. CSS is here:

Discussion:
max-height: 100%; aspect-ratio: 1/1; background-image: url('./letterpress-light.svg'); <del> background-size: 100%; </del> <ins> background-size: contain; </ins> background-position-x: center; background-repeat: no-repeat; }
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. --Steps to Reproduce: a notebook cell one, cmd+i cell two, cmd+i Inline chat gets disposed in cell one, a new one is created in cell two, and lastly, cell editor one gets focused automatically

Discussion:
this._ctxLastFeedbackKind.reset(); this._zone.hide(); <del> this._editor.focus(); </del> <ins> // Return focus to the editor only if the current focus is within the editor widget if (this._editor.hasWidgetFocus()) { this._editor.focus(); } </ins> this._sessionStore?.dispose(); this._sessionStore = undefined;
Change:
Hello, I am using jupyter notebook with VsCode. Everything works pretty well, but when I display the output of a cell with control+down arrow, the screen reader announces the entire output cell, but I can't scroll through it line by line with the arrow keys. It would be helpful if the system cursor could scroll within the output cell as in an editor. I also searched within the options, but could not find one that would enable this feature. Germano
thanks for the feedback, we are currently trying to make some improvements in this exact area. I was using for improving the context when focusing on the cell output since, from my experimentation with the screen reader, it tended to jump around to different outputs, but your suggested change might just resolve that issue by better containing the reader within that single output.
Will be one of the reasons we add
can you consider doing this in July?
verification: run a cell with output, either click the output to focus it, or press ctrl+down (default) press alt+F2 output should be presented in an accessible view
I tried to verify with a GitHub Issues notebook, and here's what I get: <img width="1920" alt="image" src=""This view isn't scrollable via mouse or via keyboard arrow down.
support was for jupyter notebooks, not github issue notebooks. We probably shouldn't be showing anything for github issue notebooks for now
strange overflow behavior covered by verification (should only affect ipynb files): run a cell with output, either click the output to focus it, or press ctrl+down (default) press alt+F2 output should be presented in an accessible view

Discussion:
import { NOTEBOOK_IS_ACTIVE_EDITOR, NOTEBOOK_OUTPUT_FOCUSED } from 'vs/workbench/contrib/notebook/common/notebookContextKeys'; import { runAccessibilityHelpAction, showAccessibleOutput } from 'vs/workbench/contrib/notebook/browser/notebookAccessibility'; import { IAccessibleViewService } from 'vs/workbench/contrib/accessibility/browser/accessibleView'; <ins> import { ContextKeyExpr } from 'vs/platform/contextkey/common/contextkey'; </ins> /*--------------------------------------------------------------------------------------------- */

const editorService = accessor.get(IEditorService); return showAccessibleOutput(accessibleViewService, editorService); <del> }, NOTEBOOK_OUTPUT_FOCUSED)); </del> <ins> }, ContextKeyExpr.and(NOTEBOOK_OUTPUT_FOCUSED, ContextKeyExpr.equals('resourceExtname', '.ipynb')) )); </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. --Version: 1.78.2 (user setup) Commit: Date: 2023-05-10T14:39:26.248Z Electron: 22.5.2 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0. Sandboxed: Yes Steps to Reproduce: a VB file with the following line: Observe that the seems to be marked with the mismatched bracket color. ! instead of line ! Probably the ideal solution is to add an value of to the file. However, it might also be worth noting that I do not understand why the or are getting this treatment, because I am not observing them being color matched.
would you expect angle brackets in VB to get color matching when bracket pair colorization is turned on?
As a quick workaround, I'd suggest to remove bracket pair from VB (and wait of a PR to configure it properly).

Discussion:
"brackets": [ ["{", "}"], ["[", "]"], <del> ["(", ")"], ["<", ">"] </del> <ins> ["(", ")"] </ins> ], "autoClosingPairs": [ ["{", "}"],
Change:
Type: <bBug</bfolder under WSL. to extension and for some extension chose Enable Enable (Workspace). ! Problem: extension is displayed as enabled in WSL globally ! It must be displayed as enabled in this workspace, see for example how it looks when not using WSL ! VS Code version: Code 1.78.2 (, 2023-05-10T14:39:26.248Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: Yes Remote OS version: Linux x64 5.15.79.1-microsoft-standard-WSL2+ Remote OS version: Linux x64 5.15.79.1-microsoft-standard-WSL2+ Remote OS version: Linux x64 5.15.79.1-microsoft-standard-WSL2+ Remote OS version: Linux x64 5.15.79.1-microsoft-standard-WSL2+ Remote OS version: Linux x64 5.15.79.1-microsoft-standard-WSL2+ Remote OS version: Linux x64 5.15.79.1-microsoft-standard-WSL2+ Remote OS version: Linux x64 5.15.79.1-microsoft-standard-WSL2+ Remote OS version: Linux x64 5.15.79.1-microsoft-standard-WSL2+ <details<summarySystem Info</summary </details<details<summaryExtensions (19)</summaryExtensionVersion ------ Bookmarks13.3.1 jupyter-keymap1.1.0 remote-containers0.292.0 remote-ssh0.102.0 remote-ssh-edit0.86.0 remote-wsl0.78.8 remote-explorer0.4.0 vscode-gn1.1.0 ng-template16.0.0 asciidoctor-vscode2.9.8 vscode-fish1.0.33 bitbake1.1.2 cmake-tools1.14.31 cpptools1.15.4 cpptools-extension-pack1.3.0 makefile-tools0.7.0 vscode-xml0.25.0 shader1.1.5 cmake0.0.17 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Seems like a UI bug

Discussion:
const isRunning = this.extensionService.extensions.some(e => areSameExtensions({ id: e.identifier.value, uuid: e.uuid }, this.extension!.identifier)); if (isEnabled && isRunning) { <ins> if (this.extension.enablementState === EnablementState.EnabledWorkspace) { this.updateStatus({ message: new MarkdownString(localize('workspace enabled', "This extension is enabled for this workspace by the user.")) }, true); return; } </ins> if (this.extensionManagementServerService.localExtensionManagementServer && this.extensionManagementServerService.remoteExtensionManagementServer) { if (this.extension.server === this.extensionManagementServerService.remoteExtensionManagementServer) { this.updateStatus({ message: new MarkdownString(localize('extension enabled on remote', "Extension is enabled on '{0}'", this.extension.server.label)) }, true);

this.updateStatus({ message: new MarkdownString(localize('globally enabled', "This extension is enabled globally.")) }, true); return; } <del> if (this.extension.enablementState === EnablementState.EnabledWorkspace) { this.updateStatus({ message: new MarkdownString(localize('workspace enabled', "This extension is enabled for this workspace by the user.")) }, true); return; } </del> } if (!isEnabled && !isRunning) {