jiebi/CodeConvo huggingface dataset:
Change:
With that setting set, I am missing the "[Extension Development Host]" title on the window, which is helpful for identifying that special window. In general, I guess the whole is missing - is there a plan to show that along with the menu? If not can we keep the [Extension Development Host] hint somewhere?
Today it only shows on hover. I am open for suggestion but it isn't trivial as the static window title can be very long, is configurable. Maybe show the "special decorations", like [Extension Dev..] etc, in the title menu

Discussion:
} private _updateFromWindowTitle() { <del> this.workspaceTitle.innerText = windowTitle.workspaceName; </del> <ins> // label: just workspace name and optional decorations const { prefix, suffix } = windowTitle.getTitleDecorations(); let label = windowTitle.workspaceName; if (prefix) { label = localize('label1', "{0} {1}", prefix, label); } if (suffix) { label = localize('label2', "{0} {1}", label, suffix); } this.workspaceTitle.innerText = label; // tooltip: full windowTitle </ins> const kb = keybindingService.lookupKeybinding(action.id)?.getLabel(); const title = kb ? localize('title', "Search {0} ({1}) u2014 {2}", windowTitle.workspaceName, kb, windowTitle.value)

} private getWindowTitle(): string { <del> let title = this.doGetWindowTitle(); </del> <ins> let title = this.doGetWindowTitle() || this.productService.nameLong; let { prefix, suffix } = this.getTitleDecorations(); if (prefix) { title = `${prefix} ${title}`; } if (suffix) { title = `${title} ${suffix}`; } // Replace non-space whitespace title = title.replace(/[^S ]/g, ' '); return title; } getTitleDecorations() { let prefix: string | undefined; let suffix: string | undefined; </ins> if (this.properties.prefix) { <del> title = `${this.properties.prefix} ${title || this.productService.nameLong}`; </del> <ins> prefix = this.properties.prefix; } if (this.environmentService.isExtensionDevelopment) { prefix = !prefix ? WindowTitle.NLS_EXTENSION_HOST : `${WindowTitle.NLS_EXTENSION_HOST} - ${prefix}`; </ins> } if (this.properties.isAdmin) { <del> title = `${title || this.productService.nameLong} ${WindowTitle.NLS_USER_IS_ADMIN}`; </del> <ins> suffix = WindowTitle.NLS_USER_IS_ADMIN; </ins> } if (!this.properties.isPure) { <del> title = `${title || this.productService.nameLong} ${WindowTitle.NLS_UNSUPPORTED}`; </del> <ins> suffix = !suffix ? WindowTitle.NLS_UNSUPPORTED : `${suffix} ${WindowTitle.NLS_UNSUPPORTED}`; </ins> } <del> if (this.environmentService.isExtensionDevelopment) { title = `${WindowTitle.NLS_EXTENSION_HOST} - ${title || this.productService.nameLong}`; } // Replace non-space whitespace title = title.replace(/[^S ]/g, ' '); return title; </del> <ins> return { prefix, suffix }; </ins> } updateProperties(properties: ITitleProperties): void {
Change:
Notice how the command is getting created in the console but not in the UI: !
registerDecoration is getting called with the initial command's marker every time
that's bc IE isn't happening !
today, the decoration isn't even showing up for the first command/placeholder
Hoping this will be fixed when and related fixed land
Seems related to , the decoration addon is disposed of immediately on creation now: ! Working on a fix

Discussion:
this._decorationAddon.dispose(); this._decorationAddon = undefined; } <ins> return; </ins> } if (this._decorationAddon) { this._decorationAddon.dispose();

describe('Shell integration', function () { // TODO: Fix on Linux, some distros use sh as the default shell in which case shell integration will fail <del> // TODO: Fix on macOS, not sure reason for failing https://github.com/microsoft/vscode/issues/149757 describe.skip('Decorations', function () { </del> <ins> (process.platform === 'win32' || process.platform === 'linux' ? describe.skip : describe)('Decorations', function () { </ins> describe('Should show default icons', function () { it('Placeholder', async () => { await terminal.createTerminal();
Change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --<!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --VS Code Version: 1.67.1 Operating System: Windows 11 Screen Reader: NVDA Extensions Installed: Put together an extension to quickly demo the bare VS Code UI features without our normal SDK and extension wrappers. "a11y-kit" () Repro Steps: a11y-kit from VS Code Marketplace command palette and run a11y-kit's menu command , select: "Show Quick Picks - Many" and observe. Expected: There should be a way for the screen reader to inform the user that the checkbox to the left of the main input field is used to select all quick pick items. I suppose the screen reader callout might read to the user something like... "select all items checkbox, unchecked" Actual: When entering the quick pick selection screen, all the quick pick items are listed as check-able items as you select over them; however, the select all checkbox next to the main input box has no such similar screen reader callout. When highlighting directly using keyboard, it states that it is a checkbox but does not describe its specific function in the context of the section. Attachments: ! Thank you!

Discussion:
const checkAll = <HTMLInputElement>dom.append(headerContainer, $('input.quick-input-check-all')); checkAll.type = 'checkbox'; <ins> checkAll.setAttribute('aria-label', localize('quickInput.checkAll', "Toggle all checkboxes")); </ins> this._register(dom.addStandardDisposableListener(checkAll, dom.EventType.CHANGE, e => { const checked = checkAll.checked; list.setAllVisibleChecked(checked);
Change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.67.2 OS Version: Windows 11 Pro 21H2 Steps to Reproduce: a monorepo, in our case one that uses Yarn 3. at any non-root package in the NPM Scripts pane. The new unexpected behaviour is the appearance of an "install" script in every non-root package: <img src="https://user-" width="300"I suppose a virtual "install" script might have been nice to have in the monorepo root; instead it appears everywhere except for the monorepo root. Running the script just executes , which has the same behaviour regardless of the working directory in which it's invoked - it just installs all the dependencies for the full monorepo. Adding to does not make this go away. I haven't been able to find any mention of this new feature anywhere, so I'm not sure what the intended behaviour was; but I'm guessing it wasn't this!
We should exclude when its in .
or do you want to take this?
Just please note it's also strange that it shows up in every package except the monorepo root package. Since from anywhere in a monorepo will install the entire monorepo - I would hope an script would only show up in the monorepo root package. Obviously a minor bug, but also the kind of bug I can't fix myself since these parts are closed source :)
Please don't take this as pressure to create a PR , but this view and the tasks it shows are provided by the built in npm extension, which is in fact part of this OSS repo:

Discussion:
result.push({ task, location: new Location(packageJsonUri, nameRange) }); } <del> // always add npm install (without a problem matcher) result.push({ task: await createTask(packageManager, INSTALL_SCRIPT, [INSTALL_SCRIPT], folder, packageJsonUri, 'install dependencies from package', []) }); </del> <ins> if (!workspace.getConfiguration('npm', folder).get<string[]>('scriptExplorerExclude', []).find(e => e.includes('install'))) { result.push({ task: await createTask(packageManager, INSTALL_SCRIPT, [INSTALL_SCRIPT], folder, packageJsonUri, 'install dependencies from package', []) }); } </ins> return result; }
Change:
! Version: 1.68.0-insider (user setup) Commit: Date: 2022-05-19T05:16:03.853Z Electron: 17.4.3 Chromium: 98.0.4758.141 16.13.0 V8: 9.8.177.13-electron.0 OS: Windows_NT x64 10.0.

Discussion:
.monaco-editor .dim-configuration { color: #b1b1b1; } <ins> .codicon-settings-edit:hover { cursor: pointer; } </ins>
Change:
Issue Type: <bBug</bThe Avatar badge always shows <img width="351" alt="image (7)" src="https://user-"Clicking the action to authenticate doesn't dismiss it. VS Code version: Code - Insiders 1.68.0-insider (, 2022-05-20T05:16:17.334Z) OS version: WindowsNT x64 10.0. Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (39)</summaryExtensionVersion ------ vscode-eslint2.2.2 kusto0.3.8 gitlens-insiders2022.5.1705 prettier-vscode9.5.0 codespaces1.8.1 copilot1.22.5957 vscode-pull-request-github0.42.0 go0.33.0 vscode-language-pack-zh-hans1.68.0 python2022.7. vscode-pylance2022.5.2 jupyter2022.5. jupyter-keymap1.0.0 jupyter-renderers1.0.6 vscode-ai0.11. vscode-ai-remote0.13. remote-containers0.236.1 remote-ssh0.80.0 remote-ssh-edit0.80.0 remote-wsl0.66.3 azure-account0.10.1 hexeditor1.9.6 js-debug-nightly2022.5.1817 live-server0.2.12 vscode-github-issue-notebooks0.0.119 vscode-markdown-notebook0.0.26 vscode-selfhost-test-provider0.3.9 vsliveshare1.0.5561 vetur0.35.0 colab-keymap0.0.4 github-issue-notebook-enhancement0.0.1 vscode-code-renderer0.0.2 vscode-jupyter-checkpoint0.0.1 notification-tester2.5.1 rest-book6.0.1 tldraw-vscode1.13.3 shell-runner-notebooks0.0.2 luna-paint0.14.0 vscode-todo-highlight1.0.5 (3 theme extensions excluded) </details<!-- generated by issue reporter --
after reloading, does the go away?
Reloading fixes the issue for me

Discussion:
const scopesSeen = new Set<string>(); const sessionPromises = sessionData.map(async (session: SessionData) => { // For GitHub scope list, order doesn't matter so we immediately sort the scopes <del> const sortedScopes = session.scopes.sort(); const scopesStr = sortedScopes.join(' '); </del> <ins> const scopesStr = [...session.scopes].sort().join(' '); </ins> if (scopesSeen.has(scopesStr)) { return undefined; }

: userInfo?.accountName ?? '<unknown>', id: session.account?.id ?? userInfo?.id ?? '<unknown>' }, <del> scopes: sortedScopes, </del> <ins> scopes: session.scopes, </ins> accessToken: session.accessToken }; });

public async createSession(scopes: string[]): Promise<vscode.AuthenticationSession> { try { <del> // For GitHub scope list, order doesn't matter so we immediately sort the scopes const sortedScopes = scopes.sort(); </del> <ins> // For GitHub scope list, order doesn't matter so we use a sorted scope to determine // if we've got a session already. const sortedScopes = [...scopes].sort(); </ins> /* __GDPR__ "login" : {

} */ this._telemetryReporter?.sendTelemetryEvent('login', { <del> scopes: JSON.stringify(sortedScopes), </del> <ins> scopes: JSON.stringify(scopes), </ins> }); const scopeString = sortedScopes.join(' '); const token = await this._githubServer.login(scopeString); <del> const session = await this.tokenToSession(token, sortedScopes); </del> <ins> const session = await this.tokenToSession(token, scopes); </ins> this.afterSessionLoad(session); const sessions = await this._sessionsPromise;
Change:
<img width="726" alt="image" src="https://user-"
zindex ftw
Actually not zindex, it was introduced via is the necessary here and could we not enforce that for notebook editor? When we have clip, the widgets in code editor will be cut off on the boundries.
We do need the clip to for notebooks. Otherwise when you scroll the editor area, the notebook widget will render on top of the sidebars Not sure how the fix this though. We've want to clip everything except the editor widgets. Off the top of my head I'm not sure how to do that I think for now we should revert the clip since it's less important than widgets rendering properly. I'll create a PR that does that but also open a new issue tracking the notebook's overlaying incorrectly when the editor area is scrolled

Discussion:
import { IWebview } from 'vs/workbench/contrib/webview/browser/webview'; import { EditorExtensionsRegistry } from 'vs/editor/browser/editorExtensions'; import { IEditorGroupsService } from 'vs/workbench/services/editor/common/editorGroupsService'; <del> import { IWorkbenchLayoutService, Parts } from 'vs/workbench/services/layout/browser/layoutService'; </del> const $ = DOM.$;

@INotebookExecutionService private readonly notebookExecutionService: INotebookExecutionService, @INotebookExecutionStateService notebookExecutionStateService: INotebookExecutionStateService, @IEditorProgressService private readonly editorProgressService: IEditorProgressService, <del> @IWorkbenchLayoutService private readonly workbenchLayoutService: IWorkbenchLayoutService, </del> ) { super(); this.isEmbedded = creationOptions.isEmbedded ?? false;

this._overlayContainer.style.left = `${this._shadowElementViewInfo.left - (elementContainerRect?.left || 0)}px`; this._overlayContainer.style.width = `${dimension ? dimension.width : this._shadowElementViewInfo.width}px`; this._overlayContainer.style.height = `${dimension ? dimension.height : this._shadowElementViewInfo.height}px`; <del> const rootContainer = this.workbenchLayoutService.getContainer(Parts.EDITOR_PART); if (rootContainer) { const clip = DOM.computeClippingRect(this._overlayContainer, rootContainer); this._overlayContainer.style.clip = `rect(${clip.top}px, ${clip.right}px, ${clip.bottom}px, ${clip.left}px)`; } </del> } //#endregion
Change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.67.2 OS Version: WSL, 'regular' Linux, Mac Steps to Reproduce: Turn on experimental shell integration () bash as the shell, and have a prompt command that uses "$?" as part of the prompt text. the command 'true' the command 'false' that the prompts should have had '0' and '1' as the replacement. it is always '0' with shell integration. OK. In the function , consider this loop: And perhaps something like this might fix it: is probably a really hacky way to set $? - but it's what I've used over the years. Note: This all goes away if were to be accepted.
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.67.2. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
Since I think we have already actioned this may not be a problem anymore
I suspect it will still be a problem. would only have addressed the issue if were adopted as it goes to great lengths to preserve state variables. Since the fix in was to bascially push/pop the trap DEBUG state, it probably doesn't help the exit $? status retention around the wrapped prompt.
good to know, thanks
to verify: add to your and with shell integration enabled, ensure that it is correct. for ex, run a command which fails (has an exit code). the status should reflect that.
Yes. This bug, as reported - without a DEBUG trap is fixed. So this can probably be closed. It still seems to be incorrect if there is a DEBUG trap in place. I have details to

Discussion:
fi __vsc_preexec() { <ins> __vsc_status="$?" </ins> eval ${__vsc_original_trap} PS1="$__vsc_prior_prompt" if [ -z "${__vsc_in_command_execution-}" ]; then

if [[ ${IFS+set} ]]; then __vsc_original_ifs="$IFS" fi <del> __vsc_status="$?" </del> if [[ "$__vsc_original_prompt_command" =~ .+;.+ ]]; then IFS=';' else

unset IFS fi for ((i = 0; i < ${#ADDR[@]}; i++)); do <del> # unset IFS </del> <ins> (exit ${__vsc_status}) </ins> builtin eval ${ADDR[i]} done __vsc_precmd
Change:
Tracks shipping TypeScript 4.7 in VS Code See for details
/verified Insiders shows this for me: !

Discussion:
"license": "MIT", "description": "Dependencies shared by all extensions", "dependencies": { <del> "typescript": "4.7.1-rc" </del> <ins> "typescript": "4.7" </ins> }, "scripts": { "postinstall": "node ./postinstall.mjs"

resolved "https://registry.yarnpkg.com/node-gyp-build/-/node-gyp-build-4.3.0.tgz#9f256b03e5826150be39c764bf51e993946d71a3" integrity sha512-iWjXZvmboq0ja1pUGULQBexmxq8CV4xBhX7VDOTbL7ZR4FOowwY/VOtRxBN/yKxmdGoIp4j5ysNT4u3S2pDQ3Q== <del> typescript@4.7.1-rc: version "4.7.1-rc" resolved "https://registry.yarnpkg.com/typescript/-/typescript-4.7.1-rc.tgz#23a0517d36c56de887b4457f29e2d265647bbd7c" integrity sha512-EQd2NVelDe6ZVc2sO1CSpuSs+RHzY8c2n/kTNQAHw4um/eAXY+ZY4IKoUpNK0wO6C5hN+XcUXR7yqT8VbwwNIQ== </del> <ins> typescript@4.7: version "4.7.2" resolved "https://registry.yarnpkg.com/typescript/-/typescript-4.7.2.tgz#1f9aa2ceb9af87cca227813b4310fff0b51593c4" integrity sha512-Mamb1iX2FDUpcTRzltPxgWMKy3fhg0TN378ylbktPGPK/99KbDtMQ4W1hwgsbPAsG3a0xKa1vmw4VKZQbkvz5A== </ins> vscode-grammar-updater@^1.1.0: version "1.1.0"
Change:
Run this code: Click on the 'Save as' button on the plot ! Throws an error: !
This works now, looks like what ever the issue was it has been fixed. Marking as closed for april so it gets validated.
I hit this on Insiders. Currently using the latest pre-release of Jupyter and Python . Let me know if there's any additional I can get for you. !
looks like a bug in Interactive window. It was marked as a mild regression at our end. Note: from what I can tell users will not be able to download and save images from interactive window as a result of this bug.
The problem seems to be with the class. We're unable to download files thats associated with Interactive Windows which has a custom scheme of (which doesn't have any file system providers).
Related issue
not sure if you know there is an easy fix for it. We generate from , which is interactive notebook in this case, and using that as default dir for save dialog will lead to this exception.
Seems similar to this case, like we should resolve it with the document path and the workspace URI

Discussion:
import { transformWebviewThemeVars } from 'vs/workbench/contrib/notebook/browser/view/renderers/webviewThemeMapping'; import { MarkupCellViewModel } from 'vs/workbench/contrib/notebook/browser/viewModel/markupCellViewModel'; import { CellUri, INotebookRendererInfo, NotebookSetting, RendererMessagingSpec } from 'vs/workbench/contrib/notebook/common/notebookCommon'; <del> import { INotebookExecutionStateService } from 'vs/workbench/contrib/notebook/common/notebookExecutionStateService'; </del> import { INotebookKernel } from 'vs/workbench/contrib/notebook/common/notebookKernelService'; import { IScopedRendererMessaging } from 'vs/workbench/contrib/notebook/common/notebookRendererMessagingService'; import { INotebookService } from 'vs/workbench/contrib/notebook/common/notebookService';

@ILanguageService private readonly languageService: ILanguageService, @IWorkspaceContextService private readonly workspaceContextService: IWorkspaceContextService, @IEditorGroupsService private readonly editorGroupService: IEditorGroupsService, <del> @INotebookExecutionStateService notebookExecutionStateService: INotebookExecutionStateService </del> ) { super();

return; } <del> const defaultDir = dirname(this.documentUri); </del> <ins> const defaultDir = this.documentUri.scheme === Schemas.vscodeInteractive ? this.workspaceContextService.getWorkspace().folders[0]?.uri ?? await this.fileDialogService.defaultFilePath() : dirname(this.documentUri); </ins> let defaultName: string; if (event.downloadName) { defaultName = event.downloadName;
Change:
This problem still occurs even if you disable all extensions and occurs in both stable and insider. Create the following Fenced code blocks for LaTeX in Markdown file. latex documentclass{article} begin{document} Hello, LaTeX{}!! end{document} Then run (&lt;kbdCtrl+/&lt;/kbd) on the line with . You will get the following results: latex documentclass{article} begin{document} &lt;!-- Hello, LaTeX{}!! --end{document} The correct result is: latex documentclass{article} begin{document} % Hello, LaTeX{}!! end{document} ` Execute repeatedly !
Hi Did you save the file? I disabled all my extensions for vscode insider and can't reproduce this issue. Is this still happening for you?
Yes. And all extensions are disabled. Yes. The insider was updated to the following versions because has been available for updating. However, the problem continues to be reproduced.
Sorry I was saving file as latex extension so it worked. I tried with markdown and it doesn't work for me too. This is a verified bug now.
Hi, I'm having the same issue. I'm new to the codebase. Can I try to solve this issue?
I had previously submitted similar issue. It may help to solve this issue. See
thanks for this, It will help me solve this issue. I am working on this.
Hey I made the PR. Could you please check it?

Discussion:
"meta.embedded.block.javascript": "javascript", "meta.embedded.block.json": "json", "meta.embedded.block.jsonc": "jsonc", <ins> "meta.embedded.block.latex": "latex", </ins> "meta.embedded.block.less": "less", "meta.embedded.block.objc": "objc", "meta.embedded.block.scss": "scss",

], "configurationDefaults": { "[markdown]": { <del> "editor.unicodeHighlight.ambiguousCharacters": false, "editor.unicodeHighlight.invisibleCharacters": false </del> <ins> "editor.unicodeHighlight.ambiguousCharacters": false, "editor.unicodeHighlight.invisibleCharacters": false </ins> } } },