jiebi/CodeConvo huggingface dataset:
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 (don't know) <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.75.1 OS Version: macOS Ventura 13.0.1 VS Code walkthrough instructions disappear when opening the hello- file from the link (simple workflow step). Hearing the same feedback from multiple users doing internal testing. Steps to Reproduce: a codespace from . to the second walkthrough called "Writing workflows". the first step ("Actions workflow"), click the link to open the hello- file
This could potentially happen because the webivew that displays the welcome content has been reparented. This is actually easy to simulate: a single editor group open a walkthrough This will destroy the webview content because one of its parent nodes changes. The iframe still exists in the dom, but nothing is rendered inside of it. This is a limitation of how iframes are designed and is not something we can disable (but we do workaround it in other places) To fix this, you can either try switching the welcome webview to use an  or explore forcing the webview to re-render itself if it get reparented (but I'm not sure how difficult this would be) Webviews like the readme and markdown preview all use to avoid this issue

Discussion:
const layoutDelayer = new Delayer(50); this.layoutMarkdown = () => { <del> layoutDelayer.trigger(() => { webview.postMessage({ layoutMeNow: true }); </del> <ins> layoutDelayer.trigger(async () => { this.buildMediaComponent(stepId); </ins> }); };
Change:
In the experimental dark theme the vscode-textPreformat-foreground token color shows up as red for me: !

Discussion:
"textCodeBlock.background": "#6e768166", "textLink.activeForeground": "#40A6FF", "textLink.foreground": "#40A6FF", <del> "textPreformat.foreground": "#f85149", </del> "textSeparator.foreground": "#21262d", "titleBar.activeBackground": "#181818", "titleBar.activeForeground": "#cccccc",
Change:
Currently the aria label of extension items does not announce if the author is verified or not. We should change that as it was requested by users and overall makes good sense. fyi
Announces verified publisher: <img width="641" alt="image" src="https://user-"CC
Awesome! Works great -verified

Discussion:
if (!extension) { return ''; } <del> const publisher = localize('extension.arialabel.publihser', "Publisher {0}", extension.publisherDisplayName); </del> <ins> const publisher = extension.publisherDomain?.verified ? localize('extension.arialabel.verifiedPublihser', "Verified Publisher {0}", extension.publisherDisplayName) : localize('extension.arialabel.publihser', "Publisher {0}", extension.publisherDisplayName); </ins> const deprecated = extension?.deprecationInfo ? localize('extension.arialabel.deprecated', "Deprecated") : ''; return `${extension.displayName}, ${deprecated ? `${deprecated}, ` : ''}${extension.version}, ${publisher}, ${extension.description}`; },
Change:
<img width="602" alt="image" src="https://user-"IMHO it's very unlikely that users install VS Code through the remote picker, so we probably want to move it down to the bottom.
It's still not at the bottom of the list, but has moved to be below the codespace option, so considering this verified. !
Yeah that's the intended behavior, we still suffix the list with Install Additional Remote Extensions so that entry should always be last if it is shown.

Discussion:
if (isCurrentRemote1 !== isCurrentRemote2) { return isCurrentRemote1 ? -1 : 1; } <ins> // legacy indicator commands go last if (g1[0] !== '' && g2[0] === '') { return -1; } else if (g1[0] === '' && g2[0] !== '') { return 1; } </ins> return g1[0].localeCompare(g2[0]); }); }
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: version 1.76 OS Version: Windows 22H2 Steps to Reproduce: a debugging session, and click on the "Edit Condition..." button (the pencil). Ensure that the cursor is in a window with a short width. ! appears. ! window. The text appears to be cut off. ! to look like this: !
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.76.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
Probably we need to relayout that breakpoint editor when the parent editor width changes
I'll get it done
My phone is not working unless connected to wifi I need serious help as I am to be in GA at 7am I realize this phone is outdated a Motorola it is used but my Apple I cannot see the screen on it and I obviously can't carry my pro on the road cuz it is not activated can someone help me you can record everything l do not care I need help
All kids are grown? The Samsung used to belong to my son now belongs to coworker On Sun, Apr 9, 2023, 8:29 PM Amy Scarbrough

Discussion:
this.centerInputVertically(); } <ins> protected override _onWidth(widthInPixel: number): void { if (typeof this.heightInPx === 'number') { this._doLayout(this.heightInPx, widthInPixel); } } </ins> private createBreakpointInput(container: HTMLElement): void { const scopedContextKeyService = this.contextKeyService.createScoped(container); this.toDispose.push(scopedContextKeyService);
Change:
Type: <bBug</bhigh contrast dark them explorer, start find Bug Unlike the editor find widget, the tree find widget does not get a border: ! This makes it harder to see VS Code version: Code - Insiders 1.77.0-insider (Universal) (, 2023-03-02T12:44:52.544Z) OS version: Darwin x64 22.3.0 Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<!-- generated by issue reporter --

Discussion:
max-width: 200px; z-index: 100; margin: 0 6px; <ins> border: 1px solid var(--vscode-widget-border); </ins> } .monaco-tree-type-filter.disabled {
Change:
Version: 1.77.0-insider (Universal) Commit: Date: 2023-03-03T05:23:13.637Z Electron: 19.1.11 Chromium: 102.0.5005.196 16.14.2 V8: 10.2.154.26-electron.0 OS: Darwin arm64 20.6.0 Sandboxed: Yes ProductName: macOS ProductVersion: 11.7.4 BuildVersion: 20G1120 <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes Steps to Reproduce: the following extension sample: a text document. and type falls into an infinite loop https://user-
I can reproduce. Thanks for reporting this, looking into this asap
To reproduce use completion provider from above have a text file with  type  after the existing  and select the second option The issue is computing alternative suggestions (for tab complete). That trips on an invalid state because the chosen (start) index doesn't exist anymore. That's because the model updated in response to applying the additional edits.

Discussion:
private static _moveIndex(fwd: boolean, model: CompletionModel, index: number): number { let newIndex = index; <del> while (true) { </del> <ins> for (let rounds = model.items.length; rounds > 0; rounds--) { </ins> newIndex = (newIndex + model.items.length + (fwd ? +1 : -1)) % model.items.length; if (newIndex === index) { break;

if (Array.isArray(item.completion.additionalTextEdits)) { <ins> // cancel -> stops all listening and closes widget this.model.cancel(); </ins> // sync additional edits const scrollState = StableEditorScrollState.capture(this.editor); this.editor.executeEdits(
Change:
there's an issue now because tabbing goes to the status bar instead of the terminal. I see that isn't set on the element. even when I set that explicitly, it seems like it's removed Originally posted by in

Discussion:
z-index: 2; position: relative; } <del> .xterm.terminal.hide { display: none; } </del>

private _hide(): void { this._accessibleBuffer.classList.remove('active'); <del> this._xtermElement.classList.remove('hide'); </del> this._xterm.raw.focus(); }

if (model) { this._bufferEditor.setModel(model); } <ins> this._bufferEditor.onDidFocusEditorText(() => this._accessibleBuffer.classList.add('active')); </ins> if (!this._registered) { this._bufferEditor.layout({ width: this._xtermElement.clientWidth, height: this._xtermElement.clientHeight }); this._bufferEditor.onKeyDown((e) => { <ins> // tab moves focus mode will prematurely move focus to the next element before // xterm can be focused </ins> if (e.keyCode === KeyCode.Escape || e.keyCode === KeyCode.Tab) { <ins> e.stopPropagation(); e.preventDefault(); </ins> this._hide(); } });

} this._accessibleBuffer.tabIndex = -1; this._accessibleBuffer.classList.add('active'); <del> this._xtermElement.classList.add('hide'); </del> if (this._lastContentLength !== fragment.length || this._refreshSelection) { let lineNumber = 1; const lineCount = model?.getLineCount();
Change:
I just tried Codespaces for the first time. I clicked on Codespaces, and then I started my first Jupyter template. Then I opened one of the included notebooks (). The window opened is empty and it loops forever (small moving blue line moving from left to right on top of window). It also opens the following notifications: " Error loading webview: Error: Could not register service workers: NotSupportedError: Failed to register a ServiceWorker for scope ('') with script (''): The user denied permission to use Service Worker.. " There seems to be an option for "Insiders Version". I tried that as well, but to no avail, same error. I also tried the latest version of the Jupyter extension plugin by Microsoft, still the same error. The demo/jupyter template seems to be broken. Also any advise on how to try it out ? cheers ADD ISSUE DESCRIPTION HERE Version: 1.76.0 Commit: User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36 Embedder: codespaces <!-- generated by web issue reporter --
What browser are you using? Are you in private mode?
hi thanks for the follow up. I'm not sure what "private mode" means, but I was using a standard Chrome browser in a linux laptop. chrome://version ==110.0.5481.177 (Official Build) (64-bit)
In chrome it's called incognito mode. Are you using it or any other privacy type settings, specifically around cookies?
Oh, apologies. No, I was not using incognito mode. I don't have any special cookies settings, or using any extension in that direction. Pretty vanilla set up, as far as I know.
Also I tried from 2 different computers, both using Chrome, and Linux 22.04.
Oh, ok, today I tried once again. And this time I noticed that Chrome is configured to block third-party cookies -- I hadn't noticed before because that only kicks in later, once I open the jupyter notebooks. Once I clicked on the little icon to enable it, it works!
Maybe worth finding a way to communicate this to the user ?
Thanks for confirming. Discussed in AFAIk we can't actually track that this setting is causing the error, but I'll see if we can add some suggestion text to the error message we show

Discussion:
<meta charset="UTF-8"> <meta http-equiv="Content-Security-Policy" <del> content="default-src 'none'; script-src 'sha256-PXLLbTxUqUn4p+KvvFj5cqYN1AHAoeOHkHWZwsmuGck=' 'self'; frame-src 'self'; style-src 'unsafe-inline';"> </del> <ins> content="default-src 'none'; script-src 'sha256-tzEa4Fy2HeWh9MuG37ZD3KtUwJ9bB44fgpDcvpmRm2w=' 'self'; frame-src 'self'; style-src 'unsafe-inline';"> </ins> <!-- Disable pinch zooming --> <meta name="viewport"

navigator.serviceWorker.addEventListener('controllerchange', onControllerChange); } }).catch(error => { <del> reject(new Error(`Could not register service workers: ${error}.`)); </del> <ins> if (!onElectron && error instanceof Error && error.message.includes('user denied permission')) { return reject(new Error(`Could not register service worker. Please make sure third party cookies are enabled: ${error}`)); } return reject(new Error(`Could not register service worker: ${error}.`)); </ins> }); });
Change:
Steps to Reproduce: Create a MR workspace file with more than one folder the MR workspace All top level folders are expanded. This is very slow if there are lot of root folders and also if the MR workspace is in remote
how are you creating your MR workspace? By composing an file directly, then opening it? Or by opening the first folder from FileOpen Folder... and then using FileAdd Folder to Workspace... to add more folders to make it MR? Or some other way? When I create a MR workspace and save it, then collapse the top-level folders, then exit VS Code, restart and reopen the MR workspace, the top-level folders remain collapsed. But if I then create a copy of that .code-workspace file and open this, the root folders get expanded (and I also get asked the trust question). Presumably the expand happens because my local storage hasn't got any collapse-state record for a workspace with this name, so it defaults to expanding the first level. I suppose VS Code could be changed so it defaults to keeping root folders collapsed for a workspace it hasn't previously seen. But some users might complain about such a change.
I think like suggested in the duplicate issue, we probably need a limit here. It's nice when you have 3-4 folders to expand but 100s+ can crash VS Code.
Yes

Discussion:
const promise = this.tree.setInput(input, viewState).then(async () => { if (Array.isArray(input)) { if (!viewState || previousInput instanceof ExplorerItem) { <del> // There is no view state for this workspace (we transitioned from a folder workspace?), expand all roots. await Promise.all(input.map(async item => { </del> <ins> // There is no view state for this workspace (we transitioned from a folder workspace?), expand up to five roots. // If there are many roots in a workspace, expanding them all would can cause performance issues #176226 for (let i = 0; i < Math.min(input.length, 5); i++) { </ins> try { <del> await this.tree.expand(item); </del> <ins> await this.tree.expand(input[i]); </ins> } catch (e) { } <del> })); </del> <ins> } </ins> } // Reloaded or transitioned from an empty workspace, but only have a single folder in the workspace. if (!previousInput && input.length === 1 && this.configurationService.getValue<IFilesConfiguration>().explorer.expandSingleFolderWorkspaces) {
Change:
copies a url-encoded filepath copies a url-encoded filepath, e.g. becomes , which also yields a "Workspace does not exist" warning message. Originally posted by in
Candidate PR for 1.76:

Discussion:
if (connectionInfo) { const linkToOpen = that.getLinkToOpen(connectionInfo); const remoteExtension = that.serverConfiguration.extension; <del> const linkToOpenForMarkdown = linkToOpen.toString().replace(/)/g, '%29'); </del> <ins> const linkToOpenForMarkdown = linkToOpen.toString(false).replace(/)/g, '%29'); </ins> await notificationService.notify({ severity: Severity.Info, message:

), actions: { primary: [ <del> new Action('copyToClipboard', localize('action.copyToClipboard', "Copy Browser Link to Clipboard"), undefined, true, () => clipboardService.writeText(linkToOpen.toString())), </del> <ins> new Action('copyToClipboard', localize('action.copyToClipboard', "Copy Browser Link to Clipboard"), undefined, true, () => clipboardService.writeText(linkToOpen.toString(true))), </ins> new Action('showExtension', localize('action.showExtension', "Show Extension"), undefined, true, () => { return commandService.executeCommand('workbench.extensions.action.showExtensionsWithIds', [remoteExtension.extensionId]); })

const clipboardService = accessor.get(IClipboardService); if (that.connectionInfo) { const linkToOpen = that.getLinkToOpen(that.connectionInfo); <del> clipboardService.writeText(linkToOpen.toString()); </del> <ins> clipboardService.writeText(linkToOpen.toString(true)); </ins> } }
Change:
suggested would be good for this
FYI, I have customized like below:
feel free to close if we already support this now.
We do not have a default keybinding that works along with the screen reader being enabled, though ctrl+pagedown/pageup are currently bound to next/previous editor, so I don't think we can use that one without breaking current workflows.
Maybe ctrl+alt+pagedown/pageup?

Discussion:
), primary: KeyCode.DownArrow, weight: KeybindingWeight.EditorCore <del> } </del> <ins> }, { when: NOTEBOOK_EDITOR_FOCUSED, primary: KeyMod.CtrlCmd | KeyMod.Alt | KeyCode.PageDown, mac: { primary: KeyMod.CtrlCmd | KeyMod.Alt | KeyCode.PageDown, }, weight: KeybindingWeight.WorkbenchContrib }, </ins> ] }); }

), primary: KeyCode.UpArrow, weight: KeybindingWeight.WorkbenchContrib, // markdown keybinding, focus on list: higher weight to override list.focusDown <del> } </del> <ins> }, { when: NOTEBOOK_EDITOR_FOCUSED, primary: KeyMod.CtrlCmd | KeyMod.Alt | KeyCode.PageUp, mac: { primary: KeyMod.CtrlCmd | KeyMod.Alt | KeyCode.PageUp }, weight: KeybindingWeight.WorkbenchContrib }, </ins> ], }); }

content.push(descriptionForCommand('notebook.cell.focusInOutput', localize('notebook.cell.focusInOutput', 'The Focus Output command ({0}) will set focus in the cell's output.'), localize('notebook.cell.focusInOutputNoKb', 'The Quit Edit command will set focus in the cell's output and is currently not triggerable by a keybinding.'), keybindingService)); <del> content.push(localize('notebook.cellNavigation', 'The up and down arrows will move focus between cells while focused on the outer cell container')); </del> <ins> content.push(descriptionForCommand('notebook.focusNextEditor', localize('notebook.focusNextEditor', 'The Focus Next Cell Editor command ({0}) will set focus in the next cell's editor.'), localize('notebook.focusNextEditorNoKb', 'The Focus Next Cell Editor command will set focus in the next cell's editor and is currently not triggerable by a keybinding.'), keybindingService)); content.push(descriptionForCommand('notebook.focusPreviousEditor', localize('notebook.focusPreviousEditor', 'The Focus Previous Cell Editor command ({0}) will set focus in the previous cell's editor.'), localize('notebook.focusPreviousEditorNoKb', 'The Focus Previous Cell Editor command will set focus in the previous cell's editor and is currently not triggerable by a keybinding.'), keybindingService)); content.push(localize('notebook.cellNavigation', 'The up and down arrows will also move focus between cells while focused on the outer cell container.')); </ins> content.push(descriptionForCommand('notebook.cell.executeAndFocusContainer', localize('notebook.cell.executeAndFocusContainer', 'The Execute Cell command ({0}) executes the cell that currently has focus.',), localize('notebook.cell.executeAndFocusContainerNoKb', 'The Execute Cell command executes the cell that currently has focus and is currently not triggerable by a keybinding.'), keybindingService));
Change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.76.0 Steps to Reproduce: the browser devtools the command palette the items is a lot of errors in the console: !
I'm not seeing this anymore... Can you confirm
Actually I can repro this only in and not odd

Discussion:
import { ThrottledDelayer } from 'vs/base/common/async'; import { compareAnything } from 'vs/base/common/comparers'; import { memoize } from 'vs/base/common/decorators'; <ins> import { isCancellationError } from 'vs/base/common/errors'; </ins> import { Emitter, Event } from 'vs/base/common/event'; import { IMatch } from 'vs/base/common/filters'; import { IMarkdownString } from 'vs/base/common/htmlContent';

) { return; } <del> await delayer.trigger(async () => { if (e.element) { this.showHover(e.element); </del> <ins> try { await delayer.trigger(async () => { if (e.element) { this.showHover(e.element); } }); } catch (e) { // Ignore cancellation errors due to mouse out if (!isCancellationError(e)) { throw e; </ins> } <del> }); </del> <ins> } </ins> })); this.disposables.push(this.list.onMouseOut(e => { // onMouseOut triggers every time a new element has been moused over