jiebi/CodeConvo huggingface dataset:
Change:
Type: <bBug</bCC CC I create a terminal in VSCode, press shift+alt+f1 to display the accessibility help, and then press the esc key to dismiss the displayed information. I believe that the focus should be moved back to the terminal but it doesn't. I need to press shift+tab to move the focus back to the terminal. I tested using orca but I believe the same happens using nvda, I'll test later. VS Code version: Code - Insiders 1.76.0-insider (, 2023-02-09T05:23:03.109Z) OS version: Linux x64 6.1.9-200.fc37.x8664 Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<details<summaryExtensions (37)</summaryExtensionVersion ------ doxdocgen1.4.0 vscode-markdownlint0.49.0 vscode-chatgpt3.5.9 rest-client0.25.1 better-cpp-syntax1.17.2 azure-pipelines1.208.0 vscode-docker1.23.3 csharp1.25.4 vscode-kubernetes-tools1.3.11 remote-containers0.278.0 remote-ssh0.97. remote-ssh-edit0.84.0 azure-account0.11.3 cmake-tools1.13.45 cpptools1.14.1 cpptools-extension-pack1.3.0 makefile-tools0.6.0 powershell-preview2023.2.0 remote-explorer0.3. vsliveshare1.0.5828 fabric8-analytics0.3.6 java1.15. vscode-xml0.25. vscode-yaml1.11.0 sonarlint-vscode3.14.0 cmake0.0.17 intellicode-api-usage-examples0.2.7 vscodeintellicode1.2.30 vscode-boot-dev-pack0.2.1 vscode-spring-boot1.44.0 vscode-java-debug0.48.0 vscode-java-dependency0.21. vscode-java-pack0.25. vscode-java-test0.37. vscode-maven0.40. vscode-spring-boot-dashboard0.10.1 vscode-spring-initializr0.11.2 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --

Discussion:
this._register(dom.addStandardDisposableListener(this._contentDomNode.domNode, 'keydown', (e) => { if (e.keyCode === KeyCode.Escape) { this.hide(); <ins> instance.focus(); </ins> } })); this._register(instance.onDidFocus(() => this.hide()));
Change:
Here's a recording demonstrating Insiders (left) and previous Stable 1.74 (right): https://user- Steps: the SCM view and add a long line the width of the side bar such that the text wraps Notice how: When selecting the entire buffer, the selection expands beyond the text When selecting a subrange, sometimes the start position of the selection moves The rounded corners is generally broken: not all corners are rounded any more. This applies even for 1.74.
points to and a manual bisect points to being the first bad commit
Reverting from the change fixes the rendering problem. This diff fixes the rendering problem: The root problem here is that it is not supported that the editor background color is transparent. The class name ".monaco-editor-background" is used to render rounded corners and that stops working if it is transparent.
Thank you Tested the changes the created a PR.
Thanks for fixing. This has been on my list for weeks and I've just been, well, slammed

