Question:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --Add support for --proxy-bypass-list in the file so that we can provide a default proxy bypass list to VS Code users. Setting NO_PROXY doesn't work as a solution because it would either have to be set as a user / system environment variable thus impacting all applications, or we would have to rely on our VS Code users to explicitly pass --proxy-bypass-list as an argument to code on the command line each time they launch. Having the option to set this in would provide us with a way to package this in our default enterprise installation of VS Code so users would get this setting by default, but just for VS Code.
Could we just in . I was not aware that only a subset of our command line arguments can be configured there actually. fyi
Yes we can expose it Yeah the list of chromium commandline flags in quit large and always changes with version updates it would be a nightmare if we are to support all of them in . At this time we only support those on a case by case basis.
Thanks, makes sense! Should I assign this one to you? If you are busy, I am happy to provide a PR in July if you give me a code pointer?
Here is an example of recent flag addition , feel free to send a PR. I can review it. Thanks!
Thanks for that great example. Here's the PR I verified that adding "proxy-bypass-list" does not produce errors in I did not verify if this list actually gets passed to Chrome. We can ask if we get this out to an insiders build.
FYI: There is a PR in progress for adding a setting for the feature:
Thanks. But unlike that PR, I think this flag just needs to be passed to Chromium and it should get handled. i.e. I did not add any code in VS Code that actually handles the flag.
<!-- 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!
This flag doesn't seem to work for me unfortunately. Using mitmproxy I still see the bypassed domains: !
Can confirm, preparing a fix now.
thanks for the quick fix
verification steps: Setup mitmproxy Start the application with proxy server Check the logs to see requests from the application are intercepted, you should see some domains like or Open and set Restart the application with same proxy server Confirm that requests to these hosts are not seen in the intercepted logs anymore

'force-color-profile', // disable LCD font rendering, a Chromium flag <del> 'disable-lcd-text' </del> <ins> 'disable-lcd-text', // bypass any specified proxy for the given semi-colon-separated list of hosts 'proxy-bypass-list' </ins> ]; if (process.platform === 'linux') {


Question:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --Add support for --proxy-bypass-list in the file so that we can provide a default proxy bypass list to VS Code users. Setting NO_PROXY doesn't work as a solution because it would either have to be set as a user / system environment variable thus impacting all applications, or we would have to rely on our VS Code users to explicitly pass --proxy-bypass-list as an argument to code on the command line each time they launch. Having the option to set this in would provide us with a way to package this in our default enterprise installation of VS Code so users would get this setting by default, but just for VS Code.
Could we just in . I was not aware that only a subset of our command line arguments can be configured there actually. fyi
Yes we can expose it Yeah the list of chromium commandline flags in quit large and always changes with version updates it would be a nightmare if we are to support all of them in . At this time we only support those on a case by case basis.
Thanks, makes sense! Should I assign this one to you? If you are busy, I am happy to provide a PR in July if you give me a code pointer?
Here is an example of recent flag addition , feel free to send a PR. I can review it. Thanks!
Thanks for that great example. Here's the PR I verified that adding "proxy-bypass-list" does not produce errors in I did not verify if this list actually gets passed to Chrome. We can ask if we get this out to an insiders build.
FYI: There is a PR in progress for adding a setting for the feature:
Thanks. But unlike that PR, I think this flag just needs to be passed to Chromium and it should get handled. i.e. I did not add any code in VS Code that actually handles the flag.
<!-- 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!
This flag doesn't seem to work for me unfortunately. Using mitmproxy I still see the bypassed domains: !
Can confirm, preparing a fix now.
thanks for the quick fix
verification steps: Setup mitmproxy Start the application with proxy server Check the logs to see requests from the application are intercepted, you should see some domains like or Open and set Restart the application with same proxy server Confirm that requests to these hosts are not seen in the intercepted logs anymore

type: 'boolean', description: localize('argv.disableLcdText', 'Disables LCD font antialiasing.') }, <ins> 'proxy-bypass-list': { type: 'string', description: localize('argv.proxyBypassList', 'Bypass any specified proxy for the given semi-colon-separated list of hosts. Example value "<local>;*.microsoft.com;*foo.com;1.2.3.4:5678", will use the proxy server for all hosts except for local addresses (localhost, 127.0.0.1 etc.), microsoft.com subdomains, hosts that contain the suffix foo.com and anything at 1.2.3.4:5678') }, </ins> 'disable-hardware-acceleration': { type: 'boolean', description: localize('argv.disableHardwareAcceleration', 'Disables hardware acceleration. ONLY change this option if you encounter graphic issues.')


Question:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --Add support for --proxy-bypass-list in the file so that we can provide a default proxy bypass list to VS Code users. Setting NO_PROXY doesn't work as a solution because it would either have to be set as a user / system environment variable thus impacting all applications, or we would have to rely on our VS Code users to explicitly pass --proxy-bypass-list as an argument to code on the command line each time they launch. Having the option to set this in would provide us with a way to package this in our default enterprise installation of VS Code so users would get this setting by default, but just for VS Code.
Could we just in . I was not aware that only a subset of our command line arguments can be configured there actually. fyi
Yes we can expose it Yeah the list of chromium commandline flags in quit large and always changes with version updates it would be a nightmare if we are to support all of them in . At this time we only support those on a case by case basis.
Thanks, makes sense! Should I assign this one to you? If you are busy, I am happy to provide a PR in July if you give me a code pointer?
Here is an example of recent flag addition , feel free to send a PR. I can review it. Thanks!
Thanks for that great example. Here's the PR I verified that adding "proxy-bypass-list" does not produce errors in I did not verify if this list actually gets passed to Chrome. We can ask if we get this out to an insiders build.
FYI: There is a PR in progress for adding a setting for the feature:
Thanks. But unlike that PR, I think this flag just needs to be passed to Chromium and it should get handled. i.e. I did not add any code in VS Code that actually handles the flag.
<!-- 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!
This flag doesn't seem to work for me unfortunately. Using mitmproxy I still see the bypassed domains: !
Can confirm, preparing a fix now.
thanks for the quick fix
verification steps: Setup mitmproxy Start the application with proxy server Check the logs to see requests from the application are intercepted, you should see some domains like or Open and set Restart the application with same proxy server Confirm that requests to these hosts are not seen in the intercepted logs anymore

app.commandLine.appendSwitch(argvKey); } } else if (argvValue) { <del> if (argvKey === 'force-color-profile') { // Color profile app.commandLine.appendSwitch(argvKey, argvValue); } else if (argvKey === 'password-store') { </del> <ins> if (argvKey === 'password-store') { </ins> // Password store // TODO@TylerLeonhardt: Remove this migration in 3 months let migratedArgvValue = argvValue;


Question:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --Add support for --proxy-bypass-list in the file so that we can provide a default proxy bypass list to VS Code users. Setting NO_PROXY doesn't work as a solution because it would either have to be set as a user / system environment variable thus impacting all applications, or we would have to rely on our VS Code users to explicitly pass --proxy-bypass-list as an argument to code on the command line each time they launch. Having the option to set this in would provide us with a way to package this in our default enterprise installation of VS Code so users would get this setting by default, but just for VS Code.
Could we just in . I was not aware that only a subset of our command line arguments can be configured there actually. fyi
Yes we can expose it Yeah the list of chromium commandline flags in quit large and always changes with version updates it would be a nightmare if we are to support all of them in . At this time we only support those on a case by case basis.
Thanks, makes sense! Should I assign this one to you? If you are busy, I am happy to provide a PR in July if you give me a code pointer?
Here is an example of recent flag addition , feel free to send a PR. I can review it. Thanks!
Thanks for that great example. Here's the PR I verified that adding "proxy-bypass-list" does not produce errors in I did not verify if this list actually gets passed to Chrome. We can ask if we get this out to an insiders build.
FYI: There is a PR in progress for adding a setting for the feature:
Thanks. But unlike that PR, I think this flag just needs to be passed to Chromium and it should get handled. i.e. I did not add any code in VS Code that actually handles the flag.
<!-- 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!
This flag doesn't seem to work for me unfortunately. Using mitmproxy I still see the bypassed domains: !
Can confirm, preparing a fix now.
thanks for the quick fix
verification steps: Setup mitmproxy Start the application with proxy server Check the logs to see requests from the application are intercepted, you should see some domains like or Open and set Restart the application with same proxy server Confirm that requests to these hosts are not seen in the intercepted logs anymore

migratedArgvValue = 'gnome-libsecret'; } app.commandLine.appendSwitch(argvKey, migratedArgvValue); <ins> } else { app.commandLine.appendSwitch(argvKey, argvValue); </ins> } } }


Question: Testing enable link underline open settings editor and scroll to "Text Editor" section in-text links are underlines but command links aren't unsure if this should be aligned or not? <img width="759" alt="Screenshot 2024-06-25 at 09 50 40" src=""

color: var(--vscode-textLink-foreground); } <ins> .settings-editor > .settings-body .settings-tree-container .setting-item-contents .setting-item-markdown a, .settings-editor > .settings-body .settings-tree-container .setting-item-contents .edit-in-settings-button { text-decoration: var(--text-link-decoration); } </ins> .settings-editor > .settings-body .settings-tree-container .setting-item-contents .setting-item-markdown a:focus, .settings-editor > .settings-body .settings-tree-container .setting-item-contents .edit-in-settings-button:focus { outline: 1px solid -webkit-focus-ring-color;


Question:
Testing Once again, I'm not sure what the norms are here, but would it be useful to have the actions in the status bar show in the accessibly view? <img width="607" alt="image" src=""
Hi yes that would make sense. Good point!

return new HoverAction(parent, actionOptions, keybindingLabel); } <ins> public readonly actionLabel: string; public readonly actionKeybindingLabel: string | null; </ins> private readonly actionContainer: HTMLElement; private readonly action: HTMLElement; private constructor(parent: HTMLElement, actionOptions: { label: string; iconClass?: string; run: (target: HTMLElement) => void; commandId: string }, keybindingLabel: string | null) { super(); <ins> this.actionLabel = actionOptions.label; this.actionKeybindingLabel = keybindingLabel; </ins> this.actionContainer = dom.append(parent, $('div.action-container')); this.actionContainer.setAttribute('tabindex', '0');


Question:
Testing Once again, I'm not sure what the norms are here, but would it be useful to have the actions in the status bar show in the accessibly view? <img width="607" alt="image" src=""
Hi yes that would make sense. Good point!

import { localize } from 'vs/nls'; import { InlayHintsHover } from 'vs/editor/contrib/inlayHints/browser/inlayHintsHover'; import { BugIndicatingError } from 'vs/base/common/errors'; <ins> import { HoverAction } from 'vs/base/browser/ui/hover/hoverWidget'; </ins> export class RenderedContentHover extends Disposable {


Question:
Testing Once again, I'm not sure what the norms are here, but would it be useful to have the actions in the status bar show in the accessibly view? <img width="607" alt="image" src=""
Hi yes that would make sense. Good point!

* The HTML element containing the hover status bar. */ hoverElement: HTMLElement; <ins> /** * The actions of the hover status bar. */ actions: HoverAction[]; </ins> } type IRenderedContentHoverPartOrStatusBar = IRenderedContentHoverPart | IRenderedContentStatusBar;


Question:
Testing Once again, I'm not sure what the norms are here, but would it be useful to have the actions in the status bar show in the accessibly view? <img width="607" alt="image" src=""
Hi yes that would make sense. Good point!

return this._statusBar.hoverElement; } <ins> get actions(): HoverAction[] { return this._statusBar.actions; } </ins> dispose() { this._statusBar.dispose(); }


Question:
Testing Once again, I'm not sure what the norms are here, but would it be useful to have the actions in the status bar show in the accessibly view? <img width="607" alt="image" src=""
Hi yes that would make sense. Good point!

this._renderedParts.push({ type: 'statusBar', hoverElement: renderedStatusBar.hoverElement, <ins> actions: renderedStatusBar.actions, </ins> }); } return toDisposable(() => { disposables.dispose(); });


