jiebi/CodeConvo huggingface dataset:
Change:
let hrefText = node.getAttribute('data-href'); if (!hrefText) { <ins> hrefText = node.getAttribute('href'); </ins> // Pass through known schemes <del> if (passThroughLinkSchemes.some(scheme => node.href.startsWith(scheme))) { </del> <ins> if (passThroughLinkSchemes.some(scheme => hrefText.startsWith(scheme))) { </ins> return; } <del> hrefText = node.getAttribute('href'); </del> } // If original link doesn't look like a url, delegate back to VS Code to resolve

Discussion:
<!-- 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.85.2 OS Version: Windows 11 Steps to Reproduce: clone the repository. in VSCode's Preview Mode. one of links to . Hello, VSCode Team. I've recently been experimenting with creating a language switcher in , allowing it to switch to different language versions of . Below is the code snippet I've created: However, I found that when I open the preview of *.md files in VSCode using "Markdown: Open Preview" and try to click those hyperlinks to switch to other languages of README, the system automatically opens the default browser. The content in the URL bar is: But when I upload the folder's content to GitHub, clicking those hyperlinks indeed switches normally. It means that it might be an issue with VSCode, right? If this behavior is the default in VSCode, then: should I modify the HTML syntax to enable normal switching in VSCode's preview mode? , is there a way to change this default behavior in VSCode? !
I read about it and got to know that the default behavior of Visual Studio Code's built-in Markdown preview mode is to open links in an external browser buy If you want to change this behavior specifically for your local preview while using Visual Studio Code, you might consider looking for a VSCode extension that customizes the behavior of the markdown preview renderer. I checked and used Markdown Preview Enhanced by Yiyi Wang to get result.
Change:
private refreshChildren(recursive: boolean, safe: boolean = false, force: boolean = false): WinJS.Promise { if (!force && !this.isExpanded()) { <del> this.needsChildrenRefresh = true; </del> <ins> const setNeedsChildrenRefresh = (item: Item) => { item.needsChildrenRefresh = true; item.forEachChild(setNeedsChildrenRefresh); }; setNeedsChildrenRefresh(this); </ins> return WinJS.TPromise.as(this); }

Discussion:
VSCode Version: 1.25.1 (also tested in latest insiders build) OS Version: Arch Linux x64 Steps to Reproduce: I have created a little demonstrating this bug: the project and run and the debugger - a new VS Code window opens containing a custom view called "BUG DEMO" that custom view and expand all nodes in it - the labels are , and on "INCREASE COUNTER" - now the labels are , and (which is correct) the root node, click "INCREASE COUNTER" and expand the root node again Now the labels are , and - this is incorrect, the grandchild's label should be . You can also see in the Debug console that after clicking "INCREASE COUNTER" the second time and expanding the root node again, only the root and child nodes are fetched, but not the grandchild.
Assigned to July milestone for investigation
Looks like in your code you are using the same id for all nodes. If you are providing an it should be unique. is optional and when it is removed the last step increase counter for all elements
But I'm only using this for one of the 3 nodes:
I just tried with the latest Insiders build and the bug is still there: ! The output in the debug console shows that the three nodes have different IDs , and : Removing the IDs is not a good workaround as it means that the tree loses its collapsed state on every update: !
You are right, it is also reproducible with attribute.
To Verify: Open VS Code on a folder with following structureExpand to see Reveal File C in OS Explorer (Finder/File Explorer) Collapse in VS Code file explorer Rename to Outside VS Code (Finder) Refresh the File Explorer Tree in VS Code Expand in VS Code Verify that Folder B is expanded and showing
Change:
await this.configurationEditing.writeConfiguration(editableConfigurationTarget, { key, value }, { scopes: overrides, ...options }); switch (editableConfigurationTarget) { case EditableConfigurationTarget.USER_LOCAL: <del> if (this.applicationConfiguration && this.configurationRegistry.getConfigurationProperties()[key].scope === ConfigurationScope.APPLICATION) { </del> <ins> if (this.applicationConfiguration && this.configurationRegistry.getConfigurationProperties()[key]?.scope === ConfigurationScope.APPLICATION) { </ins> await this.reloadApplicationConfiguration(); } else { await this.reloadLocalUserConfiguration();

Discussion:
Issue filed by Hi, I would like to ask about a problem related to the usage of WorkspaceConfiguration.Update() We received an issue This happens when the C# extension starts, we are migrating some old configurations to its new name when using a non-default profile. (This doesn't repro when use default profile) See the code here: I tested locally and verified the issue in feedback happens when executing during the extension activation. What I did is created a non-default profile, and put one of our deprecated options in the global profile. <img width="985" alt="image" src=""Then the error occurs when removing the old configuration see this ! The old configuration is removed in this case. Is this our misuse of the API or is this a bug in vscode?
Profile / config - assigning first to Sandeep this is from the C# extension, so if you have additional questions feel free to ask or let me know if I can help in any way.
It would be great if we can have a summary of steps to reproduce
can you provide steps please? Thank you
My repro step: Install the C# extension in the preview channel. <img width="665" alt="image" src=""- Use this sample solution, open it. Create a non-default profile. <img width="515" alt="image" src=""- Open the profile in json editor. Add these to the JSON. Close VSCode and restart it. You can see one configuration is changed. <img width="602" alt="image" src=""C# extension is not activated. And the error log is shown in the extension host output window.
can you verify that this fix indeed fixes the problem you reported. Thank you!
Verified it is solved in 1.81.0-insider
Change:
append(moreInfo, $('.more-info-entry', undefined, $('div', undefined, localize('release date', "Released on")), <del> $('div', undefined, new Date(gallery.releaseDate).toLocaleString(undefined, { hour12: false })) </del> <ins> $('div', undefined, new Date(gallery.releaseDate).toLocaleString(undefined, { hourCycle: 'h23' })) </ins> ), $('.more-info-entry', undefined, $('div', undefined, localize('last updated', "Last updated")), <del> $('div', undefined, new Date(gallery.lastUpdated).toLocaleString(undefined, { hour12: false })) </del> <ins> $('div', undefined, new Date(gallery.lastUpdated).toLocaleString(undefined, { hourCycle: 'h23' })) </ins> ) ); }

Discussion:
<!-- 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.65.0 OS Version: Linux debian 5.16.0-3-amd64 Steps to Reproduce: some extensions in the market. Check the field, if the extension was updated between and AM, it will show , which is not desired. examples: extension in enUS locale, in zhCN locale Analysis: According to the question on , It seems to be a bug in INTL ECMA specifications. we can avoid this issue by add to method. I tried the solution, it worked. The changes is as follows: ! Is this suitable to avoid the issue ? Screen shots: ! !
Change:
const timer = setTimeout(() => { codeProc.kill(); reject(new Error('export-default-configuration process timed out')); <del> }, 12 * 1000); </del> <ins> }, 30 * 1000); </ins> codeProc.on('error', err => { clearTimeout(timer);

Discussion:
Refs
Not sure what's going on - this process is pretty straightforward and hasn't changed in years. I am launching the full vscode window on this build machine, nothing has changed in electron that would interact with that right?
and are on same electron versions, the step worked fine in the latest build last Friday , first timeout failure started since insiders were turned back on last Saturday and since then all insiders build seem to consistently hit the timeout Todays' nightly run: Testing if I can repro the issue locally.
Testing the callsite locally seems to work fine.
I wonder if the timeout is insufficient, testing a build with increased timeout here
Previous build did not enable the upload step, new build
Kicked off another, removing the branch check
Might not be fixed ( - run on 11th of May, one day after this fix has been merged to main)
the fix only landed in , failing build was on , how do you feel about backporting the fix to ?
I can do that
Change:
resolved "https://registry.yarnpkg.com/xterm-addon-webgl/-/xterm-addon-webgl-0.12.0-beta.36.tgz#460f80829a78c979a448d5b764699af3f0366ff1" integrity sha512-sgX7OHSGZQZE5b4xtPqd/5NEcll0Z+00tnTVxKZlXf5XEENcG0tnBF4I4f+k9K3cmjE1UIUVG2yYPrqWlYCdpA== <del> xterm-headless@4.19.0-beta.52: version "4.19.0-beta.52" resolved "https://registry.yarnpkg.com/xterm-headless/-/xterm-headless-4.19.0-beta.52.tgz#87298cb205694cfdd701a9a96dcd06434a9773fe" integrity sha512-9s8VtGa9JUdEWxrNDJpEng2mEFn0KjWM3R9nxezA8mXHsJ/0cMqoK00s/fzhAEXZqHycWASSECMWgFOaT0MrnQ== </del> <ins> xterm-headless@4.19.0-beta.53: version "4.19.0-beta.53" resolved "https://registry.yarnpkg.com/xterm-headless/-/xterm-headless-4.19.0-beta.53.tgz#bbcf2b9c3853fb96b642df6950d3b8fa37174be7" integrity sha512-o3Hbe9zT918IIfHlREhVQolTdXrdOmQKyHtVsfT9x2CG4Z3TaD6A5koX6P0cIoeVwP/dc3R/WBnbXLYl9B0Jiw== </ins> <del> xterm@4.19.0-beta.52: version "4.19.0-beta.52" resolved "https://registry.yarnpkg.com/xterm/-/xterm-4.19.0-beta.52.tgz#21c7ad0bd905f3fddaa0583951514c8271dcd822" integrity sha512-2itY6dyiimOEkgVwc31TngYQ6npHt7or1wxU0Flbv4PjH4ke8K26NDB7KAi0YYkn2g0/qzIjQc7ykdrrTaEgMg== </del> <ins> xterm@4.19.0-beta.53: version "4.19.0-beta.53" resolved "https://registry.yarnpkg.com/xterm/-/xterm-4.19.0-beta.53.tgz#ddb555e032d5ff3a1450d9c4b0250bc3e3ccac99" integrity sha512-WoJAux1FawCpgDBP9Gr5H+RQUY8H7djr+ZQTpD+D2A3nJTXmoHH5Q1lnu8XCsuPscjRAgqFSQCG+5oHQwBQIdA== </ins> yallist@^4.0.0: version "4.0.0"

Discussion:
Testing a new terminal a script which logs the same text 2000 times a query, find widget says there are 2000 matches the terminal (e.g. collapse and expand the side bar) :bug: the number of matches is now less even though the same amount of scrollback is visible, moreover deleting and reentering the query doesn't reset the match count !
Maybe this isn't released yet, but I'm still getting the same problem in today's insiders.
Still repros for me :(
Can one of you pls provide a gif? it's working for me with the above example as expected and with others
https://user-
You are both on Windows - I wonder if that has to do with this. Could someone on mac pls verify this?
!
from !
Something weird going on here: ! This is after pasting in " Hi Hi" many times, once the command wraps to the end the terminal freaks out (conpty reprinting), but at some point it breaks and find only finds one result. Finding the next works, but it still says 1 of 1.
More weird behavior !
All results aren't getting included when search results get highlighted !
Problem here seems to be the search addon gets confused because translateToString considers the second character whitespace: But in the search algorirthm it's treated as a null character, of length 0, as opposed to .
Still reproing this. Initially: ! After making the terminal panel taller: !
this is on Windows? That's actually acting as expected because of the way conpty works, it ends up losing lines just above the bottom of the buffer.
Pretty sure you were seeing so closing this again for verification
Change:
overflow: hidden; white-space: nowrap; text-overflow: ellipsis; <ins> text-decoration: var(--text-link-decoration); </ins> } .extension-editor > .body > .content > .details > .additional-details-container .resources-container > .resources > .resource:hover {

Discussion:
Testing No links in an extension metadata page show links underlined... !
Same as before, fixed and not merged in time via and underlines for the domain and resource section in
Change:
"git": { "name": "electron", "repositoryUrl": "https://github.com/electron/electron", <del> "commitHash": "73c87bcfc6e18428c21676d68f829364e6a7b15d" </del> <ins> "commitHash": "322f1c3f8907f2592eef5b5e03a97045e30df9e3" </ins> } }, "isOnlyProductionDependency": true, "license": "MIT", <del> "version": "17.4.1" </del> <ins> "version": "17.4.3" </ins> }, { "component": {

Discussion:
<!-- 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.67.1 OS Version: Win 7 x64 Steps to Reproduce: update Electron to 17.4.3
Does this fix the high CPU usage on OSX? (introduced in 1.67.0)
Change:
return { type: FileType.File, ctime: 0, <del> mtime: this.versions.get(resource.toString()) || 0, </del> <ins> mtime: this.mtimes.get(resource.toString()) || 0, </ins> size: entry.size ?? (await this.readFile(resource)).byteLength }; }

Discussion:
<!-- 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/69-insider OS Version: Windows 11 Steps to Reproduce: user file in timeline view :bug: see timeline entries from 52 years ago !
Is this reproducible or a one-off?
Looks like the file system provider that is implemented for is not implementing properly, I see a value of : <img width="851" alt="image" src="https://user-"Moving to
Change:
import { localize } from 'vs/nls'; import { EditorGroupLayout, GroupDirection, GroupLocation, GroupOrientation, GroupsArrangement, GroupsOrder, IAuxiliaryEditorPart, IAuxiliaryEditorPartCreateEvent, IEditorDropTargetDelegate, IEditorGroupsService, IEditorSideGroup, IFindGroupScope, IMergeGroupOptions } from 'vs/workbench/services/editor/common/editorGroupsService'; import { Emitter } from 'vs/base/common/event'; <del> import { DisposableStore, IDisposable } from 'vs/base/common/lifecycle'; </del> <ins> import { DisposableStore, IDisposable, toDisposable } from 'vs/base/common/lifecycle'; </ins> import { GroupIdentifier } from 'vs/workbench/common/editor'; import { EditorPart, MainEditorPart } from 'vs/workbench/browser/parts/editor/editorPart'; import { IEditorGroupView, IEditorPartsView } from 'vs/workbench/browser/parts/editor/editor';

Discussion:
Currently we do not really track MRU of editor groups across windows. Some features rely on this though, so we should see if we can track MRU truly across aux windows.
Change:
this.installingExtensions.clear(); this.uninstallingExtensions.clear(); })); <del> const extensionLifecycle = this._register(new ExtensionsLifecycle(environmentService, this.logService)); this._register(this.extensionsScanner.onDidRemoveExtension(extension => extensionLifecycle.postUninstall(extension))); </del> } zip(extension: ILocalExtension): Promise<URI> {

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.46.0 OS Version: Windows 10/macOS Catalina 10.15.4 VS Code 1.46 no longer executes the Attached test extension (rename file extension to .vsix) which creates a file on uninstall in the user's home directory. Using VS Code 1.45.1 the file is created on both Windows and macOS. Using VS Code 1.46 no file is created. Steps to Reproduce: attached extension extension VS Code VS Code again file is created <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: This is an extension management problem
Change:
cursor: initial; } <ins> .debug-pane .monaco-list:focus .monaco-list-row.selected .state.label, .debug-pane .monaco-list:focus .monaco-list-row.selected .load-all, .debug-pane .monaco-list:focus .monaco-list-row.selected.focused .state.label { color: inherit; } </ins> /* Call stack */ .debug-pane .call-stack-state-message {

Discussion:
If I focus the callstack row, I can't read "Paused on breakpoint" or see the debug command buttons with the new list focus color !
Thanks for fixing
For verification: start a debug session and verify that selecting a call stack row shows the icons correctly in dark/light. Also ensure the icons in the toolbar (docked and floating) appear correctly.
Change:
@ISpeechService private readonly speechService: ISpeechService, @ILogService private readonly logService: ILogService ) { <del> super(); </del> this.proxy = extHostContext.getProxy(ExtHostContext.ExtHostSpeech); }

