jiebi/CodeConvo huggingface dataset:
Change:
"language": "scss", "scopeName": "source.css.scss", "path": "./syntaxes/scss.tmLanguage.json" <ins> }, { "scopeName": "source.sassdoc", "path": "./syntaxes/sassdoc.tmLanguage.json" </ins> }], "problemMatchers": [{ "name": "node-sass",

Discussion:
It looks like Code is using 0.52.0 of to generate its Sass syntax — 0.62.0 was released today. It would be great to have the new fixes & features included. I'm happy to submit a PR with the re-generated syntax.
Thanks for the update! Just a heads-up though, the updated SCSS syntax references a separate file for SassDoc comment blocks. I updated the build script to account for the extra file in my PR:
Change:
.monaco-workbench .part.statusbar > .items-container > .statusbar-item > a:hover:not(.disabled) { text-decoration: none; <ins> color: var(--vscode-statusBarItem-hoverForeground); </ins> } .monaco-workbench .part.statusbar > .items-container > .statusbar-item > a.disabled {

Discussion:
Hi. i am creating a theme pack for VSCode. I have discovered that there is a to customize the background color of a status bar hovered item but there is no option to customize the color of the hovered item foreground color. Something like !
<!-- -96bd-47a8-a0e8- --This feature request is now a candidate for our backlog. The community has 60 days to the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our . Happy Coding!
Yeah there seems to be colors like but not the relevant foreground colors. //cc
Added with values defaulting to in . You'll be able to set that manually in your or in the theme itself.
nice, but we do have more hover backgrounds: <img width="725" alt="image" src=""I am not sure about the compact one but maybe prominent one needs it too?
Added via
Change:
testInvalidTypeError([null], 'null', false); testInvalidTypeError('null', 'null', false); }); <ins> test('uri checks work', () => { const tester = new Tester({ type: 'string', format: 'uri' }); tester.rejects('example.com'); tester.rejects('example.com/example'); tester.rejects('example/example.html'); tester.rejects('www.example.com'); tester.rejects(''); tester.rejects(' '); tester.rejects('example'); tester.accepts('https:'); tester.accepts('https://'); tester.accepts('https://example.com'); tester.accepts('https://www.example.com'); }); </ins> });

Discussion:
Found this issue while trying to set 's format to uri (or uri-reference), in order to fix <!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.42.0-insider () OS Version: Mac OS 10.14.6 Steps to Reproduce: a "mysetting" setting define "format":"uri" (as documented in ) settings in UI, write then delete some value, no error is shown , see that has a warning: <img width="1155" alt="Screen Shot 2020-01-15 at 7 44 33 PM" src="https://user-"The validation error should be displayed in the UI too (as it does when using a validation pattern) <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Maybe
I guess we are missing that validation, also, the type of that setting should be if the default is "null".
I can try working on this. Any code pointers, though? Not sure where to look.
See for where these validations for the settings editor live. You need to figure out what validation the json language server does for . I assume that lives somewhere in but I don't know where. I can help you if you can't find it.
Verifier: the extension and search in the settings editor different values in the textbox that shows up. The empty string should not be accepted, and a string such as should not be accepted. However, , , and should be accepted.
This bug has been fixed in to the latest release of ! you can help us out by confirming things are working as expected in the latest Insiders release. If things look good, please leave a comment with the text to let us know. If not, 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!
Change:
repository.provider.onDidChangeResourceGroups, () => repository.provider.groups.find(g => g.id === groupId) )); <ins> const scmActivities = observableFromEvent( this._activityService.onDidChangeActivity, () => [...this._activityService.getViewContainerActivities('workbench.view.scm')], ); const scmViewHasNoProgressBadge = scmActivities.map(activities => !activities.some(a => a.badge instanceof ProgressBadge)); await waitForState(scmViewHasNoProgressBadge, v => v); </ins> return new ScmResolvedMultiDiffSource(group, repository); } }

Discussion:
open a multifile diff reload window while the diff editor stores and loads it says that there are no changes yet <img width="1178" alt="Screenshot 2024-06-21 at 09 16 43" src=""
Thanks for filing! Briefly looked into it, but fixing it is a little bit more complex than I thought. The model creation is what takes a while, and during that time the multi file diff editor just has no model. It would be better if the model creation is immediate, but it has some property, that the editor could then show.
Change:
type: 'boolean', default: true }, <ins> [TerminalSettingId.ShowLinkHover]: { scope: ConfigurationScope.APPLICATION, description: localize('terminal.integrated.showLinkHover', "Whether to show hovers for links in the terminal output."), type: 'boolean', default: true } </ins> } };