Question:
Testing Once again, I'm not sure what the norms are here, but would it be useful to have the actions in the status bar show in the accessibly view? <img width="607" alt="image" src=""
Hi yes that would make sense. Good point!

return ''; } if (renderedPart.type === 'statusBar') { <del> return localize('hoverAccessibilityStatusBar', "This is a hover status bar."); </del> <ins> const statusBarDescription = [localize('hoverAccessibilityStatusBar', "This is a hover status bar.")]; for (const action of renderedPart.actions) { const keybinding = action.actionKeybindingLabel; if (keybinding) { statusBarDescription.push(localize('hoverAccessibilityStatusBarActionWithKeybinding', "It has an action with label {0} and keybinding {1}.", action.actionLabel, keybinding)); } else { statusBarDescription.push(localize('hoverAccessibilityStatusBarActionWithoutKeybinding', "It has an action with label {0}.", action.actionLabel)); } } return statusBarDescription.join('n'); </ins> } return renderedPart.participant.getAccessibleContent(renderedPart.hoverPart); }


Question:
Testing Once again, I'm not sure what the norms are here, but would it be useful to have the actions in the status bar show in the accessibly view? <img width="607" alt="image" src=""
Hi yes that would make sense. Good point!

export class EditorHoverStatusBar extends Disposable implements IEditorHoverStatusBar { public readonly hoverElement: HTMLElement; <ins> public readonly actions: HoverAction[] = []; </ins> private readonly actionsElement: HTMLElement; private _hasContent: boolean = false;


Question:
Testing Once again, I'm not sure what the norms are here, but would it be useful to have the actions in the status bar show in the accessibly view? <img width="607" alt="image" src=""
Hi yes that would make sense. Good point!

const keybinding = this._keybindingService.lookupKeybinding(actionOptions.commandId); const keybindingLabel = keybinding ? keybinding.getLabel() : null; this._hasContent = true; <del> return this._register(HoverAction.render(this.actionsElement, actionOptions, keybindingLabel)); </del> <ins> const action = this._register(HoverAction.render(this.actionsElement, actionOptions, keybindingLabel)); this.actions.push(action); return action; </ins> } public append(element: HTMLElement): HTMLElement {


Question:
<!-- 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.91.0 (Universal) OS Version: Darwin arm64 23.5.0 Steps to Reproduce: new profile test to new profile in Devcontainer sample container is loaded without extensions. Opening in DevContainer with the default profile works correctly. Works correctly with the previous version of vscode 1.90.2
Same For Me
+1 extensions from are not enabled in the container when using a custom profile. Although the container logs does report that the extension was successfully installed, and I can see it is installed in the container, in . It's just not enabled when using a custom vscode profile.

} extensionsToInstall.push({ extension: gallery, <del> options: { ...installOptions, installGivenVersion: !!version, isApplicationScoped: installedExtension?.isApplicationScoped }, </del> <ins> options: { ...installOptions, installGivenVersion: !!version, isApplicationScoped: installOptions.isApplicationScoped || installedExtension?.isApplicationScoped }, </ins> }); }));


Question: <!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --VSCode Version 1.91.0 introduces a new "New Window with Profile menu item". I see it's not currently available in the command palette, like the "New Window" command. <img width="603" alt="image" src=""It would be nice to have this available in the command palette.

this._register(this.registerSwitchProfileAction()); this.registerOpenProfileSubMenu(); <ins> this.registerNewWindowWithProfileAction(); </ins> this.registerProfilesActions(); this._register(this.userDataProfilesService.onDidChangeProfiles(() => this.registerProfilesActions()));


Question: <!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --VSCode Version 1.91.0 introduces a new "New Window with Profile menu item". I see it's not currently available in the command palette, like the "New Window" command. <img width="603" alt="image" src=""It would be nice to have this available in the command palette.

}); } <ins> private registerNewWindowWithProfileAction(): IDisposable { return registerAction2(class NewWindowWithProfileAction extends Action2 { constructor() { super({ id: `workbench.profiles.actions.newWindowWithProfile`, title: localize2('newWindowWithProfile', "New Window with Profile..."), category: PROFILES_CATEGORY, precondition: HAS_PROFILES_CONTEXT, f1: true, }); } async run(accessor: ServicesAccessor) { const quickInputService = accessor.get(IQuickInputService); const userDataProfilesService = accessor.get(IUserDataProfilesService); const hostService = accessor.get(IHostService); const pick = await quickInputService.pick( userDataProfilesService.profiles.map(profile => ({ label: profile.name, profile })), { title: localize('new window with profile', "New Window with Profile"), placeHolder: localize('pick profile', "Select Profile"), canPickMany: false }); if (pick) { return hostService.openWindow({ remoteAuthority: null, forceProfile: pick.profile.name }); } } }); } </ins> private registerNewWindowAction(profile: IUserDataProfile): IDisposable { const disposables = new DisposableStore();


Question:
Type: <bBug</bscreen ready accessiblity mode to be on. Look for screen reader optimized at the bottom bar of VS Code. settings, search for "accessibility volume". Set it to 0. an action in a VS Code editor that creates a sound (which you haven't configured to be "off"/"never"), eg trigger an inline copilot suggestion. a sound (make sure your computer audio is on) even though you set volume to 0. VS Code version: Code 1.91.1 (, 2024-07-09T22:07:46.768Z) OS version: Darwin arm64 23.5.0 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (71)</summaryExtensionVersion ------ better-comments3.0.2 quitcontrol-vscode4.0.0 solarized-light-custom4.0.1 solidjs3.0.7 vscode-tailwindcss0.12.5 turbo-console-log2.10.4 ruff2024.30.0 regex0.4.0 doxdocgen1.4.0 vscode-eslint3.0.10 xml2.5.1 es7-react-js-snippets3.1.1 gitlens15.2.0 prettier-vscode10.4.0 figma-vscode-extension0.3.5 auto-rename-tag0.1.10 shell-format7.2.5 kotlin0.2.34 macros1.2.1 copilot1.213.0 copilot-chat0.17. vscode-pull-request-github0.92.0 go0.41.4 gti-vscode0.6.1 vscode-graphql-syntax1.3.6 better-cpp-syntax1.27.1 vscode-go-template0.2.1 cmake-language-support-vscode0.0.9 Kotlin1.7.1 git-graph1.30.0 vscode-docker1.29.1 vscode-dotnet-runtime2.0.9 black-formatter2024.3. debugpy2024.9. isort2023.10.1 python2024.10.0 vscode-pylance2024.7.1 jupyter2024.6.0 jupyter-keymap1.1.2 jupyter-renderers1.0.18 vscode-jupyter-cell-tags0.1.9 vscode-jupyter-slideshow0.1.6 remote-containers0.375.1 remote-ssh0.112.0 remote-ssh-edit0.86.0 remote-wsl0.88.2 vscode-remote-extensionpack0.25.0 cmake-tools1.18.43 cpptools1.20.5 cpptools-extension-pack1.3.0 remote-explorer0.4.3 remote-server1.5.2 test-adapter-converter0.1.9 vsliveshare1.0.5932 vsix-viewer1.0.5 vscode-hack2.20.0 quicktype23.0.170 webgl-glsl-editor1.3.8 code-spell-checker3.0.1 tauri-vscode0.2.6 blueprint3.0.0 best-dark-themes-pack1.0.2 best-light-themes-pack1.0.2 cmake0.0.17 vscode-lldb1.10.0 vscode-swiftformat1.6.10 change-case1.0.0 luahelper0.2.28 pretty-ts-errors0.5.4 markdown-all-in-one3.6.2 material-theme3.17.2 (28 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
thanks for taking a look ! i believe this will resolve as well
Specifically the setting doesn't get saved to Even if you write it manually in , VSCode removes it on next start. Both and have this problem.

} private getVolumeInPercent(): number { <del> const volume = this.configurationService.getValue<number>('accessibilitySignals.volume'); </del> <ins> const volume = this.configurationService.getValue<number>('accessibility.signalOptions.volume'); </ins> if (typeof volume !== 'number') { return 50; }


Question:
Postgres supports dollar quoted strings as an alternative to regular strings. This is useful when you need to include the character itself but don't want to escape it. The official documentation can be found . Unfortunately, the default SQL highlighter in VSCode does not seem to support this syntax. Steps to Reproduce to a new file the "SQL" language mode the following content: Expected should not start a new string. The content between and should be identified as a string and highlighted as such. Actual ! Additional context Version: 1.91.1 Commit: User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Embedder: Also tested in the desktop version with identical results.
Note that there may be good reason the editor tries to highlight code in the dollar quoted block. Dollar quoted strings are often used to declare function bodies in postgres and there are therefore (perhaps most commonly) instances where the content inside the dollar signs would be better off using "regular" sql highlighting. However, the reported issue is very annoying as it breaks highlighting for the rest of the file. If implementing a full parser with support for these types of "sometimes strings" requires too much effort, a passable alternative would be to at least stop the highlighter from leaking outside the dollar quoted scope.
Th grammar we have is for MS SQL and doesn't support features outside that. Duplicate of
In that case, I think you should rename the user-visible language mode to "MSSQL" rather than "SQL". I find just calling it "SQL" to be a deceptive marketing practice if you are not going to support other SQL dialects in it.
It is fair to say that MS SQL won't work for all SQL flavors. I will discuss renaming it with the team.
Based on some quick digging, MS SQL uses Transact-SQL (T-SQL). The most appropriate thing to rename the built in SQL grammar to would be T-SQL. However, I'm not sure that T-SQL will mean something to most users.
I'm going to wait and try renaming at the very beginning of our next milestone so that I can see if any insiders users are thrown off first.
I think T-SQL is not well known enough and will be confusing. I'll try renaming to MS SQL.
<!-- UNABLETOLOCATECOMMITMESSAGE repo --Issue marked as unreleased but unable to locate closing commit in repo history. If this was closed in a separate repo you can add the label directly, or comment .
<!-- UNABLETOLOCATECOMMITMESSAGE --Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting , or directly add the label if you know this has already been releaased
To verify: Open a file in VS Code Open the language picker from the status bar Verify that you don't see SQL, but instead see MS SQL

".dsql" ], "aliases": [ <del> "SQL" </del> <ins> "MS SQL", "T-SQL" </ins> ], "configuration": "./language-configuration.json" }


Question:
<!-- 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, this is an extension-related issue that arises across extensions with walkthroughs <!-- 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.91.1 OS Version: Windows 11 Extension walkthroughs are not launching upon install. Expected behavior: walkthrough launches automatically upon install. Tested on C# Dev Kit extension and Python extension. Seemed to work in 1.90.0 but does not work in 1.91.1. Steps to Reproduce [Windows Sandbox]: a Windows Sandbox Edge and download VS Code (stable) from the VS Code website the C# Dev Kit extension. Note: Upon install the walkthrough is supposed to launch automatically. This is not happening, but I can manually open the walkthrough using these steps. command palette. command 'Welcome: Open Walkthrough' 'Get Started with C# Dev Kit' ! steps 3-7 with the Python extension. Same behavior. Steps to Reproduce [VS Code stable and VS Code insider]: VS Code C# Dev Kit (if you have it installed) VS Code C# Dev Kit extension. Note: Upon install the walkthrough is supposed to launch automatically. This is not happening, but I can manually open the walkthrough using these steps. command palette. command 'Welcome: Open Walkthrough' 'Get Started with C# Dev Kit' steps 2-7 with the Python extension. Same behavior.
closedWith
using the steps above, I am not seeing the walkthrough open when I reinstall the extension
Was just talking with about this- if you've had it installed in the past, it won't work, but for me it works in a window with a clean user-data-dir