Discussion:
Testing Kept playing with "hey code", at one point the EH restarted (unsure why but likely due to speech). Anyways, the console showed the error below which likely means some didn't dispose something. Once you are in this state speech is broken
Steps open vscode, start speech F1 restart EH error shows, speech is broken
I always keep forgetting this in , we should probably have some kind of lint rule...
Change:
"name": "Strings: Regular Expressions", "scope": "string.regexp", "settings": { <del> "foreground": "#4B83CD" </del> <ins> "foreground": "#4B69C6" </ins> } }, {

Discussion:
Environment Details: VSCode Version : 1.25.0 OS Version : Win10 Additional Details: HighContrast,MAS1.4.3 Repro Steps: Visual Studio code desktop application. to "Plain Text" of "Status Bar"-Enter "PowerShell" in "Select Language Mode" combo box-Write the PowerShell Code in plain editor-Save the editor. to Setting button of Activity Bar and select "Color Theme" option. Themes shows number of different colors list apply all that theme on the editor. color contrast analyser and check the color contrast ratio. shows color contrast ratio less than expected color contrast ratio. Actual: After applying color themes to editor it shows color contrast ratio as 3.5:1 eg. Select "QuietLight" theme from color theme list and check for the color contrast ratio. Expected: The expected colorcontrast ratio should be greater than or equals to 7:1 ratio. Recommendations: Refer below link which is repository of bug fixes code  User Impact: User will not able to see the content of the editor. MAS Reference: MAS1.4.3- Attachment For Reference: ! Does this issue occur when all extensions are disabled?: Yes
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.701 --- <!-- score: 0.617 --- <!-- score: 0.552 --- <!-- score: 0.508 --<!-- potentialduplicatescomment --
I believe you are using the wrong color contrast ratio. From the link you provided: We've only been targeting the minimum contrast ratio, which is Level AA at 4.5:1
Change:
}, "scripts": { "test": "node node_modules/mocha/bin/_mocha", <del> "preinstall": "node build/npm/preinstall.js", </del> <ins> "preinstall": "node build/npm/preinstall.js", </ins> "postinstall": "npm --prefix extensions/csharp-o/ install extensions/csharp-o/ && npm --prefix extensions/vscode-api-tests/ install extensions/vscode-api-tests/" }, "dependencies": {

Discussion:
This will let the Setup installer not go ahead and perform an update/install if Code is running.
We already have a native app mutex node module which we could use for this.
Change:
) { super(WebviewEditor.ID, telemetryService, themeService, storageService); <del> this._register(editorGroupsService.onDidScroll(() => { </del> <ins> this._register(Event.any( editorGroupsService.onDidScroll, editorGroupsService.onDidAddGroup, editorGroupsService.onDidRemoveGroup, editorGroupsService.onDidMoveGroup, )(() => { </ins> if (this.webview && this._visible) { this.synchronizeWebviewContainerDimensions(this.webview); }

Discussion:
Repro: Get in this state: <img width="869" alt="image" src="https://user-"Close the right editor group: <img width="864" alt="image" src="https://user-"Version: 1.76.0-insider (user setup) Commit: Date: 2023-02-08T12:47:14.528Z Electron: 19.1.9 Chromium: 102.0.5005.194 16.14.2 V8: 10.2.154.23-electron.0 OS: Windows_NT x64 10.0. Sandboxed: Yes
Actually seems like a generic webview issue
Fixed webview layout issue but now it seems like we also need a fix to the markdown extension
Actually not a bug. If you have two editors and side but side with a preview below , closing switches focus to the preview tab. However the preview stays for the content of This is now a duplicate of . To verify this issue: two editors and side by side a markdown preview below the entire group and confirm that the preview still shows its contents