Discussion:
Forking off the setting part off from PR:
Hello, is this issue is still open. I am new to open source and wanted to contribute.
there's a PR open already for this one
Change:
import { ShutdownReason } from 'vs/workbench/services/lifecycle/common/lifecycle'; import { ITelemetryService } from 'vs/platform/telemetry/common/telemetry'; import { Barrier } from 'vs/base/common/async'; <ins> import { IEnvironmentService } from 'vs/platform/environment/common/environment'; </ins> type NativeCodeWindow = CodeWindow & { readonly vscode: ISandboxGlobals;

Discussion:
Since the november 2023 update steals window focus. This is really problematic because uses this to run end to end tests and now the development host window pops up for every single test case, which renders all other windows unusable while I’m running tests, as the test window steals focus many times per second. <!-- 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.1 (user setup) OS Version: Windows_NT x64 10.0. Steps to Reproduce: extension host vscode main window the following code: vscode extension development host window is now focused.
We should add rules to not change focus during extension development tests.
<!-- 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!
I can reproduce this: an extension that activates : 5, and immediately focus back to the VS Code window you F5'd from When executes, the ext dev host window will regain focus
Sorry, bad description: its only disabled when running extension tests.
Change:
const notificationService = accessor.get(INotificationService); const instantiationService = accessor.get(IInstantiationService); <del> const context = explorerService.getContext(true); </del> <ins> const context = explorerService.getContext(false); </ins> const element = context.length ? context[0] : explorerService.roots[0]; try {

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.82.0-insider () OS Version: Windows_NT x64 10.0. Steps to Reproduce: a directory with 2 files and a directory and , right-click, Copy -click , Paste Expected: and are pasted in Actual: and are pasted in
This issue has existed for a while and it's bitten me a few times. I found in order for copy/paste to work as expected the destination folder must first be selected before right-click.
Change:
constructor( @IEditorService private readonly _editorService: IEditorService, <del> @ITerminalEditorService private readonly _terminalService: ITerminalService, </del> <ins> @ITerminalService private readonly _terminalService: ITerminalService, </ins> @ITerminalEditorService private readonly _terminalEditorService: ITerminalEditorService, @ITerminalGroupService private readonly _terminalGroupService: ITerminalGroupService, @ICommandService private readonly _commandService: ICommandService,

Discussion:
Hi, The terminal option is not deleting and terminal option is not renaming correctly in command palette. Version: Commit: 8b617bd08fd9e3fc94d14adb8d358b56e3f72314Edition: Version: OS build: : Id: Description: Fluent product icons for Visual Studio Code Version: 0.0.18 Publisher: Miguel Solorio : Id: Description: Material Design Icons for Visual Studio Code Version: 4.30.1 Publisher: Philipp Kief Vscode. internal terminals. command palatte type to list terminals. to a terminal using delete icon button. to a terminal using rename icon button. corresponding terminal on clicking . corresponding terminal on clicking . not deleted ( clicking did nothing ). last terminal in the list of terminals instead of corresponding terminal. error when tried to delete terminal: ! Also, can we change the rename terminal icon to codicon. It would be much easier to understand than codicon.
works for me but I can repro not working.
Hi, let me explain the terminal rename issue again Steps to reproduce the issue 3 terminals ! 2nd terminal rename option ! terminal name from to ! but After rename, 3rd terminal is renamed instead of 2nd terminal ! My VSCode settings:
Change:
// We need to disconnect the management connection before killing the local extension host. // Otherwise, the local extension host might terminate the underlying tunnel before the // management connection has a chance to send its disconnection message. <del> await this._remoteAgentService.endConnection(); await this._doStopExtensionHosts(); this._remoteAgentService.getConnection()?.dispose(); </del> <ins> try { await this._remoteAgentService.endConnection(); await this._doStopExtensionHosts(); this._remoteAgentService.getConnection()?.dispose(); } catch { this._logService.warn('Error while disconnecting remote agent'); } </ins> }, { id: 'join.disconnectRemote', label: nls.localize('disconnectRemote', "Disconnect Remote Agent"),

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.92.2(user setup) OS Version: Windows_NT x64 10.0. Steps to Reproduce: the Remote for ssh open a folder File -Save workspace as ... a folder to save the workspace file the windows, then we can get a message 'Reloading the window is longer...' ! vscode window is hanged up and can not closed manually. only way to reopen it is force close it by Task Manager. I can give more information if it need.
Please see if you can find any logged output that could help us find the source of the issue: run from the command line reproduce the issue attach the log files you find from running the command "Open Logs Folder" Thanks!
I got those logs. Please check it .
Looks like a unhealthy connection to me:
The vscode client is on Windows_NT x64 10.0., Remote SSH server is a host which the network is same with the vscode client. such as 10.0.0.44 -10.0.1.245:ssh. The client conntected to the server by ssh with a domain name. And the domain name is valid and always avaiable for me. So it is not a ssh or network connection problem. There must be some wrong with the vscode or Remote for SSH plugin. I do not know why the log file say 'Error: Cannot resolve authority'.
Having the same experience, with the same setup. Same network, windows 10 ssh to linux client. Happens on two linux machines from my Windows machine.

I'm also encountering this (windows -linux) and have to use the task manager to close VSCode (on 1.92.2). Particularly, this happens when debugging an extension in an extension host window.
Change:
throw new Error(`Unable to extract tag names from error message: ${raw}`); } <del> // Notification const replaceLocalTags = l10n.t('Replace Local Tag(s)'); const message = l10n.t('Unable to pull from remote repository due to conflicting tag(s): {0}. Would you like to resolve the conflict by replacing the local tag(s)?', tags.join(', ')); const choice = await window.showErrorMessage(message, { modal: true }, replaceLocalTags); </del> <ins> const config = workspace.getConfiguration('git', Uri.file(this.repository.root)); const replaceTagsWhenPull = config.get<boolean>('replaceTagsWhenPull', false) === true; if (!replaceTagsWhenPull) { // Notification const replaceLocalTags = l10n.t('Replace Local Tag(s)'); const replaceLocalTagsAlways = l10n.t('Always Replace Local Tag(s)'); const message = l10n.t('Unable to pull from remote repository due to conflicting tag(s): {0}. Would you like to resolve the conflict by replacing the local tag(s)?', tags.join(', ')); const choice = await window.showErrorMessage(message, { modal: true }, replaceLocalTags, replaceLocalTagsAlways); if (choice !== replaceLocalTags && choice !== replaceLocalTagsAlways) { return false; } </ins> <del> if (choice !== replaceLocalTags) { return false; </del> <ins> if (choice === replaceLocalTagsAlways) { await config.update('replaceTagsWhenPull', true, true); } </ins> } // Force fetch tags

Discussion:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --Is it possible to have a setting that would automatically replace the local tags rather than always prompting? Thx
Even, I am also looking for a similar functionality.
<!-- -96bd-47a8-a0e8- --This feature request is now a candidate for our backlog. The community has 60 days to the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our . Happy Coding!
+1
We are now "moving" a tag to track the last successful build in our CI/CD process for users who don't have a lot of CI/CD or Git experience. We want them to naturally see the tag slide up as the team makes changes and the server succeeds in processing them. It's very jarring to have this modal pop up and have no way of hiding it.
Tomorrow's (2024-02-14) VS Code Insiders release has an updated dialog that has an "Always Replace Local Tag(s)" button. Pressing the button will toggle the so if you wish you can proactively enable this setting in your users/workspace/folder settings. Please give it a try and let me know if you run into any issues. Thanks! <img width="265" alt="image" src=""
Change:
position: absolute; bottom: 0; top: 0; <ins> padding-bottom: 2px; </ins> } .monaco-workbench .panel.integrated-terminal .xterm a:not(.xterm-invalid-link) {

Discussion:
<!-- Do you have a question? Please ask it on --<!-- Use Help Report Issues to prefill these. --- VSCode Version: latest OS Version: Win10 A little bit more space between last line from terminal and the blue line below would be nice !
I 1px border on the bottom would be fine, opening to PRs. Who ever wants to pick this up, you need to make sure the size of the terminal is calculated correctly given the new margin. Relevant files: , .
I'll pick this up. pretty much all of the other terminal issues are already taken, or out of my realm. just let me know somebody's not already working on this ;-)
sounds good
PR posted
Change:
this.splitView.setViewVisible(0, true); } } <ins> progressRunner.done(); </ins> } /**

Discussion:
I don't have precise repro steps, but maybe: search for something scroll all the way down clear search searching animation persists
I'm unable to repro the issue. Let me know if there's any devtools errors next time it occurs.
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
just reproduced this and will give us the logs
In the case of JooYoung, the search wasn't performed at all.
just reproduced myself
The error likely means there's an array that's undefined, but I'll probably have to reproduce the issue on OSS to actually see what's going on Example REPL run
it takes much longer than expected to stop - is there a long happening for input change or... ?
I'm unable to repro on the latest Insiders on Windows or macOS. For me, clearing the search stops it immediately.
Change:
.monaco-editor .find-widget { position: absolute; z-index: 10; <del> top: -44px; </del> height: 33px; overflow: hidden; line-height: 19px; <del> transition: top 200ms linear; </del> <ins> transition: transform 200ms linear; </ins> padding: 0 4px; box-sizing: border-box; <ins> transform: translateY(Calc(-100% - 10px)); /* shadow (10px) */ </ins> } .monaco-editor .find-widget.hiddenEditor {

Discussion:
Issue Type: <bBug</bSteps to Reproduce: any file to open the Search and Replace bar the Replace field, hit to add a line return the bar --The bottom of the bar is visible while closed. ! VS Code version: Code 1.39.2 (, 2019-10-15T15:33:40.634Z) OS version: Linux x64 5.0.0-32-generic <details<summarySystem Info</summary </details<details<summaryExtensions (18)</summaryExtensionVersion ------ vscode-intelephense-client1.2.3 vscode-tailwindcss0.2.0 gitlens10.1.1 auto-rename-tag0.1.0 gc-excelviewer2.1.32 todo-tree0.0.160 graphql-for-vscode1.15.1 rainbow-csv1.3.1 git-graph1.17.0 dotenv1.0.1 language-gettext0.1.1 vscode-typescript-tslint-plugin1.2.2 vsliveshare1.0.988 debugger-for-chrome4.12.0 material-icon-theme3.9.1 partial-diff1.4.0 ayu0.18.0 change-case1.0.0 (1 theme extensions excluded) </details<!-- generated by issue reporter --
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.467 --<!-- potentialduplicatescomment --
This is not a duplicate.
I hope you don't mind but I had a look into this and I've fixed it. Should I bother with a PR or leave it to you? It only adds if the contains , it doesn't check . However, I noticed that if is , you don't get the animation (slide down/up). I think a better solution may be to animate on transform.
not at all, feel free to send out your work and thanks for your contribution!
Change:
* Options to configure the behavior of the quick pick UI. */ export interface QuickPickOptions { <ins> /** * An optional string that represents the tile of the quick pick. */ title?: string; </ins> /** * An optional flag to include the description when filtering the picks. */

Discussion:
Currently, can only be set when going through the more complex API. It would be great if the title could be set via when using the simpler .
proposal: for quickpick or Input: This basically meshes with UI in: and in the class itself here: cc
what extensions have to do now in order to get the base functionality + a title:
In API sync there was no pushback or additional comments. I have moved to implementation ^
I will reopen this for API finalization next week.
This was covered on so there's nothing else to do here besides wait for the next release of vscode types :)
Change:
@ILanguageService private readonly languageService: ILanguageService, @IExtensionManagementService extensionManagementService: IExtensionManagementService, @IProductService private readonly productService: IProductService, <del> @IEnvironmentService private readonly environmentService: IEnvironmentService, </del> @IExtensionGalleryService private readonly extensionGalleryService: IExtensionGalleryService, @IEditorProgressService private readonly editorProgressService: IEditorProgressService, ) {

Discussion:
On the latest Stable or Insiders, the Copilot setting button does not show up in the Settings editor when the Copilot extension is disabled or not installed. ! removed the dependency on the assignment/experimentation service incorrectly, and ended up making it so that the feature was only available in OSS aka from-source builds. The main branch fix is available in The candidate PR is available in . [x] Set up a candidate PR
Change:
} return Iterator.map(iterator, treeElement => { <del> const node = this.nodes.get(treeElement.element); </del> <ins> let node = this.nodes.get(treeElement.element); if (!node && this.identityProvider) { const id = this.identityProvider.getId(treeElement.element).toString(); node = this.nodesByIdentity.get(id); } </ins> if (!node) { return {

Discussion:
Issue Type: <bBug</bTesting Repo settings editor to the section click to switch to instead of Bug TOC is collapsed. Any scrolling causes the TOC to be expanded at the correctly again VS Code version: Code - Insiders 1.31.0-insider (, 2019-01-29T06:13:57.866Z) OS version: Darwin x64 18.2.0 <details<summarySystem Info</summary </details<!-- generated by issue reporter --
Probably another case of The TOC tree sometimes maintains its selection/expansion state, sometimes not.
Hey should expansion state be preserved using the string identity? was for focus/selection, this is for expansion state.
Adding myself so I don't forget about this.
Let's merge this early June:
Thanks