installed.forEach(ext => this.progressByEvent(`extensionInstalled:${ext.identifier.id.toLowerCase()}`)); }); <del> this._register(this.extensionManagementService.onDidInstallExtensions(async (result) => { const hadLastFoucs = await this.hostService.hadLastFocus(); </del> <ins> this._register(this.extensionManagementService.onDidInstallExtensions((result) => { </ins> for (const e of result) { const skipWalkthrough = e?.context?.[EXTENSION_INSTALL_SKIP_WALKTHROUGH_CONTEXT] || e?.context?.[EXTENSION_INSTALL_DEP_PACK_CONTEXT]; // If the window had last focus and the install didn't specify to skip the walkthrough // Then add it to the sessionInstallExtensions to be opened <del> if (hadLastFoucs && !skipWalkthrough) { </del> <ins> if (!skipWalkthrough) { </ins> this.sessionInstalledExtensions.add(e.identifier.id.toLowerCase()); } this.progressByEvent(`extensionInstalled:${e.identifier.id.toLowerCase()}`);


Question:
<!-- 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, this is an extension-related issue that arises across extensions with walkthroughs <!-- 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.91.1 OS Version: Windows 11 Extension walkthroughs are not launching upon install. Expected behavior: walkthrough launches automatically upon install. Tested on C# Dev Kit extension and Python extension. Seemed to work in 1.90.0 but does not work in 1.91.1. Steps to Reproduce [Windows Sandbox]: a Windows Sandbox Edge and download VS Code (stable) from the VS Code website the C# Dev Kit extension. Note: Upon install the walkthrough is supposed to launch automatically. This is not happening, but I can manually open the walkthrough using these steps. command palette. command 'Welcome: Open Walkthrough' 'Get Started with C# Dev Kit' ! steps 3-7 with the Python extension. Same behavior. Steps to Reproduce [VS Code stable and VS Code insider]: VS Code C# Dev Kit (if you have it installed) VS Code C# Dev Kit extension. Note: Upon install the walkthrough is supposed to launch automatically. This is not happening, but I can manually open the walkthrough using these steps. command palette. command 'Welcome: Open Walkthrough' 'Get Started with C# Dev Kit' steps 2-7 with the Python extension. Same behavior.
closedWith
using the steps above, I am not seeing the walkthrough open when I reinstall the extension
Was just talking with about this- if you've had it installed in the past, it won't work, but for me it works in a window with a clean user-data-dir

this.storageService.store(walkthroughMetadataConfigurationKey, JSON.stringify([...this.metadata.entries()]), StorageScope.PROFILE, StorageTarget.USER); <del> if (sectionToOpen && this.configurationService.getValue<string>('workbench.welcomePage.walkthroughs.openOnInstall')) { </del> <ins> const hadLastFoucs = await this.hostService.hadLastFocus(); if (hadLastFoucs && sectionToOpen && this.configurationService.getValue<string>('workbench.welcomePage.walkthroughs.openOnInstall')) { </ins> type GettingStartedAutoOpenClassification = { owner: 'lramos15'; comment: 'When a walkthrthrough is opened upon extension installation';


Question:
Connect to my mac with Remote-SSH See these errors from the server in the log (Remote-SSH output channel) doesn't seem to cause a problem but it's noisy and looks like an issue
could you point me at which line this is? Our stack beautifier doesn't work on server code afaik
I don't know which line it is, I only have that stack
It's this line: Somehow node-pty can return undefined for Doesn't seem like it should be possible considering or are the fallbacks for :
I'm seeing this on my own machine so could do some debugging if you want to add logs or something

if (this._store.isDisposed) { return; } <del> this._currentTitle = ptyProcess.process; </del> <ins> // HACK: The node-pty API can return undefined somehow https://github.com/microsoft/vscode/issues/222323 this._currentTitle = (ptyProcess.process ?? ''); </ins> this._onDidChangeProperty.fire({ type: ProcessPropertyType.Title, value: this._currentTitle }); // If fig is installed it may change the title of the process const sanitizedTitle = this.currentTitle.replace(/ (figterm)$/g, '');


Question:
Type: <bBug</bWelcome - Learn the Fyndamentals Safely browse and edit code Workspace Trust Link 404 - page not found VS Code version: Code 1.91.1 (, 2024-07-09T22:06:49.809Z) OS version: Windows_NT x64 10.0. Modes: Restricted <!-- generated by issue reporter --
could you please provide a screenshot of where this broken link is? Thanks!
Got it - issue is in the walkthrough. Fix incoming. Thanks for signaling this
Is this a candidate? The change has been merged to the main branch but not the release branch, and so the fix is not in the latest Insiders.
IMO, it can go with the next one.
<!-- UNABLETOLOCATECOMMITMESSAGE repo --Issue marked as unreleased but unable to locate closing commit in repo history. If this was closed in a separate repo you can add the label directly, or comment .
<!-- UNABLETOLOCATECOMMITMESSAGE --Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting , or directly add the label if you know this has already been releaased

{ id: 'workspaceTrust', title: localize('gettingStarted.workspaceTrust.title', "Safely browse and edit code"), <del> description: localize('gettingStarted.workspaceTrust.description.interpolated', "{0} lets you decide whether your project folders should **allow or restrict** automatic code execution __(required for extensions, debugging, etc)__.nOpening a file/folder will prompt to grant trust. You can always {1} later.", Button(localize('workspaceTrust', "Workspace Trust"), 'https://github.com/microsoft/vscode-docs/blob/workspaceTrust/docs/editor/workspace-trust.md'), Button(localize('enableTrust', "enable trust"), 'command:toSide:workbench.action.manageTrustedDomain')), </del> <ins> description: localize('gettingStarted.workspaceTrust.description.interpolated', "{0} lets you decide whether your project folders should **allow or restrict** automatic code execution __(required for extensions, debugging, etc)__.nOpening a file/folder will prompt to grant trust. You can always {1} later.", Button(localize('workspaceTrust', "Workspace Trust"), 'https://code.visualstudio.com/docs/editor/workspace-trust'), Button(localize('enableTrust', "enable trust"), 'command:toSide:workbench.action.manageTrustedDomain')), </ins> when: 'workspacePlatform != 'webworker' && !isWorkspaceTrusted && workspaceFolderCount == 0', media: { type: 'svg', altText: 'Workspace Trust editor in Restricted mode and a primary button for switching to Trusted mode.', path: 'workspaceTrust.svg'


Question:
Type: <bBug</bIssue Reporter, e.g. from off Command Palette. the first dropdown to VS Code version: Code - Insiders 1.92.0-insider (, 2024-07-24T07:50:18.385Z) OS version: Windows_NT x64 10.0. Modes: <!-- generated by issue reporter --
good catch, thanks! looks like an issue with the refactor

if (styles.backgroundColor) { content.push(`.monaco-workbench { background-color: ${styles.backgroundColor} !important; }`); <ins> content.push(`.issue-reporter-body::-webkit-scrollbar-track { background-color: ${styles.backgroundColor}; }`); </ins> } if (styles.inputBorder) {


Question:
Type: <bBug</bIssue Reporter, e.g. from off Command Palette. the first dropdown to VS Code version: Code - Insiders 1.92.0-insider (, 2024-07-24T07:50:18.385Z) OS version: Windows_NT x64 10.0. Modes: <!-- generated by issue reporter --
good catch, thanks! looks like an issue with the refactor

content.push(`a:hover, .workbenchCommand:hover { color: ${styles.textLinkActiveForeground}; }`); } <del> if (styles.sliderBackgroundColor) { content.push(`::-webkit-scrollbar-thumb { background-color: ${styles.sliderBackgroundColor}; }`); } </del> if (styles.sliderActiveColor) { <del> content.push(`::-webkit-scrollbar-thumb:active { background-color: ${styles.sliderActiveColor}; }`); </del> <ins> content.push(`.issue-reporter-body::-webkit-scrollbar-thumb:active { background-color: ${styles.sliderActiveColor}; }`); </ins> } if (styles.sliderHoverColor) { <del> content.push(`::--webkit-scrollbar-thumb:hover { background-color: ${styles.sliderHoverColor}; }`); </del> <ins> content.push(`.issue-reporter-body::-webkit-scrollbar-thumb { background-color: ${styles.sliderHoverColor}; }`); content.push(`.issue-reporter-body::--webkit-scrollbar-thumb:hover { background-color: ${styles.sliderHoverColor}; }`); </ins> } if (styles.buttonBackground) {


Question:
Type: <bBug</bIssue Reporter, e.g. from off Command Palette. the first dropdown to VS Code version: Code - Insiders 1.92.0-insider (, 2024-07-24T07:50:18.385Z) OS version: Windows_NT x64 10.0. Modes: <!-- generated by issue reporter --
good catch, thanks! looks like an issue with the refactor

if (issueType === IssueType.PerformanceIssue && this.receivedSystemInfo && this.receivedPerformanceInfo) { return true; } <ins> if (issueType === IssueType.FeatureRequest) { return true; } </ins> } return false;


Question:
Type: <bBug</bIssue Reporter, e.g. from off Command Palette. the first dropdown to VS Code version: Code - Insiders 1.92.0-insider (, 2024-07-24T07:50:18.385Z) OS version: Windows_NT x64 10.0. Modes: <!-- generated by issue reporter --
good catch, thanks! looks like an issue with the refactor

// Store into config object URL this.configuration = { <ins> zoomLevel: data.zoomLevel, </ins> appRoot: this.environmentService.appRoot, windowId: 0, userEnv: {},


Question:
Type: <bBug</bIssue Reporter, e.g. from off Command Palette. the first dropdown to VS Code version: Code - Insiders 1.92.0-insider (, 2024-07-24T07:50:18.385Z) OS version: Windows_NT x64 10.0. Modes: <!-- generated by issue reporter --
good catch, thanks! looks like an issue with the refactor

cursor: pointer; appearance: auto; border: none; <ins> border-right: 6px solid transparent; padding-left: 10px; </ins> } .issue-reporter-body #similar-issues {


Question:
Type: <bBug</bIf you rename a folder to "Cut Sheet" for example, that folder and anything below it becomes a "greyed" out folder. If you have a file that is named "Cut " for example, this is also greyed out. Renaming any of these makes them a normal folder/item icon. I have confirmed that this is not a .gitignore issue, nor does it appear to be a theme issue. Please see the image below. ! VS Code version: Code 1.91.1 (, 2024-07-09T22:06:49.809Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (81)</summaryExtensionVersion ------ amazon-q-vscode1.17.0 vscode-intelephense-client1.10.4 phpserver3.0.2 vscode-yarn-script0.0.1 path-intellisense2.9.0 codeium1.10.1 doxdocgen1.4.0 vscode-markdownlint0.55.0 composer-php-vscode1.49. intelli-php-vscode0.12. phptools-vscode1.49. profiler-php-vscode1.49. xml2.5.1 gitlens15.2.1 vscode-html-css2.0.10 EditorConfig0.16.4 prettier-vscode10.4.0 vscode-yarn2.1.0 copilot1.218.0 copilot-chat0.17.1 remotehub0.62.0 vscode-pull-request-github0.92.0 gc-excelviewer4.2.59 todo-tree0.0.226 vscode-test-explorer2.21.1 better-cpp-syntax1.27.1 vscode-nuget-package-manager1.1.6 cmake-language-support-vscode0.0.9 vscode-autohotkey-plus-plus5.0.5 rainbow-csv3.12.0 compare-folders0.24.3 vscode-docker1.29.1 csdevkit1.8.14 csharp2.39.29 vscode-dotnet-runtime2.1.1 vscodeintellicode-csharp2.1.11 debugpy2024.8.0 gather2022.3.2 isort2023.10.1 python2024.10.0 vscode-pylance2024.7.1 jupyter2024.6.0 jupyter-keymap1.1.2 jupyter-renderers1.0.18 vscode-jupyter-cell-tags0.1.9 vscode-jupyter-slideshow0.1.6 remote-containers0.379.0 remote-ssh0.112.0 remote-ssh-edit0.86.0 remote-wsl0.88.2 cmake-tools1.18.43 cpptools1.21.3 cpptools-extension-pack1.3.0 live-server0.4.14 powershell2024.2.2 remote-explorer0.4.3 remote-repositories0.40.0 remote-server1.5.2 test-adapter-converter0.1.9 vscode-speech0.10.0 vsliveshare1.0.5936 indent-rainbow8.3.1 word-count0.1.0 material-icon-theme5.8.0 LiveServer5.7.9 vscode-vba0.11.0 logos-vscode1.0.1 pdf1.2.2 cmake0.0.17 highlight-matching-tag0.11.0 intellicode-api-usage-examples0.2.8 vscodeintellicode1.3.1 vscode-gradle3.15.0 vscode-java-debug0.58.0 vscode-java-dependency0.24.0 vscode-java-pack0.27.0 vscode-maven0.44.0 vscode-todo-highlight1.0.5 php-debug1.35.0 php-pack1.0.3 php-intellisense1.3.3 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
/needsMoreInfo Is it reproducible with all extensions disabled? You can try this with <kbdF1</kbdand Do you have mentioned in setting for user or workspace or do you have it in ignore file?
Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our . Please take the time to review these and update the issue. Happy Coding!
It still occurs when I reload window with extensions disabled. And I do not have mentioned in my files.exclude in my user or workspace settings JSON. My workspace does not have a a files.exclude. My user settings has the following: "files.exclude": { "/.classpath": true, "/.project": true, "/.settings": true, "/.factorypath": true }, See attached image showing extensions disabled and both files. ! And here's a picture of my .gitignore file: !
Same problem here !
PR fixing it
Fix reverted by

class FastLabelNode { private disposed: boolean | undefined; private _textContent: string | undefined; <del> private _className: string | undefined; </del> <ins> private _classNames: string[] | undefined; </ins> private _empty: boolean | undefined; constructor(private _element: HTMLElement) {


Question:
Type: <bBug</bIf you rename a folder to "Cut Sheet" for example, that folder and anything below it becomes a "greyed" out folder. If you have a file that is named "Cut " for example, this is also greyed out. Renaming any of these makes them a normal folder/item icon. I have confirmed that this is not a .gitignore issue, nor does it appear to be a theme issue. Please see the image below. ! VS Code version: Code 1.91.1 (, 2024-07-09T22:06:49.809Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (81)</summaryExtensionVersion ------ amazon-q-vscode1.17.0 vscode-intelephense-client1.10.4 phpserver3.0.2 vscode-yarn-script0.0.1 path-intellisense2.9.0 codeium1.10.1 doxdocgen1.4.0 vscode-markdownlint0.55.0 composer-php-vscode1.49. intelli-php-vscode0.12. phptools-vscode1.49. profiler-php-vscode1.49. xml2.5.1 gitlens15.2.1 vscode-html-css2.0.10 EditorConfig0.16.4 prettier-vscode10.4.0 vscode-yarn2.1.0 copilot1.218.0 copilot-chat0.17.1 remotehub0.62.0 vscode-pull-request-github0.92.0 gc-excelviewer4.2.59 todo-tree0.0.226 vscode-test-explorer2.21.1 better-cpp-syntax1.27.1 vscode-nuget-package-manager1.1.6 cmake-language-support-vscode0.0.9 vscode-autohotkey-plus-plus5.0.5 rainbow-csv3.12.0 compare-folders0.24.3 vscode-docker1.29.1 csdevkit1.8.14 csharp2.39.29 vscode-dotnet-runtime2.1.1 vscodeintellicode-csharp2.1.11 debugpy2024.8.0 gather2022.3.2 isort2023.10.1 python2024.10.0 vscode-pylance2024.7.1 jupyter2024.6.0 jupyter-keymap1.1.2 jupyter-renderers1.0.18 vscode-jupyter-cell-tags0.1.9 vscode-jupyter-slideshow0.1.6 remote-containers0.379.0 remote-ssh0.112.0 remote-ssh-edit0.86.0 remote-wsl0.88.2 cmake-tools1.18.43 cpptools1.21.3 cpptools-extension-pack1.3.0 live-server0.4.14 powershell2024.2.2 remote-explorer0.4.3 remote-repositories0.40.0 remote-server1.5.2 test-adapter-converter0.1.9 vscode-speech0.10.0 vsliveshare1.0.5936 indent-rainbow8.3.1 word-count0.1.0 material-icon-theme5.8.0 LiveServer5.7.9 vscode-vba0.11.0 logos-vscode1.0.1 pdf1.2.2 cmake0.0.17 highlight-matching-tag0.11.0 intellicode-api-usage-examples0.2.8 vscodeintellicode1.3.1 vscode-gradle3.15.0 vscode-java-debug0.58.0 vscode-java-dependency0.24.0 vscode-java-pack0.27.0 vscode-maven0.44.0 vscode-todo-highlight1.0.5 php-debug1.35.0 php-pack1.0.3 php-intellisense1.3.3 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
/needsMoreInfo Is it reproducible with all extensions disabled? You can try this with <kbdF1</kbdand Do you have mentioned in setting for user or workspace or do you have it in ignore file?
Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our . Please take the time to review these and update the issue. Happy Coding!
It still occurs when I reload window with extensions disabled. And I do not have mentioned in my files.exclude in my user or workspace settings JSON. My workspace does not have a a files.exclude. My user settings has the following: "files.exclude": { "/.classpath": true, "/.project": true, "/.settings": true, "/.factorypath": true }, See attached image showing extensions disabled and both files. ! And here's a picture of my .gitignore file: !
Same problem here !
PR fixing it
Fix reverted by

this._element.textContent = content; } <del> set className(className: string) { if (this.disposed || className === this._className) { </del> <ins> set classNames(classNames: string[]) { if (this.disposed || equals(classNames, this._classNames)) { </ins> return; } <del> this._className = className; this._element.className = className; </del> <ins> this._classNames = classNames; this._element.classList.value = ''; this._element.classList.add(...classNames); </ins> } set empty(empty: boolean) {


Question:
Type: <bBug</bIf you rename a folder to "Cut Sheet" for example, that folder and anything below it becomes a "greyed" out folder. If you have a file that is named "Cut " for example, this is also greyed out. Renaming any of these makes them a normal folder/item icon. I have confirmed that this is not a .gitignore issue, nor does it appear to be a theme issue. Please see the image below. ! VS Code version: Code 1.91.1 (, 2024-07-09T22:06:49.809Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (81)</summaryExtensionVersion ------ amazon-q-vscode1.17.0 vscode-intelephense-client1.10.4 phpserver3.0.2 vscode-yarn-script0.0.1 path-intellisense2.9.0 codeium1.10.1 doxdocgen1.4.0 vscode-markdownlint0.55.0 composer-php-vscode1.49. intelli-php-vscode0.12. phptools-vscode1.49. profiler-php-vscode1.49. xml2.5.1 gitlens15.2.1 vscode-html-css2.0.10 EditorConfig0.16.4 prettier-vscode10.4.0 vscode-yarn2.1.0 copilot1.218.0 copilot-chat0.17.1 remotehub0.62.0 vscode-pull-request-github0.92.0 gc-excelviewer4.2.59 todo-tree0.0.226 vscode-test-explorer2.21.1 better-cpp-syntax1.27.1 vscode-nuget-package-manager1.1.6 cmake-language-support-vscode0.0.9 vscode-autohotkey-plus-plus5.0.5 rainbow-csv3.12.0 compare-folders0.24.3 vscode-docker1.29.1 csdevkit1.8.14 csharp2.39.29 vscode-dotnet-runtime2.1.1 vscodeintellicode-csharp2.1.11 debugpy2024.8.0 gather2022.3.2 isort2023.10.1 python2024.10.0 vscode-pylance2024.7.1 jupyter2024.6.0 jupyter-keymap1.1.2 jupyter-renderers1.0.18 vscode-jupyter-cell-tags0.1.9 vscode-jupyter-slideshow0.1.6 remote-containers0.379.0 remote-ssh0.112.0 remote-ssh-edit0.86.0 remote-wsl0.88.2 cmake-tools1.18.43 cpptools1.21.3 cpptools-extension-pack1.3.0 live-server0.4.14 powershell2024.2.2 remote-explorer0.4.3 remote-repositories0.40.0 remote-server1.5.2 test-adapter-converter0.1.9 vscode-speech0.10.0 vsliveshare1.0.5936 indent-rainbow8.3.1 word-count0.1.0 material-icon-theme5.8.0 LiveServer5.7.9 vscode-vba0.11.0 logos-vscode1.0.1 pdf1.2.2 cmake0.0.17 highlight-matching-tag0.11.0 intellicode-api-usage-examples0.2.8 vscodeintellicode1.3.1 vscode-gradle3.15.0 vscode-java-debug0.58.0 vscode-java-dependency0.24.0 vscode-java-pack0.27.0 vscode-maven0.44.0 vscode-todo-highlight1.0.5 php-debug1.35.0 php-pack1.0.3 php-intellisense1.3.3 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
/needsMoreInfo Is it reproducible with all extensions disabled? You can try this with <kbdF1</kbdand Do you have mentioned in setting for user or workspace or do you have it in ignore file?
Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our . Please take the time to review these and update the issue. Happy Coding!
It still occurs when I reload window with extensions disabled. And I do not have mentioned in my files.exclude in my user or workspace settings JSON. My workspace does not have a a files.exclude. My user settings has the following: "files.exclude": { "/.classpath": true, "/.project": true, "/.settings": true, "/.factorypath": true }, See attached image showing extensions disabled and both files. ! And here's a picture of my .gitignore file: !
Same problem here !
PR fixing it
Fix reverted by

existingIconNode.remove(); } <del> this.domNode.className = labelClasses.join(' '); </del> <ins> this.domNode.classNames = labelClasses; </ins> this.domNode.element.setAttribute('aria-label', ariaLabel); <del> this.labelContainer.className = containerClasses.join(' '); </del> <ins> this.labelContainer.classList.value = ''; this.labelContainer.classList.add(...containerClasses); </ins> this.setupHover(options?.descriptionTitle ? this.labelContainer : this.element, options?.title); this.nameNode.setLabel(label, options);


Question:
Type: <bBug</bIf you rename a folder to "Cut Sheet" for example, that folder and anything below it becomes a "greyed" out folder. If you have a file that is named "Cut " for example, this is also greyed out. Renaming any of these makes them a normal folder/item icon. I have confirmed that this is not a .gitignore issue, nor does it appear to be a theme issue. Please see the image below. ! VS Code version: Code 1.91.1 (, 2024-07-09T22:06:49.809Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (81)</summaryExtensionVersion ------ amazon-q-vscode1.17.0 vscode-intelephense-client1.10.4 phpserver3.0.2 vscode-yarn-script0.0.1 path-intellisense2.9.0 codeium1.10.1 doxdocgen1.4.0 vscode-markdownlint0.55.0 composer-php-vscode1.49. intelli-php-vscode0.12. phptools-vscode1.49. profiler-php-vscode1.49. xml2.5.1 gitlens15.2.1 vscode-html-css2.0.10 EditorConfig0.16.4 prettier-vscode10.4.0 vscode-yarn2.1.0 copilot1.218.0 copilot-chat0.17.1 remotehub0.62.0 vscode-pull-request-github0.92.0 gc-excelviewer4.2.59 todo-tree0.0.226 vscode-test-explorer2.21.1 better-cpp-syntax1.27.1 vscode-nuget-package-manager1.1.6 cmake-language-support-vscode0.0.9 vscode-autohotkey-plus-plus5.0.5 rainbow-csv3.12.0 compare-folders0.24.3 vscode-docker1.29.1 csdevkit1.8.14 csharp2.39.29 vscode-dotnet-runtime2.1.1 vscodeintellicode-csharp2.1.11 debugpy2024.8.0 gather2022.3.2 isort2023.10.1 python2024.10.0 vscode-pylance2024.7.1 jupyter2024.6.0 jupyter-keymap1.1.2 jupyter-renderers1.0.18 vscode-jupyter-cell-tags0.1.9 vscode-jupyter-slideshow0.1.6 remote-containers0.379.0 remote-ssh0.112.0 remote-ssh-edit0.86.0 remote-wsl0.88.2 cmake-tools1.18.43 cpptools1.21.3 cpptools-extension-pack1.3.0 live-server0.4.14 powershell2024.2.2 remote-explorer0.4.3 remote-repositories0.40.0 remote-server1.5.2 test-adapter-converter0.1.9 vscode-speech0.10.0 vsliveshare1.0.5936 indent-rainbow8.3.1 word-count0.1.0 material-icon-theme5.8.0 LiveServer5.7.9 vscode-vba0.11.0 logos-vscode1.0.1 pdf1.2.2 cmake0.0.17 highlight-matching-tag0.11.0 intellicode-api-usage-examples0.2.8 vscodeintellicode1.3.1 vscode-gradle3.15.0 vscode-java-debug0.58.0 vscode-java-dependency0.24.0 vscode-java-pack0.27.0 vscode-maven0.44.0 vscode-todo-highlight1.0.5 php-debug1.35.0 php-pack1.0.3 php-intellisense1.3.3 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
/needsMoreInfo Is it reproducible with all extensions disabled? You can try this with <kbdF1</kbdand Do you have mentioned in setting for user or workspace or do you have it in ignore file?
Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our . Please take the time to review these and update the issue. Happy Coding!
It still occurs when I reload window with extensions disabled. And I do not have mentioned in my files.exclude in my user or workspace settings JSON. My workspace does not have a a files.exclude. My user settings has the following: "files.exclude": { "/.classpath": true, "/.project": true, "/.settings": true, "/.factorypath": true }, See attached image showing extensions disabled and both files. ! And here's a picture of my .gitignore file: !
Same problem here !
PR fixing it
Fix reverted by

} function cssEscape(str: string): string { <del> return str.replace(/[x11x12x14x15x40]/g, '/'); // HTML class names can not contain certain whitespace characters, use / instead, which doesn't exist in file names. </del> <ins> return str.replace(/[s]/g, '/'); // HTML class names can not contain certain whitespace characters (https://dom.spec.whatwg.org/#interface-domtokenlist), use / instead, which doesn't exist in file names. </ins> }


Question:
Type: <bBug</bIf you rename a folder to "Cut Sheet" for example, that folder and anything below it becomes a "greyed" out folder. If you have a file that is named "Cut " for example, this is also greyed out. Renaming any of these makes them a normal folder/item icon. I have confirmed that this is not a .gitignore issue, nor does it appear to be a theme issue. Please see the image below. ! VS Code version: Code 1.91.1 (, 2024-07-09T22:06:49.809Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (81)</summaryExtensionVersion ------ amazon-q-vscode1.17.0 vscode-intelephense-client1.10.4 phpserver3.0.2 vscode-yarn-script0.0.1 path-intellisense2.9.0 codeium1.10.1 doxdocgen1.4.0 vscode-markdownlint0.55.0 composer-php-vscode1.49. intelli-php-vscode0.12. phptools-vscode1.49. profiler-php-vscode1.49. xml2.5.1 gitlens15.2.1 vscode-html-css2.0.10 EditorConfig0.16.4 prettier-vscode10.4.0 vscode-yarn2.1.0 copilot1.218.0 copilot-chat0.17.1 remotehub0.62.0 vscode-pull-request-github0.92.0 gc-excelviewer4.2.59 todo-tree0.0.226 vscode-test-explorer2.21.1 better-cpp-syntax1.27.1 vscode-nuget-package-manager1.1.6 cmake-language-support-vscode0.0.9 vscode-autohotkey-plus-plus5.0.5 rainbow-csv3.12.0 compare-folders0.24.3 vscode-docker1.29.1 csdevkit1.8.14 csharp2.39.29 vscode-dotnet-runtime2.1.1 vscodeintellicode-csharp2.1.11 debugpy2024.8.0 gather2022.3.2 isort2023.10.1 python2024.10.0 vscode-pylance2024.7.1 jupyter2024.6.0 jupyter-keymap1.1.2 jupyter-renderers1.0.18 vscode-jupyter-cell-tags0.1.9 vscode-jupyter-slideshow0.1.6 remote-containers0.379.0 remote-ssh0.112.0 remote-ssh-edit0.86.0 remote-wsl0.88.2 cmake-tools1.18.43 cpptools1.21.3 cpptools-extension-pack1.3.0 live-server0.4.14 powershell2024.2.2 remote-explorer0.4.3 remote-repositories0.40.0 remote-server1.5.2 test-adapter-converter0.1.9 vscode-speech0.10.0 vsliveshare1.0.5936 indent-rainbow8.3.1 word-count0.1.0 material-icon-theme5.8.0 LiveServer5.7.9 vscode-vba0.11.0 logos-vscode1.0.1 pdf1.2.2 cmake0.0.17 highlight-matching-tag0.11.0 intellicode-api-usage-examples0.2.8 vscodeintellicode1.3.1 vscode-gradle3.15.0 vscode-java-debug0.58.0 vscode-java-dependency0.24.0 vscode-java-pack0.27.0 vscode-maven0.44.0 vscode-todo-highlight1.0.5 php-debug1.35.0 php-pack1.0.3 php-intellisense1.3.3 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
/needsMoreInfo Is it reproducible with all extensions disabled? You can try this with <kbdF1</kbdand Do you have mentioned in setting for user or workspace or do you have it in ignore file?
Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our . Please take the time to review these and update the issue. Happy Coding!
It still occurs when I reload window with extensions disabled. And I do not have mentioned in my files.exclude in my user or workspace settings JSON. My workspace does not have a a files.exclude. My user settings has the following: "files.exclude": { "/.classpath": true, "/.project": true, "/.settings": true, "/.factorypath": true }, See attached image showing extensions disabled and both files. ! And here's a picture of my .gitignore file: !
Same problem here !
PR fixing it
Fix reverted by

} function escapeCSS(str: string) { <del> str = str.replace(/[x11x12x14x15x40]/g, '/'); // HTML class names can not contain certain whitespace characters, use / instead, which doesn't exist in file names. </del> <ins> str = str.replace(/[s]/g, '/'); // HTML class names can not contain certain whitespace characters (https://dom.spec.whatwg.org/#interface-domtokenlist), use / instead, which doesn't exist in file names. </ins> return mainWindow.CSS.escape(str); }


Question:
a workspace: and drop into Expected Inserts Actual Inserts
Closing as fixed in main and release branch

return; } <del> const snippet = await this.createUriListSnippet(uriList); </del> <ins> const snippet = await this.createUriListSnippet(document.uri, uriList); </ins> if (!snippet || token.isCancellationRequested) { return; }


Question:
a workspace: and drop into Expected Inserts Actual Inserts
Closing as fixed in main and release branch

return new UriList(uris.map(uri => ({ uri, str: uri.toString(true) }))); } <del> private async createUriListSnippet(uriList: UriList): Promise<{ readonly snippet: vscode.SnippetString; readonly label: string } | undefined> { </del> <ins> private async createUriListSnippet(docUri: vscode.Uri, uriList: UriList): Promise<{ readonly snippet: vscode.SnippetString; readonly label: string } | undefined> { </ins> if (!uriList.entries.length) { return; }


Question:
a workspace: and drop into Expected Inserts Actual Inserts
Closing as fixed in main and release branch

const snippet = new vscode.SnippetString(); for (let i = 0; i < uriList.entries.length; i++) { const uri = uriList.entries[i]; <del> const relativePath = getRelativePath(uri.uri); </del> <ins> const relativePath = getRelativePath(getDocumentDir(docUri), uri.uri); </ins> const urlText = relativePath ?? uri.str; snippet.appendText(`url(${urlText})`);


Question:
a workspace: and drop into Expected Inserts Actual Inserts
Closing as fixed in main and release branch

} } <del> function getRelativePath(file: vscode.Uri): string | undefined { const dir = getDocumentDir(file); if (dir && dir.scheme === file.scheme && dir.authority === file.authority) { if (file.scheme === Schemes.file) { </del> <ins> function getRelativePath(fromFile: vscode.Uri | undefined, toFile: vscode.Uri): string | undefined { if (fromFile && fromFile.scheme === toFile.scheme && fromFile.authority === toFile.authority) { if (toFile.scheme === Schemes.file) { </ins> // On windows, we must use the native `path.relative` to generate the relative path // so that drive-letters are resolved cast insensitively. However we then want to // convert back to a posix path to insert in to the document <del> const relativePath = path.relative(dir.fsPath, file.fsPath); </del> <ins> const relativePath = path.relative(fromFile.fsPath, toFile.fsPath); </ins> return path.posix.normalize(relativePath.split(path.sep).join(path.posix.sep)); } <del> return path.posix.relative(dir.path, file.path); </del> <ins> return path.posix.relative(fromFile.path, toFile.path); </ins> } return undefined;


Question:
a workspace: and drop into Expected Inserts Actual Inserts
Closing as fixed in main and release branch


Question:
a workspace: and drop into Expected Inserts Actual Inserts
Closing as fixed in main and release branch


Question:
a workspace: and drop into Expected Inserts Actual Inserts
Closing as fixed in main and release branch


Question:
a workspace: and drop into Expected Inserts Actual Inserts
Closing as fixed in main and release branch


Question:
<!-- 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.92.0, commit OS Version: Windows 10 Enterprise, 22H2 build .4651 Error message: Steps to Reproduce: a new VS code window ! a new file and drag out to make another window ! "Create New Terminal in Editor Area" on that new window ! error will show up ! "Try Again" will reload the terminal, but it doesn't accept inputs, cannot type anything there ! Creating terminal in main window and drag it to side windows does work, but I have to do that with every window reload. Yesterday I could still use terminals in side windows like normal, this only occured after updating to 1.92 July update Thanks for reading :)
! Facing same issue
coming from xterm here I think !
I have the same problem on Fedora 40 Sway. After I click , it will create a non-interoperable terminal.
I'm also having this issue, I thought it might be a problem with WSL but it started for me after updating to VSCode 1.92.0 !
QUICK FIX!!! Just create a new In-window terminal and drag it to the new terminal window.
Will this be hotfixed or should we downgrade?
sorry this won't get a patch release as there's a few workarounds. To downgrade in the meantime you can grab 1.91.1 here , you'll also want to set
Hi. Didn't do the trick for me. Other hack: Ctrl+J (new term in main window) Ctrl + Shift + P Terminal: Move Into New Window Drag & Drop into wanted window. Cumbersom many many times a day.

"@vscode/windows-mutex": "^0.5.0", "@vscode/windows-process-tree": "^0.6.0", "@vscode/windows-registry": "^1.1.0", <del> "@xterm/addon-clipboard": "0.2.0-beta.34", "@xterm/addon-image": "0.9.0-beta.51", "@xterm/addon-search": "0.16.0-beta.51", "@xterm/addon-serialize": "0.14.0-beta.51", "@xterm/addon-unicode11": "0.9.0-beta.51", "@xterm/addon-webgl": "0.19.0-beta.51", "@xterm/headless": "5.6.0-beta.51", "@xterm/xterm": "5.6.0-beta.51", </del> <ins> "@xterm/addon-clipboard": "0.2.0-beta.35", "@xterm/addon-image": "0.9.0-beta.52", "@xterm/addon-search": "0.16.0-beta.52", "@xterm/addon-serialize": "0.14.0-beta.52", "@xterm/addon-unicode11": "0.9.0-beta.52", "@xterm/addon-webgl": "0.19.0-beta.52", "@xterm/headless": "5.6.0-beta.52", "@xterm/xterm": "5.6.0-beta.52", </ins> "http-proxy-agent": "^7.0.0", "https-proxy-agent": "^7.0.2", "jschardet": "3.1.3",


Question:
<!-- 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.92.0, commit OS Version: Windows 10 Enterprise, 22H2 build .4651 Error message: Steps to Reproduce: a new VS code window ! a new file and drag out to make another window ! "Create New Terminal in Editor Area" on that new window ! error will show up ! "Try Again" will reload the terminal, but it doesn't accept inputs, cannot type anything there ! Creating terminal in main window and drag it to side windows does work, but I have to do that with every window reload. Yesterday I could still use terminals in side windows like normal, this only occured after updating to 1.92 July update Thanks for reading :)
! Facing same issue
coming from xterm here I think !
I have the same problem on Fedora 40 Sway. After I click , it will create a non-interoperable terminal.
I'm also having this issue, I thought it might be a problem with WSL but it started for me after updating to VSCode 1.92.0 !
QUICK FIX!!! Just create a new In-window terminal and drag it to the new terminal window.
Will this be hotfixed or should we downgrade?
sorry this won't get a patch release as there's a few workarounds. To downgrade in the meantime you can grab 1.91.1 here , you'll also want to set
Hi. Didn't do the trick for me. Other hack: Ctrl+J (new term in main window) Ctrl + Shift + P Terminal: Move Into New Window Drag & Drop into wanted window. Cumbersom many many times a day.

"@vscode/vscode-languagedetection": "1.0.21", "@vscode/windows-process-tree": "^0.6.0", "@vscode/windows-registry": "^1.1.0", <del> "@xterm/addon-clipboard": "0.2.0-beta.34", "@xterm/addon-image": "0.9.0-beta.51", "@xterm/addon-search": "0.16.0-beta.51", "@xterm/addon-serialize": "0.14.0-beta.51", "@xterm/addon-unicode11": "0.9.0-beta.51", "@xterm/addon-webgl": "0.19.0-beta.51", "@xterm/headless": "5.6.0-beta.51", "@xterm/xterm": "5.6.0-beta.51", </del> <ins> "@xterm/addon-clipboard": "0.2.0-beta.35", "@xterm/addon-image": "0.9.0-beta.52", "@xterm/addon-search": "0.16.0-beta.52", "@xterm/addon-serialize": "0.14.0-beta.52", "@xterm/addon-unicode11": "0.9.0-beta.52", "@xterm/addon-webgl": "0.19.0-beta.52", "@xterm/headless": "5.6.0-beta.52", "@xterm/xterm": "5.6.0-beta.52", </ins> "cookie": "^0.4.0", "http-proxy-agent": "^7.0.0", "https-proxy-agent": "^7.0.2",


Question:
<!-- 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.92.0, commit OS Version: Windows 10 Enterprise, 22H2 build .4651 Error message: Steps to Reproduce: a new VS code window ! a new file and drag out to make another window ! "Create New Terminal in Editor Area" on that new window ! error will show up ! "Try Again" will reload the terminal, but it doesn't accept inputs, cannot type anything there ! Creating terminal in main window and drag it to side windows does work, but I have to do that with every window reload. Yesterday I could still use terminals in side windows like normal, this only occured after updating to 1.92 July update Thanks for reading :)
! Facing same issue
coming from xterm here I think !
I have the same problem on Fedora 40 Sway. After I click , it will create a non-interoperable terminal.
I'm also having this issue, I thought it might be a problem with WSL but it started for me after updating to VSCode 1.92.0 !
QUICK FIX!!! Just create a new In-window terminal and drag it to the new terminal window.
Will this be hotfixed or should we downgrade?
sorry this won't get a patch release as there's a few workarounds. To downgrade in the meantime you can grab 1.91.1 here , you'll also want to set
Hi. Didn't do the trick for me. Other hack: Ctrl+J (new term in main window) Ctrl + Shift + P Terminal: Move Into New Window Drag & Drop into wanted window. Cumbersom many many times a day.

"@vscode/iconv-lite-umd": "0.7.0", "@vscode/tree-sitter-wasm": "^0.0.1", "@vscode/vscode-languagedetection": "1.0.21", <del> "@xterm/addon-clipboard": "0.2.0-beta.34", "@xterm/addon-image": "0.9.0-beta.51", "@xterm/addon-search": "0.16.0-beta.51", "@xterm/addon-serialize": "0.14.0-beta.51", "@xterm/addon-unicode11": "0.9.0-beta.51", "@xterm/addon-webgl": "0.19.0-beta.51", "@xterm/xterm": "5.6.0-beta.51", </del> <ins> "@xterm/addon-clipboard": "0.2.0-beta.35", "@xterm/addon-image": "0.9.0-beta.52", "@xterm/addon-search": "0.16.0-beta.52", "@xterm/addon-serialize": "0.14.0-beta.52", "@xterm/addon-unicode11": "0.9.0-beta.52", "@xterm/addon-webgl": "0.19.0-beta.52", "@xterm/xterm": "5.6.0-beta.52", </ins> "jschardet": "3.1.3", "tas-client-umd": "0.2.0", "vscode-oniguruma": "1.7.0",


Question:
<!-- 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.92.0, commit OS Version: Windows 10 Enterprise, 22H2 build .4651 Error message: Steps to Reproduce: a new VS code window ! a new file and drag out to make another window ! "Create New Terminal in Editor Area" on that new window ! error will show up ! "Try Again" will reload the terminal, but it doesn't accept inputs, cannot type anything there ! Creating terminal in main window and drag it to side windows does work, but I have to do that with every window reload. Yesterday I could still use terminals in side windows like normal, this only occured after updating to 1.92 July update Thanks for reading :)
! Facing same issue
coming from xterm here I think !
I have the same problem on Fedora 40 Sway. After I click , it will create a non-interoperable terminal.
I'm also having this issue, I thought it might be a problem with WSL but it started for me after updating to VSCode 1.92.0 !
QUICK FIX!!! Just create a new In-window terminal and drag it to the new terminal window.
Will this be hotfixed or should we downgrade?
sorry this won't get a patch release as there's a few workarounds. To downgrade in the meantime you can grab 1.91.1 here , you'll also want to set
Hi. Didn't do the trick for me. Other hack: Ctrl+J (new term in main window) Ctrl + Shift + P Terminal: Move Into New Window Drag & Drop into wanted window. Cumbersom many many times a day.

resolved "https://registry.yarnpkg.com/@vscode/vscode-languagedetection/-/vscode-languagedetection-1.0.21.tgz#89b48f293f6aa3341bb888c1118d16ff13b032d3" integrity sha512-zSUH9HYCw5qsCtd7b31yqkpaCU6jhtkKLkvOOA8yTrIRfBSOFb8PPhgmMicD7B/m+t4PwOJXzU1XDtrM9Fd3/g== <del> "@xterm/addon-clipboard@0.2.0-beta.34": version "0.2.0-beta.34" resolved "https://registry.yarnpkg.com/@xterm/addon-clipboard/-/addon-clipboard-0.2.0-beta.34.tgz#9a753601e69d3f9aad10e6d22b3a3d05be237d6a" integrity sha512-Iduj2jGO37VkFLrRzxK5SkE7b2bAPaIvkvcSnw5JCdsvu9cjmPy7jgJkvUu54Tltzt55X+YTkQQ2GIKHqcor8A== </del> <ins> "@xterm/addon-clipboard@0.2.0-beta.35": version "0.2.0-beta.35" resolved "https://registry.yarnpkg.com/@xterm/addon-clipboard/-/addon-clipboard-0.2.0-beta.35.tgz#4c9b553ea63ce02a3c8075fea7df1637d52092ef" integrity sha512-B8AulZEjsfvSEaLKp8oyRu7yJ7FJb5R3W0wpPbI/rOMVAuBwxDJsz0CxLvJUXnJX7OJwd5cjnyTnEcXJfMJycA== </ins> dependencies: js-base64 "^3.7.5" <del> "@xterm/addon-image@0.9.0-beta.51": version "0.9.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-image/-/addon-image-0.9.0-beta.51.tgz#832be645ab04de3ab1af28aa37d4c3bcc72d9960" integrity sha512-u8f0C8Kae8d8jGo2OGaxy1j4hvXOij41ZUp5fNsGL3quYufwmtVixVHUnc7WfEMVdSaSBNqfDXE+qpV4i3C3ng== "@xterm/addon-search@0.16.0-beta.51": version "0.16.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-search/-/addon-search-0.16.0-beta.51.tgz#4595c6294287a2560abe4b76f6ef2f0aafd2f05e" integrity sha512-DhnNDP9bAd/7/9TW+0N3BUaF/6Fpv/6RiIiromlzSu+6g1VDmuWsd8JpeTxErOCoWZuEMLpVVje9ky3yj8pN9A== "@xterm/addon-serialize@0.14.0-beta.51": version "0.14.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-serialize/-/addon-serialize-0.14.0-beta.51.tgz#0c9802ba94018e94a727abc9e977a2349279468f" integrity sha512-EjKIOuzSP+HCtk05iwHk0N3jYfsx81bKRv4pfGXKsc3rN0H6gQ+bvx/abSkndtgIjKtee2cy1H8pggMaezmzIA== "@xterm/addon-unicode11@0.9.0-beta.51": version "0.9.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-unicode11/-/addon-unicode11-0.9.0-beta.51.tgz#c2f2b1ad14b2481648ca7deaa0bf2923d987e2e6" integrity sha512-6FmA4MOue7SDYjSLmuG8rZC2eeVZ+YjhWEXWiUAAoiZ9X11j9HMdOhWcutca3crAMc6mrHfjx6fNsUxwtELMkQ== "@xterm/addon-webgl@0.19.0-beta.51": version "0.19.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-webgl/-/addon-webgl-0.19.0-beta.51.tgz#14cb115d45c140525eb51427e236189dd800c20c" integrity sha512-oO6yVuVA+9kNA47bT2c2IkGj9eLWvV6mEEo8wHKN7WXyYUFgw6ivAgmdrIdnKh679xbCq7th3GfcESwwQFH/sg== "@xterm/xterm@5.6.0-beta.51": version "5.6.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/xterm/-/xterm-5.6.0-beta.51.tgz#3b9a5016d9588eb0a05226f6fc090b48a85b7698" integrity sha512-0i9gkiP2hhCMIRk5ACM8LJXHRd1umzC27ZDHD8n14vutrQRgdW4ENvCdmrWHiVJy4Ui1t7m70zdgg72shOgcEA== </del> <ins> "@xterm/addon-image@0.9.0-beta.52": version "0.9.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-image/-/addon-image-0.9.0-beta.52.tgz#a3115a50f884e5ba2f8ce09118a3d7e833fceb7b" integrity sha512-1fWhnCIvLeO0aQ3CKqkTB9ye1bUsocpgFdDOgmwfW4XhLXpvu+QcyMGQMtWJHt8JWBN2w0cgR9eyfKw7orN+9Q== "@xterm/addon-search@0.16.0-beta.52": version "0.16.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-search/-/addon-search-0.16.0-beta.52.tgz#f8c77629b95ceff7d6b93d95c4b085857f405470" integrity sha512-ZLVh0O91dcjxCjrU3vadl+40Z/mBnYXhKNA58oU/dGWFtFxtUB9SaZoOUtBvnfDpQIloYAK6raC2AfVsKHzD8A== "@xterm/addon-serialize@0.14.0-beta.52": version "0.14.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-serialize/-/addon-serialize-0.14.0-beta.52.tgz#19708cdd2895ddbd983b771ae9d14d7bc54cf7c9" integrity sha512-1+ckKya1OURFmELH1Tjjoxz3Gnj78Dxj+NNRrEunfINkvyzaY+n8wT28FQxIlU5gJq+a0VGvlhNgTkMwgOn6aw== "@xterm/addon-unicode11@0.9.0-beta.52": version "0.9.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-unicode11/-/addon-unicode11-0.9.0-beta.52.tgz#15afdf03c20d2e46b4eca68bd461eea71c8dd37f" integrity sha512-5tZR/8c+vf0YNSYS6B9pEv8gyWWZpPYOf/BRQDkTGtYAnFf04MzggVE/U7tKUXGDzBhzwTPODq5qPNTX1xpGgw== "@xterm/addon-webgl@0.19.0-beta.52": version "0.19.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-webgl/-/addon-webgl-0.19.0-beta.52.tgz#695b20a5fa88ff92e115624149592080fad59594" integrity sha512-kbPO9iR166xW8qgRkYmKX2Vu0kQHXpxYLQ9jY/01e5kvNrI/rqRDV63FIq14ncOi7N3+dmTuUkjvbg8anCpuIw== "@xterm/xterm@5.6.0-beta.52": version "5.6.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/xterm/-/xterm-5.6.0-beta.52.tgz#ed7456a8b78ea1d00431737d078b5ab0bafbcdfe" integrity sha512-aZh8IBdZPb2N4NjTt/fQ/C90z/PM3Zxkfoqhmlsp5+v3Otmyw5kd3DepeHK1SFW/pz0/xdj4KFgX8t8Y2lDRbA== </ins> js-base64@^3.7.5: version "3.7.7"


Question:
<!-- 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.92.0, commit OS Version: Windows 10 Enterprise, 22H2 build .4651 Error message: Steps to Reproduce: a new VS code window ! a new file and drag out to make another window ! "Create New Terminal in Editor Area" on that new window ! error will show up ! "Try Again" will reload the terminal, but it doesn't accept inputs, cannot type anything there ! Creating terminal in main window and drag it to side windows does work, but I have to do that with every window reload. Yesterday I could still use terminals in side windows like normal, this only occured after updating to 1.92 July update Thanks for reading :)
! Facing same issue
coming from xterm here I think !
I have the same problem on Fedora 40 Sway. After I click , it will create a non-interoperable terminal.
I'm also having this issue, I thought it might be a problem with WSL but it started for me after updating to VSCode 1.92.0 !
QUICK FIX!!! Just create a new In-window terminal and drag it to the new terminal window.
Will this be hotfixed or should we downgrade?
sorry this won't get a patch release as there's a few workarounds. To downgrade in the meantime you can grab 1.91.1 here , you'll also want to set
Hi. Didn't do the trick for me. Other hack: Ctrl+J (new term in main window) Ctrl + Shift + P Terminal: Move Into New Window Drag & Drop into wanted window. Cumbersom many many times a day.

resolved "https://registry.yarnpkg.com/@vscode/windows-registry/-/windows-registry-1.1.0.tgz#03dace7c29c46f658588b9885b9580e453ad21f9" integrity sha512-5AZzuWJpGscyiMOed0IuyEwt6iKmV5Us7zuwCDCFYMIq7tsvooO9BUiciywsvuthGz6UG4LSpeDeCxvgMVhnIw== <del> "@xterm/addon-clipboard@0.2.0-beta.34": version "0.2.0-beta.34" resolved "https://registry.yarnpkg.com/@xterm/addon-clipboard/-/addon-clipboard-0.2.0-beta.34.tgz#9a753601e69d3f9aad10e6d22b3a3d05be237d6a" integrity sha512-Iduj2jGO37VkFLrRzxK5SkE7b2bAPaIvkvcSnw5JCdsvu9cjmPy7jgJkvUu54Tltzt55X+YTkQQ2GIKHqcor8A== </del> <ins> "@xterm/addon-clipboard@0.2.0-beta.35": version "0.2.0-beta.35" resolved "https://registry.yarnpkg.com/@xterm/addon-clipboard/-/addon-clipboard-0.2.0-beta.35.tgz#4c9b553ea63ce02a3c8075fea7df1637d52092ef" integrity sha512-B8AulZEjsfvSEaLKp8oyRu7yJ7FJb5R3W0wpPbI/rOMVAuBwxDJsz0CxLvJUXnJX7OJwd5cjnyTnEcXJfMJycA== </ins> dependencies: js-base64 "^3.7.5" <del> "@xterm/addon-image@0.9.0-beta.51": version "0.9.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-image/-/addon-image-0.9.0-beta.51.tgz#832be645ab04de3ab1af28aa37d4c3bcc72d9960" integrity sha512-u8f0C8Kae8d8jGo2OGaxy1j4hvXOij41ZUp5fNsGL3quYufwmtVixVHUnc7WfEMVdSaSBNqfDXE+qpV4i3C3ng== "@xterm/addon-search@0.16.0-beta.51": version "0.16.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-search/-/addon-search-0.16.0-beta.51.tgz#4595c6294287a2560abe4b76f6ef2f0aafd2f05e" integrity sha512-DhnNDP9bAd/7/9TW+0N3BUaF/6Fpv/6RiIiromlzSu+6g1VDmuWsd8JpeTxErOCoWZuEMLpVVje9ky3yj8pN9A== "@xterm/addon-serialize@0.14.0-beta.51": version "0.14.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-serialize/-/addon-serialize-0.14.0-beta.51.tgz#0c9802ba94018e94a727abc9e977a2349279468f" integrity sha512-EjKIOuzSP+HCtk05iwHk0N3jYfsx81bKRv4pfGXKsc3rN0H6gQ+bvx/abSkndtgIjKtee2cy1H8pggMaezmzIA== "@xterm/addon-unicode11@0.9.0-beta.51": version "0.9.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-unicode11/-/addon-unicode11-0.9.0-beta.51.tgz#c2f2b1ad14b2481648ca7deaa0bf2923d987e2e6" integrity sha512-6FmA4MOue7SDYjSLmuG8rZC2eeVZ+YjhWEXWiUAAoiZ9X11j9HMdOhWcutca3crAMc6mrHfjx6fNsUxwtELMkQ== "@xterm/addon-webgl@0.19.0-beta.51": version "0.19.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-webgl/-/addon-webgl-0.19.0-beta.51.tgz#14cb115d45c140525eb51427e236189dd800c20c" integrity sha512-oO6yVuVA+9kNA47bT2c2IkGj9eLWvV6mEEo8wHKN7WXyYUFgw6ivAgmdrIdnKh679xbCq7th3GfcESwwQFH/sg== "@xterm/headless@5.6.0-beta.51": version "5.6.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/headless/-/headless-5.6.0-beta.51.tgz#76ff548a88305fe476a7d3f991331c0393c0af45" integrity sha512-ehd4L3c28mQKVEd5cMmUzR1f1XcAVbJukfR1YiD7ohjphHUxSsg6mYb5qGIh50SsQsDI6wHYuIvmNSjvNgHVOw== "@xterm/xterm@5.6.0-beta.51": version "5.6.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/xterm/-/xterm-5.6.0-beta.51.tgz#3b9a5016d9588eb0a05226f6fc090b48a85b7698" integrity sha512-0i9gkiP2hhCMIRk5ACM8LJXHRd1umzC27ZDHD8n14vutrQRgdW4ENvCdmrWHiVJy4Ui1t7m70zdgg72shOgcEA== </del> <ins> "@xterm/addon-image@0.9.0-beta.52": version "0.9.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-image/-/addon-image-0.9.0-beta.52.tgz#a3115a50f884e5ba2f8ce09118a3d7e833fceb7b" integrity sha512-1fWhnCIvLeO0aQ3CKqkTB9ye1bUsocpgFdDOgmwfW4XhLXpvu+QcyMGQMtWJHt8JWBN2w0cgR9eyfKw7orN+9Q== "@xterm/addon-search@0.16.0-beta.52": version "0.16.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-search/-/addon-search-0.16.0-beta.52.tgz#f8c77629b95ceff7d6b93d95c4b085857f405470" integrity sha512-ZLVh0O91dcjxCjrU3vadl+40Z/mBnYXhKNA58oU/dGWFtFxtUB9SaZoOUtBvnfDpQIloYAK6raC2AfVsKHzD8A== "@xterm/addon-serialize@0.14.0-beta.52": version "0.14.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-serialize/-/addon-serialize-0.14.0-beta.52.tgz#19708cdd2895ddbd983b771ae9d14d7bc54cf7c9" integrity sha512-1+ckKya1OURFmELH1Tjjoxz3Gnj78Dxj+NNRrEunfINkvyzaY+n8wT28FQxIlU5gJq+a0VGvlhNgTkMwgOn6aw== "@xterm/addon-unicode11@0.9.0-beta.52": version "0.9.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-unicode11/-/addon-unicode11-0.9.0-beta.52.tgz#15afdf03c20d2e46b4eca68bd461eea71c8dd37f" integrity sha512-5tZR/8c+vf0YNSYS6B9pEv8gyWWZpPYOf/BRQDkTGtYAnFf04MzggVE/U7tKUXGDzBhzwTPODq5qPNTX1xpGgw== "@xterm/addon-webgl@0.19.0-beta.52": version "0.19.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-webgl/-/addon-webgl-0.19.0-beta.52.tgz#695b20a5fa88ff92e115624149592080fad59594" integrity sha512-kbPO9iR166xW8qgRkYmKX2Vu0kQHXpxYLQ9jY/01e5kvNrI/rqRDV63FIq14ncOi7N3+dmTuUkjvbg8anCpuIw== "@xterm/headless@5.6.0-beta.52": version "5.6.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/headless/-/headless-5.6.0-beta.52.tgz#7f934a7d7c5bbf88e2d78c22317cd2464bc9638a" integrity sha512-f4QITQwotblRLW6YOHnK801wHJWfFDnjD7jUEwaaAXtSp32xH3jguWnMP9/uuQX45q9ndjDjnm1t5aXX7gwqBQ== "@xterm/xterm@5.6.0-beta.52": version "5.6.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/xterm/-/xterm-5.6.0-beta.52.tgz#ed7456a8b78ea1d00431737d078b5ab0bafbcdfe" integrity sha512-aZh8IBdZPb2N4NjTt/fQ/C90z/PM3Zxkfoqhmlsp5+v3Otmyw5kd3DepeHK1SFW/pz0/xdj4KFgX8t8Y2lDRbA== </ins> agent-base@^7.0.1, agent-base@^7.0.2, agent-base@^7.1.0: version "7.1.0"


Question:
<!-- 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.92.0, commit OS Version: Windows 10 Enterprise, 22H2 build .4651 Error message: Steps to Reproduce: a new VS code window ! a new file and drag out to make another window ! "Create New Terminal in Editor Area" on that new window ! error will show up ! "Try Again" will reload the terminal, but it doesn't accept inputs, cannot type anything there ! Creating terminal in main window and drag it to side windows does work, but I have to do that with every window reload. Yesterday I could still use terminals in side windows like normal, this only occured after updating to 1.92 July update Thanks for reading :)
! Facing same issue
coming from xterm here I think !
I have the same problem on Fedora 40 Sway. After I click , it will create a non-interoperable terminal.
I'm also having this issue, I thought it might be a problem with WSL but it started for me after updating to VSCode 1.92.0 !
QUICK FIX!!! Just create a new In-window terminal and drag it to the new terminal window.
Will this be hotfixed or should we downgrade?
sorry this won't get a patch release as there's a few workarounds. To downgrade in the meantime you can grab 1.91.1 here , you'll also want to set
Hi. Didn't do the trick for me. Other hack: Ctrl+J (new term in main window) Ctrl + Shift + P Terminal: Move Into New Window Drag & Drop into wanted window. Cumbersom many many times a day.

resolved "https://registry.yarnpkg.com/@webpack-cli/serve/-/serve-2.0.5.tgz#325db42395cd49fe6c14057f9a900e427df8810e" integrity sha512-lqaoKnRYBdo1UgDX8uF24AfGMifWK19TxPmM5FHc2vAGxrJ/qtyUyFBWoY1tISZdelsQ5fBcOusifo5o5wSJxQ== <del> "@xterm/addon-clipboard@0.2.0-beta.34": version "0.2.0-beta.34" resolved "https://registry.yarnpkg.com/@xterm/addon-clipboard/-/addon-clipboard-0.2.0-beta.34.tgz#9a753601e69d3f9aad10e6d22b3a3d05be237d6a" integrity sha512-Iduj2jGO37VkFLrRzxK5SkE7b2bAPaIvkvcSnw5JCdsvu9cjmPy7jgJkvUu54Tltzt55X+YTkQQ2GIKHqcor8A== </del> <ins> "@xterm/addon-clipboard@0.2.0-beta.35": version "0.2.0-beta.35" resolved "https://registry.yarnpkg.com/@xterm/addon-clipboard/-/addon-clipboard-0.2.0-beta.35.tgz#4c9b553ea63ce02a3c8075fea7df1637d52092ef" integrity sha512-B8AulZEjsfvSEaLKp8oyRu7yJ7FJb5R3W0wpPbI/rOMVAuBwxDJsz0CxLvJUXnJX7OJwd5cjnyTnEcXJfMJycA== </ins> dependencies: js-base64 "^3.7.5" <del> "@xterm/addon-image@0.9.0-beta.51": version "0.9.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-image/-/addon-image-0.9.0-beta.51.tgz#832be645ab04de3ab1af28aa37d4c3bcc72d9960" integrity sha512-u8f0C8Kae8d8jGo2OGaxy1j4hvXOij41ZUp5fNsGL3quYufwmtVixVHUnc7WfEMVdSaSBNqfDXE+qpV4i3C3ng== "@xterm/addon-search@0.16.0-beta.51": version "0.16.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-search/-/addon-search-0.16.0-beta.51.tgz#4595c6294287a2560abe4b76f6ef2f0aafd2f05e" integrity sha512-DhnNDP9bAd/7/9TW+0N3BUaF/6Fpv/6RiIiromlzSu+6g1VDmuWsd8JpeTxErOCoWZuEMLpVVje9ky3yj8pN9A== "@xterm/addon-serialize@0.14.0-beta.51": version "0.14.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-serialize/-/addon-serialize-0.14.0-beta.51.tgz#0c9802ba94018e94a727abc9e977a2349279468f" integrity sha512-EjKIOuzSP+HCtk05iwHk0N3jYfsx81bKRv4pfGXKsc3rN0H6gQ+bvx/abSkndtgIjKtee2cy1H8pggMaezmzIA== "@xterm/addon-unicode11@0.9.0-beta.51": version "0.9.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-unicode11/-/addon-unicode11-0.9.0-beta.51.tgz#c2f2b1ad14b2481648ca7deaa0bf2923d987e2e6" integrity sha512-6FmA4MOue7SDYjSLmuG8rZC2eeVZ+YjhWEXWiUAAoiZ9X11j9HMdOhWcutca3crAMc6mrHfjx6fNsUxwtELMkQ== "@xterm/addon-webgl@0.19.0-beta.51": version "0.19.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/addon-webgl/-/addon-webgl-0.19.0-beta.51.tgz#14cb115d45c140525eb51427e236189dd800c20c" integrity sha512-oO6yVuVA+9kNA47bT2c2IkGj9eLWvV6mEEo8wHKN7WXyYUFgw6ivAgmdrIdnKh679xbCq7th3GfcESwwQFH/sg== "@xterm/headless@5.6.0-beta.51": version "5.6.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/headless/-/headless-5.6.0-beta.51.tgz#76ff548a88305fe476a7d3f991331c0393c0af45" integrity sha512-ehd4L3c28mQKVEd5cMmUzR1f1XcAVbJukfR1YiD7ohjphHUxSsg6mYb5qGIh50SsQsDI6wHYuIvmNSjvNgHVOw== "@xterm/xterm@5.6.0-beta.51": version "5.6.0-beta.51" resolved "https://registry.yarnpkg.com/@xterm/xterm/-/xterm-5.6.0-beta.51.tgz#3b9a5016d9588eb0a05226f6fc090b48a85b7698" integrity sha512-0i9gkiP2hhCMIRk5ACM8LJXHRd1umzC27ZDHD8n14vutrQRgdW4ENvCdmrWHiVJy4Ui1t7m70zdgg72shOgcEA== </del> <ins> "@xterm/addon-image@0.9.0-beta.52": version "0.9.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-image/-/addon-image-0.9.0-beta.52.tgz#a3115a50f884e5ba2f8ce09118a3d7e833fceb7b" integrity sha512-1fWhnCIvLeO0aQ3CKqkTB9ye1bUsocpgFdDOgmwfW4XhLXpvu+QcyMGQMtWJHt8JWBN2w0cgR9eyfKw7orN+9Q== "@xterm/addon-search@0.16.0-beta.52": version "0.16.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-search/-/addon-search-0.16.0-beta.52.tgz#f8c77629b95ceff7d6b93d95c4b085857f405470" integrity sha512-ZLVh0O91dcjxCjrU3vadl+40Z/mBnYXhKNA58oU/dGWFtFxtUB9SaZoOUtBvnfDpQIloYAK6raC2AfVsKHzD8A== "@xterm/addon-serialize@0.14.0-beta.52": version "0.14.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-serialize/-/addon-serialize-0.14.0-beta.52.tgz#19708cdd2895ddbd983b771ae9d14d7bc54cf7c9" integrity sha512-1+ckKya1OURFmELH1Tjjoxz3Gnj78Dxj+NNRrEunfINkvyzaY+n8wT28FQxIlU5gJq+a0VGvlhNgTkMwgOn6aw== "@xterm/addon-unicode11@0.9.0-beta.52": version "0.9.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-unicode11/-/addon-unicode11-0.9.0-beta.52.tgz#15afdf03c20d2e46b4eca68bd461eea71c8dd37f" integrity sha512-5tZR/8c+vf0YNSYS6B9pEv8gyWWZpPYOf/BRQDkTGtYAnFf04MzggVE/U7tKUXGDzBhzwTPODq5qPNTX1xpGgw== "@xterm/addon-webgl@0.19.0-beta.52": version "0.19.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/addon-webgl/-/addon-webgl-0.19.0-beta.52.tgz#695b20a5fa88ff92e115624149592080fad59594" integrity sha512-kbPO9iR166xW8qgRkYmKX2Vu0kQHXpxYLQ9jY/01e5kvNrI/rqRDV63FIq14ncOi7N3+dmTuUkjvbg8anCpuIw== "@xterm/headless@5.6.0-beta.52": version "5.6.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/headless/-/headless-5.6.0-beta.52.tgz#7f934a7d7c5bbf88e2d78c22317cd2464bc9638a" integrity sha512-f4QITQwotblRLW6YOHnK801wHJWfFDnjD7jUEwaaAXtSp32xH3jguWnMP9/uuQX45q9ndjDjnm1t5aXX7gwqBQ== "@xterm/xterm@5.6.0-beta.52": version "5.6.0-beta.52" resolved "https://registry.yarnpkg.com/@xterm/xterm/-/xterm-5.6.0-beta.52.tgz#ed7456a8b78ea1d00431737d078b5ab0bafbcdfe" integrity sha512-aZh8IBdZPb2N4NjTt/fQ/C90z/PM3Zxkfoqhmlsp5+v3Otmyw5kd3DepeHK1SFW/pz0/xdj4KFgX8t8Y2lDRbA== </ins> "@xtuc/ieee754@^1.2.0": version "1.2.0"


Question: Note that quick pick instances and their events are disposables. Noticed a few cases of missing:

return true; } <del> const quickPick = this._quickInputService.createQuickPick<KernelQuickPickItem>({ useSeparators: true }); </del> <ins> const localDisposableStore = new DisposableStore(); const quickPick = localDisposableStore.add(this._quickInputService.createQuickPick<KernelQuickPickItem>({ useSeparators: true })); </ins> const quickPickItems = this._getKernelPickerQuickPickItems(notebook, matchResult, this._notebookKernelService, scopedContextKeyService); if (quickPickItems.length === 1 && supportAutoRun(quickPickItems[0]) && !skipAutoRun) { <del> return await this._handleQuickPick(editor, quickPickItems[0], quickPickItems as KernelQuickPickItem[]); </del> <ins> const picked = await this._handleQuickPick(editor, quickPickItems[0], quickPickItems as KernelQuickPickItem[]); localDisposableStore.dispose(); return picked; </ins> } quickPick.items = quickPickItems;


Question: Note that quick pick instances and their events are disposables. Noticed a few cases of missing:

}, this); const pick = await new Promise<{ selected: KernelQuickPickItem | undefined; items: KernelQuickPickItem[] }>((resolve, reject) => { <del> quickPick.onDidAccept(() => { </del> <ins> localDisposableStore.add(quickPick.onDidAccept(() => { </ins> const item = quickPick.selectedItems[0]; if (item) { resolve({ selected: item, items: quickPick.items as KernelQuickPickItem[] });


Question: Note that quick pick instances and their events are disposables. Noticed a few cases of missing:

} quickPick.hide(); <del> }); </del> <ins> })); </ins> <del> quickPick.onDidHide(() => { </del> <ins> localDisposableStore.add(quickPick.onDidHide(() => { </ins> kernelDetectionTaskListener.dispose(); kernelChangeEventListener.dispose(); quickPick.dispose(); resolve({ selected: undefined, items: quickPick.items as KernelQuickPickItem[] }); <del> }); </del> <ins> })); </ins> quickPick.show(); }); <ins> localDisposableStore.dispose(); </ins> if (pick.selected) { return await this._handleQuickPick(editor, pick.selected, pick.items); }


Question: Note that quick pick instances and their events are disposables. Noticed a few cases of missing:

private async displaySelectAnotherQuickPick(editor: IActiveNotebookEditor, kernelListEmpty: boolean): Promise<boolean> { const notebook: NotebookTextModel = editor.textModel; const disposables = new DisposableStore(); <del> const quickPick = this._quickInputService.createQuickPick<KernelQuickPickItem>({ useSeparators: true }); </del> <ins> const quickPick = disposables.add(this._quickInputService.createQuickPick<KernelQuickPickItem>({ useSeparators: true })); </ins> const quickPickItem = await new Promise<KernelQuickPickItem | IQuickInputButton | undefined>(resolve => { // select from kernel sources quickPick.title = kernelListEmpty ? localize('select', "Select Kernel") : localize('selectAnotherKernel', "Select Another Kernel");


Question: Note that quick pick instances and their events are disposables. Noticed a few cases of missing:

resolve(button); } })); <del> quickPick.onDidTriggerItemButton(async (e) => { </del> <ins> disposables.add(quickPick.onDidTriggerItemButton(async (e) => { </ins> if (isKernelSourceQuickPickItem(e.item) && e.item.documentation !== undefined) { const uri = URI.isUri(e.item.documentation) ? URI.parse(e.item.documentation) : await this._commandService.executeCommand(e.item.documentation); void this._openerService.open(uri, { openExternal: true }); } <del> }); </del> <ins> })); </ins> disposables.add(quickPick.onDidAccept(async () => { resolve(quickPick.selectedItems[0]); }));


Question: Note that quick pick instances and their events are disposables. Noticed a few cases of missing:

private async _selectOneKernel(notebook: NotebookTextModel, source: string, kernels: INotebookKernel[]) { const quickPickItems: QuickPickInput<KernelPick>[] = kernels.map(kernel => toKernelQuickPick(kernel, undefined)); <del> const quickPick = this._quickInputService.createQuickPick<KernelQuickPickItem>({ useSeparators: true }); </del> <ins> const localDisposableStore = new DisposableStore(); const quickPick = localDisposableStore.add(this._quickInputService.createQuickPick<KernelQuickPickItem>({ useSeparators: true })); </ins> quickPick.items = quickPickItems; quickPick.canSelectMany = false; quickPick.title = localize('selectKernelFromExtension', "Select Kernel from {0}", source); <del> quickPick.onDidAccept(async () => { </del> <ins> localDisposableStore.add(quickPick.onDidAccept(async () => { </ins> if (quickPick.selectedItems && quickPick.selectedItems.length > 0 && isKernelPick(quickPick.selectedItems[0])) { await this._selecteKernel(notebook, quickPick.selectedItems[0].kernel); } quickPick.hide(); quickPick.dispose(); <del> }); </del> <ins> })); </ins> <del> quickPick.onDidHide(() => { quickPick.dispose(); }); </del> <ins> localDisposableStore.add(quickPick.onDidHide(() => { localDisposableStore.dispose(); })); </ins> quickPick.show(); }