Discussion:
.monaco-workbench .part.basepanel > .content .scm-view .scm-editor-container .monaco-editor .margin, .monaco-workbench .part.basepanel > .content .scm-view .scm-editor-container .monaco-editor .monaco-editor-background { color: inherit; <del> background-color: unset </del> <ins> background-color: var(--vscode-input-background); </ins> } .scm-view .scm-editor-container .mtk1 {
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.70.1 OS Version: Darwin x64 21.3.0 Steps to Reproduce: Code VSCode <img width="81" alt="Screen Shot 2022-09-04 at 4 35 00 AM" src="https://user-"GitHub color , VSCode color
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.71.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
This seems to be working correctly per you may want to see whats the issue with vscode
I think this may be caused by bracket matching
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.75.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
I still see this: !

Discussion:
"keyword.operator.relational", "storage.type.function.arrow", "keyword.operator.bitwise.shift", <del> "punctuation.definition.tag" </del> <ins> "punctuation.definition.tag", "keyword.operator.assignment.compound.bitwise.ts" </ins> ], "embeddedLanguages": { "meta.tag.tsx": "jsx-tags",
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.70.1 OS Version: Darwin x64 21.3.0 Steps to Reproduce: Code VSCode <img width="81" alt="Screen Shot 2022-09-04 at 4 35 00 AM" src="https://user-"GitHub color , VSCode color
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.71.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
This seems to be working correctly per you may want to see whats the issue with vscode
I think this may be caused by bracket matching
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.75.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
I still see this: !

Discussion:
"storage.type.function.arrow", "keyword.operator.bitwise.shift", "meta.brace.angle", <del> "punctuation.definition.tag" </del> <ins> "punctuation.definition.tag", "keyword.operator.assignment.compound.bitwise.ts" </ins> ], "tokenTypes": { "meta.template.expression": "other",
Change:
Here we have a stack trace which hints that a from the extension host utility process to the renderer process ended up firing a message event on the renderer process with a property which is null ( is null).
values are possible if de-serialization .

Discussion:
*/ export class Protocol implements IMessagePassingProtocol { <del> readonly onMessage = Event.fromDOMEventEmitter<VSBuffer>(this.port, 'message', (e: MessageEvent) => VSBuffer.wrap(e.data)); </del> <ins> readonly onMessage = Event.fromDOMEventEmitter<VSBuffer>(this.port, 'message', (e: MessageEvent) => { if (e.data) { return VSBuffer.wrap(e.data); } return VSBuffer.alloc(0); }); </ins> constructor(private port: MessagePort) {

*/ class Protocol implements IMessagePassingProtocol { <del> readonly onMessage = Event.fromNodeEventEmitter<VSBuffer>(this.port, 'message', (e: MessageEvent) => VSBuffer.wrap(e.data)); </del> <ins> readonly onMessage = Event.fromNodeEventEmitter<VSBuffer>(this.port, 'message', (e: MessageEvent) => { if (e.data) { return VSBuffer.wrap(e.data); } return VSBuffer.alloc(0); }); </ins> constructor(private port: MessagePortMain) {

clearTimeout(handle); const onMessage = new BufferedEmitter<VSBuffer>(); <del> port.onmessage = ((e) => onMessage.fire(VSBuffer.wrap(e.data))); </del> <ins> port.onmessage = ((e) => { if (e.data) { onMessage.fire(VSBuffer.wrap(e.data)); } }); </ins> port.start(); resolve({
Change:
https://user- <img width="801" alt="image" src="https://user-"
I see the same, but figured it was down to the selected VS Code profile being enabled for that workspace?

Discussion:
cachedViewContainer = cachedViewContainer || this.cachedViewContainers.find(({ id }) => id === viewContainerId); // Show builtin ViewContainer if not registered yet <del> if (!viewContainer && cachedViewContainer?.isBuiltin) { </del> <ins> if (!viewContainer && cachedViewContainer?.isBuiltin && cachedViewContainer?.visible) { </ins> return false; }
Change:
<img width="554" alt="Screen Shot 2023-02-12 at 7 45 37 PM" src="https://user-"I noticed this while I was reading the API reference. The how-to-contribute guide didn't recommend to create PRs for typos so I opened this issue instead.

Discussion:
* If you want to monitor file events across all opened workspace folders: * * ```ts <del> * vscode.workspace.createFileSystemWatcher('**​/*.js')); </del> <ins> * vscode.workspace.createFileSystemWatcher('**​/*.js'); </ins> * ``` * * *Note:* the array of workspace folders can be empty if no workspace is opened (empty window).
Change:
Type: <bBug</bI'm attempting to add CodeDescription support to diagnostics in my Language Server, it appears as if the 'query' part of the URI the language server returns is encoded before being displayed in the Problems window. This is resulting in incorrect navigation when clicking on the link. Raw data returned by the Language Server to VsCode: ! Actual link provided within the Problems window: ! This is the full diagnostic data that's returned. "diagnostics": [ { "range": { "start": { "line": 38, "character": 14 }, "end": { "line": 38, "character": 20 } }, "severity": 1, "code": "ERROR01", "source": "MyLang", "message": "Custom Error 01", "codeDescription": { "href": "https://a-custom-" } VS Code version: Code 1.75.1 (, 2023-02-08T21:32:34.589Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (8)</summaryExtensionVersion ------ vscode-eslint2.4.0 mfcobol1.0.44 mfenterprise1.0.44 csharp1.25.4 remote-ssh0.96.0 remote-ssh-edit0.84.0 remote-wsl0.75.2 remote-explorer0.2.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
This seems to be an issue with the language client, how it is creating the vscode diagnostic and code href uri - What is the recommendation here for creating the vscode Uri from the url -
Users can create uris via but when opening them externally, e.g outside of VS Code, you should use - that skips encoding and works better with 3rd parties
<!-- 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!

Discussion:
const codeMatches = filterData && filterData.codeMatches || []; code.set(marker.code, codeMatches); } else { <del> // TODO@sandeep: these widgets should be disposed </del> const container = dom.$('.marker-code'); const code = new HighlightedLabel(container); <del> new Link(parent, { href: marker.code.target.toString(), label: container, title: marker.code.target.toString() }, undefined, this._openerService); </del> <ins> const link = marker.code.target.toString(true); this.disposables.add(new Link(parent, { href: link, label: container, title: link }, undefined, this._openerService)); </ins> const codeMatches = filterData && filterData.codeMatches || []; code.set(marker.code.value, codeMatches); }
Change:
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for . See also our . Happy Coding!

Discussion:
await commands.executeCommand('vscode.open', uri); assert.strictEqual(window.tabGroups.all.length, 1); assert.strictEqual(window.tabGroups.all[0].activeTab?.group.viewColumn, ViewColumn.One); <del> assert.strictEqual(window.activeTextEditor?.viewColumn, ViewColumn.One); </del> await commands.executeCommand('vscode.open', uri, ViewColumn.Two); assert.strictEqual(window.tabGroups.all.length, 2); assert.strictEqual(window.tabGroups.all[1].activeTab?.group.viewColumn, ViewColumn.Two); <del> assert.strictEqual(window.activeTextEditor?.viewColumn, ViewColumn.Two); </del> await commands.executeCommand('vscode.open', uri, ViewColumn.One); assert.strictEqual(window.tabGroups.all.length, 2); assert.strictEqual(window.tabGroups.all[0].activeTab?.group.viewColumn, ViewColumn.One); <del> assert.strictEqual(window.activeTextEditor?.viewColumn, ViewColumn.One); </del> let e1: Error | undefined = undefined; try {
Change:
This is useful for discovering shell types and creating them. When was sharing his screen, he was going to edit his default profile in his file, which is more involved

Discussion:
const dismiss = nls.localize('dismiss', "You can dismiss this dialog by pressing Escape or focusing elsewhere."); const openDetectedLink = nls.localize('openDetectedLink', 'The Open Detected Link ({0}) command enables screen readers to easily open links found in the terminal.'); const openDetectedLinkNoKb = nls.localize('openDetectedLinkNoKb', 'The Open Detected Link command enables screen readers to easily open links found in the terminal and is currently not triggerable by a keybinding.'); <ins> const newWithProfile = nls.localize('newWithProfile', 'The Create New Terminal (With Profile) ({0}) command allows for easy terminal creation using a specific profile.'); const newWithProfileNoKb = nls.localize('newWithProfileNoKb', 'The Create New Terminal (With Profile) command command allows for easy terminal creation using a specific profile and is currently not triggerable by a keybinding.'); const accessibilitySettings = nls.localize('accessibilitySettings', 'Access accessibility settings such as `terminal.integrated.tabFocusMode` via the Preferences: Open Accessibility Settings command.'); </ins> class AccessibilityHelpWidget extends Widget implements ITerminalWidget { readonly id = 'help';

content.push('- ' + this._descriptionForCommand(TerminalCommandId.RunRecentCommand, runRecentCommand, runRecentCommandNoKb) + 'n- ' + this._descriptionForCommand(TerminalCommandId.GoToRecentDirectory, goToRecent, goToRecentNoKb)); } content.push(this._descriptionForCommand(TerminalCommandId.OpenDetectedLink, openDetectedLink, openDetectedLinkNoKb)); <ins> content.push(this._descriptionForCommand(TerminalCommandId.NewWithProfile, newWithProfile, newWithProfileNoKb)); content.push(accessibilitySettings); </ins> content.push(readMoreLink, dismiss); const element = renderElementAsMarkdown(this._markdownRenderer, this._openerService, content.join('nn'), this._register(new DisposableStore())); const anchorElements = element.querySelectorAll('a');
Change:
Type: <bBug</bintegrated terminal either through button top right or key shortcut the key shortcut for "toggle panel visibility" -Opens integrated terminal from before is still there, looks normal (BUT scrollbar is on TOP not where it should be!) to scroll up on mouse wheel -Doesnt react to scroll down on mouse wheel -Terminal scrolls up to top (where scrollbar is) Key binding for "toggle panel visibility": ! Demo: Opening through View Terminal doesnt produce this bug. VS Code version: Code 1.75.1 (, 2023-02-08T21:35:30.018Z) OS version: Linux x64 5.15.0-60-generic snap Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<details<summaryExtensions (10)</summaryExtensionVersion ------ url-encode1.1.0 vscode-pull-request-github0.58.1 beautify1.5.0 .8.0 isort2022.8.0 python2023.2.0 vscode-pylance2023.2.20 notepadplusplus-keybindings1.0.7 tyranosyntax0.15.0 markdown-pdf1.4.4 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
To add, it doesn't scroll all the way down to the input line. It skips a whole page. !
It also only seems to happen on the second opening. On the first opening it is scrolled down correctly for some reason...
I am encountering the same issue. All terminals are affected by this problem. The issue arose after hiding and reopening the panel. As you can see in the video, the scroll bar becomes shorter after reopening the terminal. Could it be that this only happens with ZSH? https://user-
Same issue with mine above. I'm using cmd, so the problem is not specific to a terminal type.
Related:

Discussion:
// using the most up to date dimensions (eg. when terminal is created in the background // using cached dimensions of a split terminal). this._resize(); <del> // Trigger a forced refresh of the viewport to sync the viewport and scroll bar. This is // necessary if the number of rows in the terminal has decreased while it was in the // background since scrollTop changes take no effect but the terminal's position does // change since the number of visible rows decreases. </del> <ins> // HACK: Trigger a forced refresh of the viewport to sync the viewport and scroll bar. // This is necessary if the number of rows in the terminal has decreased while it was in // the background since scrollTop changes take no effect but the terminal's position // does change since the number of visible rows decreases. </ins> // This can likely be removed after https://github.com/xtermjs/xterm.js/issues/291 is // fixed upstream. <del> this.xterm.forceRefresh(); </del> <ins> setTimeout(() => this.xterm!.forceRefresh(), 0); </ins> } }
Change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/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: OS Version: Steps to Reproduce: Cloud Changes on the button: <img width="713" alt="image" src="https://user-"appears but no changes are made locally at least my change doesn't go away. Logs don't indicate anything interesting
I encountered this issue myself because I had branches that had the same name locally, but their upstream branches were set differently. My local workaround was to to get Cloud Changes to do the right thing, but the only way I figured this out was by looking at logs. It would be nice for Cloud Changes to at the very least show an error message or something when I click "Resume Working Changes" but it intentionally no-ops.
sorry, misclicked a label

Discussion:
}); } <del> async run(accessor: ServicesAccessor, editSessionId?: string): Promise<void> { await that.progressService.withProgress({ ...resumeProgressOptions, title: resumeProgressOptionsTitle }, async () => await that.resumeEditSession(editSessionId)); </del> <ins> async run(accessor: ServicesAccessor, editSessionId?: string, force?: boolean): Promise<void> { await that.progressService.withProgress({ ...resumeProgressOptions, title: resumeProgressOptionsTitle }, async () => await that.resumeEditSession(editSessionId, undefined, force)); </ins> } })); }

async run(accessor: ServicesAccessor, handle: TreeViewItemHandleArg): Promise<void> { const editSessionId = URI.parse(handle.$treeItemHandle).path.substring(1); const commandService = accessor.get(ICommandService); <del> await commandService.executeCommand('workbench.editSessions.actions.resumeLatest', editSessionId); </del> <ins> await commandService.executeCommand('workbench.editSessions.actions.resumeLatest', editSessionId, true); </ins> await treeView.refresh(); } });
Change:
Open VS Code insiders Open the following ipynb file in vscode <details<summaryipynb</summary</detailsOpen the same notebook sideways (on the right) in a text editor Now set focus to the text editor (on the right) and hit the save key (CTRL+S) Watch how the error output in the notebook (on the left) gets duplicated !
The reproduce steps are very impressive

Discussion:
} function renderError(outputInfo: OutputItem, container: HTMLElement, ctx: RendererContext<void> & { readonly settings: RenderOptions }): void { <ins> clearContainer(container); </ins> const element = document.createElement('div'); container.appendChild(element); type ErrorLike = Partial<Error>;
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: OS Version: Steps to Reproduce: the extension in VS Code and run the "Run Extension" task from the "Run and Debug" panel a new untitled file and change the language to "HTML" the command or start typing "example" to reveal the "example" completion items that one of the completion items has a red block and one does not Expected Behaviour: Both completion items should display a red block. Suggested Fix: When the color extractor checks the property it should account for values: For example the piece of code above could be changed to the following:

Discussion:
out[0] = item.completion.detail; return true; } <del> if (typeof item.completion.documentation === 'string') { const match = ColorExtractor._regexRelaxed.exec(item.completion.documentation); if (match && (match.index === 0 || match.index + match[0].length === item.completion.documentation.length)) { </del> <ins> if (item.completion.documentation) { const value = typeof item.completion.documentation === 'string' ? item.completion.documentation : item.completion.documentation.value; const match = ColorExtractor._regexRelaxed.exec(value); if (match && (match.index === 0 || match.index + match[0].length === value.length)) { </ins> out[0] = match[0]; return true; }