jiebi/CodeConvo huggingface dataset:
Change:
padding-right: 5px; } <del> .monaco-workbench .progress-badge > .badge-content { background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSIxNCIgaGVpZ2h0PSIxNCIgdmlld0JveD0iMiAyIDE0IDE0IiBlbmFibGUtYmFja2dyb3VuZD0ibmV3IDIgMiAxNCAxNCI+PHBhdGggZmlsbD0iI2ZmZiIgZD0iTTkgMTZjLTMuODYgMC03LTMuMTQtNy03czMuMTQtNyA3LTdjMy44NTkgMCA3IDMuMTQxIDcgN3MtMy4xNDEgNy03IDd6bTAtMTIuNmMtMy4wODggMC01LjYgMi41MTMtNS42IDUuNnMyLjUxMiA1LjYgNS42IDUuNiA1LjYtMi41MTIgNS42LTUuNi0yLjUxMi01LjYtNS42LTUuNnptMy44NiA3LjFsLTMuMTYtMS44OTZ2LTMuODA0aC0xLjR2NC41OTZsMy44NCAyLjMwNS43Mi0xLjIwMXoiLz48L3N2Zz4="); background-position: center center; background-repeat: no-repeat; </del> <ins> .monaco-workbench .progress-badge > .badge-content::before { -webkit-mask: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSIxNCIgaGVpZ2h0PSIxNCIgdmlld0JveD0iMiAyIDE0IDE0IiBlbmFibGUtYmFja2dyb3VuZD0ibmV3IDIgMiAxNCAxNCI+PHBhdGggZmlsbD0iI2ZmZiIgZD0iTTkgMTZjLTMuODYgMC03LTMuMTQtNy03czMuMTQtNyA3LTdjMy44NTkgMCA3IDMuMTQxIDcgN3MtMy4xNDEgNy03IDd6bTAtMTIuNmMtMy4wODggMC01LjYgMi41MTMtNS42IDUuNnMyLjUxMiA1LjYgNS42IDUuNiA1LjYtMi41MTIgNS42LTUuNi0yLjUxMi01LjYtNS42LTUuNnptMy44NiA3LjFsLTMuMTYtMS44OTZ2LTMuODA0aC0xLjR2NC41OTZsMy44NCAyLjMwNS43Mi0xLjIwMXoiLz48L3N2Zz4="); width: 14px; height: 14px; position: absolute; top: 1px; left: 1px; background-color: currentColor; content: ''; </ins> }

Discussion:
! I am currently building a theme and want to change the color of the clock that is white inside the yelloq circle. It's color is and i changed all colorsettings in my theme file that had that hexcode to a different color, but the clock stays at . There is a foreground color option for numbers (and text in general i suppose) that i already changed, it looks like this: !
Happy for help if someone has ideas. The challenge is to make it possible to theme the white background of that progress icon (living in ). It should leverage the for the color that is currently white and for the color that is currently blue. /cc
My proposal: move away from an image to a unicode character like
Question, how does one make the clock icon appear from repo version of Code? I'm currently working on this, but I need to figure out how to visually see the icon. Ideas?
e.g. open a very large git repository and click refresh from the git viewlet. Or install an extension.
You can also just check for updates via right click on it and it will appear for a short time.
Also, you can download this extension and use "Show Progress Badge" command.
Is this still being worked on? is not doing anything as far as I know.
I believe it should be possible with few steps: the SVG icon from base64 to text (xml) it into the HTML Maybe with something like CSS "fill" property to change color of icon to the "activityBarBadge.foreground"
If anyone is interested, here is the code pointer to where the badge indicator is set:
Verification steps: Install the extension and run the command and modify the color token via: The icon should now inherit the same color.
Change:
export const DEFAULT_TERMINAL_OSX = 'Terminal.app'; <del> export const DEFAULT_TERMINAL_WINDOWS = '%COMSPEC%'; </del> <ins> export const DEFAULT_TERMINAL_WINDOWS = `${process.env.windir}${process.env.hasOwnProperty('PROCESSOR_ARCHITEW6432') ? 'Sysnative' : 'System32'}cmd.exe`; </ins> export interface ITerminalConfiguration { terminal: {

Discussion:
From a normal Windows command prompt, will stop a node server running. However, if I start the command prompt via the menu item , then pressing (even multiple times) does not stop the server as usual. Running on Windows 10 x64 VS Code 1.11.2 Also asked on SO:
does this still happen when you add this to your settings?
If I add that setting it works fine. Note after I install VS Code it already has similar setting: // Place your settings in this file to overwrite the default settings { "window.zoomLevel": 0.5, "": "C:WINDOWSSysnative", "terminal.external.windowsExec": "C:Windowssysnative" }
We should just hardcode 32/64-bit then if that works, right now we point to the environment variable that defaults to the 32-bit version of regardless of what version of Windows you're on.
I can reproduce. This has been a bug for the longest time. Also this true not just for node processes. E.g. when I launch a go web service that I'm developing.
I merged which should select the sysnative version. I noticed two things though, firstly I couldn't reproduce the issue on my machine (Windows 10 64-bit), plus I didn't see it change to Sysnative using the same trick we used to fix a similar issue with 64-bit PowerShell. This may be blocked by shipping a 64-bit version of VS Code. I'm interested to hear if the problem is fixed in Insiders on Monday.
I'll test when this gets released.
Works for me, adding verified.
Edit: found an open issue more appropriate....
Change:
this.registerViews(); this.onConfigurationUpdated(); this._register(this.configurationService.onDidUpdateConfiguration(e => this.onConfigurationUpdated())); <ins> this._register(this.contextService.onDidChangeWorkspaceRoots(e => this.onWorkspaceRootsChanged())); </ins> } public create(parent: Builder): TPromise<void> {

Discussion:
Today we show the workspace name it seems.
! What does "title" mean? 1 or 2?
2
It should be FOLDERS in multi root mode, and foldername_ otherwise, right?
Right
It behaves exactly in this way currently. I suppose this issue should be closed.
We should first ask if he can still repro this issue since is not seeing it, are tehre special repro steps
There are no special steps to repro this, so please confirm
!
I still cannot reproduce this. Also, your layout differs from mine - control buttons on the EXPLORER bar. Could you please explain, how I can switch VSCode into such a view?
I have "open editors" section disabled.
Change:
let resource; if (folders.length === 1) { resource = folders[0].uri; <del> } else if (workspace.configuration) { </del> <ins> } else if (workspace.configuration && !isUntitledWorkspace(workspace.configuration, this.environmentService)) { </ins> resource = workspace.configuration; } const link = URI.parse(connectionInfo.link);

Discussion:
an untitled workspace (e.g. open and use to add ) browser URI to clipboard <img width="746" alt="image" src="https://user-"url into browser :bug: fails to open workspace <img width="509" alt="image" src="https://user-"Should this command prompt to save the open workspace if it's not saved already (or just point to the user root directory)?
Also, this action always copies a url-encoded filepath, e.g. becomes , which also yields a "Workspace does not exist" warning message.
Change:
} }); <ins> test('scoreItem - ensure upper case bonus only applies on non-consecutive matches (bug #134723)', function () { const resourceWithUpper = URI.file('ASDFasdfasdf'); const resourceAllLower = URI.file('asdfasdfasdf'); assert.ok(scoreItem(resourceAllLower, 'asdf', true, ResourceAccessor).score > scoreItem(resourceWithUpper, 'asdf', true, ResourceAccessor).score); }); </ins> test('compareItemsByScore - identity', function () { const resourceA = URI.file('/some/path/fileA.txt'); const resourceB = URI.file('/some/path/other/fileB.txt');

Discussion:
Issue Type: <bBug</bI have two files in my project in different locations. and . The 'search in files' popup always shows first, event when searching for the latter: ! please include case-sensitivity in the sort function for this. VS Code version: Code 1.60.2 (, 2021-09-22T12:00:31.514Z) OS version: WindowsNT x64 10.0. Restricted Mode: No Remote OS version: Linux x64 5.10.16.3-microsoft-standard-WSL2 Remote OS version: Linux x64 5.10.16.3-microsoft-standard-WSL2 Remote OS version: Linux x64 5.10.16.3-microsoft-standard-WSL2 Remote OS version: Linux x64 5.10.16.3-microsoft-standard-WSL2 <details<summarySystem Info</summary </details<details<summaryExtensions (5)</summaryExtensionVersion ------ jupyter-keymap1.0.0 remote-ssh0.65.8 remote-ssh-edit0.65.8 remote-wsl0.58.2 hexeditor1.8.2 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Change:
const configuration: IConfigurationNode = { ...accessibilityConfigurationNodeBase, <ins> scope: ConfigurationScope.RESOURCE, </ins> properties: { [AccessibilityVerbositySettingId.Terminal]: { description: localize('verbosity.terminal.description', 'Provide information about how to access the terminal accessibility help menu when the terminal is focused.'),

Discussion:
VS Code Version: Version : 1.87.1 Validation : Date : 2024-03-06T00:22:39.156Z Electron : 27.3.2 ElectronBuildId : Chromium : 118.0.5993.159 : 18.17.1 V8 : 11.8.172.18-electron.0 Système d’exploitation : Darwin arm64 23.3.0 Steps to Reproduce: Just launch VS Code and get an error message like in picture joined. I don't know how to not get them <img width="582" alt="Capture d’écran 2024-03-07 à 19 40 25" src=""
any ideas here ? rough translation: "Unable to be described in folder settings because does not support the scope of folder resources"
Repro steps a multi-root workspace. the setting to the files of one of those workspaces. the window. :bug: The dialogs show up.
and what should I do to remove this error message ???
A workaround would be: which root folder in the multi-root workspace has defined in . the multi-root workspace, and open that root folder in a separate VS Code window. The editor should automatically migrate over the outdated setting. the multi-root workspace again.
Hi, i am sorry i don't think that i understood precisely what you meant by: Check which root folder in the multi-root workspace has defined in Close the multi-root workspace, and open that root folder in a separate VS Code window. The editor should automatically migrate over the outdated setting. Open the multi-root workspace again. Can you be clearer please ? I am relatively new to VsCode Thanks
how can I do to get rid off the error message ? Thx
English repro looks like this: <img width="402" alt="Screenshot 2024-04-04 at 6 50 20 AM" src=""
Change:
{ "name": "code-oss-dev", "version": "1.83.0", <del> "distro": "e61050c5d43d2c66a196fafaa2b78d4f2a8c929a", </del> <ins> "distro": "843239091771548f8641e7125413223827657911", </ins> "author": { "name": "Microsoft Corporation" },

Discussion:
The Python debugger extension has adopted the portsAttributes API to help us gain confidence in the API before finalization. Not granting that extension access to the API was an oversight.
<!-- UNABLETOLOCATECOMMITMESSAGE issue --Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting , or directly add the label if you know this has already been releaased
closedWith
Change:
{ "name": "code-oss-dev", <del> "version": "1.55.0", </del> <ins> "version": "1.56.0", </ins> "distro": "c57566e89bbb245d7e1a5d789b9367f5a7b8bc05", "author": { "name": "Microsoft Corporation"

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: --Hitting + with the terminal focused and a process running (i.e. in a React app) does not kill the process. If someone is able to provide a good starting point, I would be willing to take a stab at this. <!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.53.0-insider OS Version: iPadOS 14.1 (18A8395) Commit: Date: 2021-01-07T05:25:51.740Z (16 hrs ago) Browser: Mozilla/5.0 (iPad; CPU OS 14_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/87.0.4280.77 Mobile/15E148 Safari/604.1 iPad, open Codespaces environment in Chrome integrated Terminal application (i.e. like a create-react-app - ) terminal and hit + Process () should stop running Terminal receives new line https://user- <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes Related:
Perhaps that is not the right sigint.
One other piece of insight: this may not be limited to VSCode. has a product which includes a terminal in the browser. I’m able to reproduce the same issue (see line breaks at the bottom). !
As a temporary workaround, it works if you manually define the shortcut like so: Command Palette for "Preferences: Open Keyboard Shortcuts (JSON)" this: Source:
I found the root reason was iPad Safari report keyCode of ctrl-c as 13, which is not correct, reference from MDN, keyCode is a deprecated property; The key and code property is right, so I suggest just use key property, not keyCode, on the whole html page not just terminal.
I'm still seeing this in codespace, am I testing the right environment?
fixed w
as another workaround, use shortcut instead of , it will interrupt the process as well
Change:
return; } if (keyboardEvent.equals(KeyCode.Escape)) { <del> if (this._chords !== null) { this.clear(); } </del> this._onEscape.fire(); return; }

Discussion:
Type: <bBug</bPreviously pressing escape while "Record Keys" was active in the keybindings UI would disable key recording and leave the search query intact. Now it disables key recording and clears the search query which makes it much harder to use. I traced this regression to 1.78. I'm guessing this is an issue with keybindings. The binding for is being processed in addition to the (hard-coded?) binding to stop recording. ! VS Code version: Code - Insiders 1.79.0-insider (, 2023-05-04T22:11:08.187Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: Yes <details<summarySystem Info</summary </detailsExtensions: none<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Change:
if (i === this._primarySelection.endLineNumber) { selectionEndOffset += this._primarySelection.endColumn - 1; } else { <del> selectionEndOffset += this._context.viewModel.getLineMaxColumn(i); </del> <ins> selectionEndOffset += this._context.viewModel.model.getLineMaxColumn(i); </ins> } } <del> const endColumnOfEndLineNumber = this._context.viewModel.getLineMaxColumn(this._primarySelection.endLineNumber); </del> <ins> const endColumnOfEndLineNumber = this._context.viewModel.model.getLineMaxColumn(this._primarySelection.endLineNumber); </ins> const rangeOfText = new Range(this._primarySelection.startLineNumber, 1, this._primarySelection.endLineNumber, endColumnOfEndLineNumber); <del> const text = this._context.viewModel.getValueInRange(rangeOfText, EndOfLinePreference.TextDefined); </del> <ins> const text = this._context.viewModel.model.getValueInRange(rangeOfText, EndOfLinePreference.TextDefined); </ins> const textStartPositionWithinEditor = rangeOfText.getStartPosition(); return { text,

Discussion:
Enable the setting which enabled the native edit context adoption (make sure to reload the editor) Toggle word wrap on Resize the editor, so one of the lines is wrapped Type on that line Part of the line is deleted/incorrectly edited
Looks like this could be an issue with the coordinate system chosen too.
Change:
'!build/{lib,tslintRules}/**/*.js', '!build/**/*.sh', '!build/tfs/**/*.js', <ins> '!build/tfs/**/*.config', </ins> '!**/Dockerfile', '!extensions/markdown-language-features/media/*.js' ];

Discussion:
is from an unknown publisher
!
Oh it really seems like you can't uninstall it... Not good.
Related to

Unlike the VS Code installer for Windows, the VS Code uninstaller for Windows is not signed. You can fix this by using the directive in your Inno Setup script. See For dual signing it's easiest to use Inno Setup 5.5.8 instead of 5.5.6 as you currently use: 5.5.8 allows you to have two SignTool directives, one for the sha-1 signing and another for the sha-256 signing.
To keep the number of issues in our inbox on a manageable level, we're closing issues that have been on the backlog for a long time but haven't gained traction: We look at the number of votes the issue has received and the number of duplicates issues filed. Thanks for your understanding. Happy coding!
Change:
"activityBar.dropBackground": "#414339", "sideBar.background": "#1e1f1c", "sideBarSectionHeader.background": "#272822", <ins> "menu.background": "#1e1f1c", "menu.foreground": "#cccccc", </ins> "pickerGroup.foreground": "#75715E", "input.background": "#414339", "inputOption.activeBorder": "#75715E",

Discussion:
Issue Type: <bBug</bI think this change appeared in VS Code Insiders couple builds ago. New background for dropdowns in title menu bar and context menus ( is set to ) now have brighter background, which has to much contrast with editor background and makes it harder to read text on it. Also it appears much brighter than backgrounds for auto-suggestions dropdown and peek view. Is it intended change in Dark+ color theme or is it possible to revert it back to the same color as in current stable version (1.27)? Insider (left) and stable (right) ! VS Code version: Code - Insiders 1.28.0-insider (, 2018-09-19T09:34:25.276Z) OS version: Windows_NT x64 10.0. Issue is reproducible without extensions. <details<summaryExtensions (26)</summaryExtensionVersion ------ markdown-toc1.5.6 vscode-css-modules1.0.1 spellright2.5.32 markdown-preview-github-styles0.1.3 vscode-css-modules0.2.3 bracket-pair-colorizer1.0.60 vscode-eslint1.6.0 gitlens8.5.6 remotehub0.2.0 EditorConfig0.12.4 tslint1.0.39 vscode-pull-request-github0.1.5 beautify1.4.3 rest-client0.19.1 code-fragments1.2.0 vsliveshare0.3.709 debugger-for-chrome4.10.1 debugger-for-edge1.0.5 vscode-docker0.2.0 material-icon-theme3.6.0 quicktype12.0.42 gi0.2.11 code-settings-sync3.1.2 dot0.0.1 quokka-vscode1.0.149 markdown-pdf1.2.0 </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.459 --<!-- potentialduplicatescomment --
Change:
private readonly _disposables = new DisposableStore(); private readonly _breadcrumbsDisposables = new DisposableStore(); private readonly _labels: ResourceLabels; <ins> private readonly _model = new MutableDisposable<BreadcrumbsModel>(); </ins> private _breadcrumbsPickerShowing = false; private _breadcrumbsPickerIgnoreOnceItem: BreadcrumbsItem | undefined;

Discussion:
profile on startup and have a css file opened the registers a fs provider for this somehow ends up causing a dom layout via the breadcrumbs <img width="606" alt="image" src="https://user-"
The trigger is that registering a file system causes a label service change event which causes breadcrumbs to re-render. Tho, we can likely optimise this
Change:
const elem = this.actionsList.children[i]; if (DOM.isAncestor(DOM.getActiveElement(), elem)) { this.focusedItem = i; <ins> this.viewItems[this.focusedItem]?.showHover?.(); </ins> break; } }

Discussion:
This ask is from the Copilot team in response to feedback they've received. When something is represented via only an icon, and is focused via keyboard, we should automatically focus the tooltip.
cc
related
we would also want to do this for all toolbars <img width="202" alt="Screenshot 2023-11-01 at 10 12 16 AM" src=""
Just out of curiosity, what does "focus the tooltip mean"? Does it mean "make the tooltip visible"? (sorry- the language is a bit confusing. tooltips are not actually focusable, right?)
yes I think meant to show the hover, not focus it as that would break left/right navigation.
Yep, it just shows the hover, doesn't focus it.
Change:
import * as nls from 'vs/nls'; import * as objects from 'vs/base/common/objects'; import * as DOM from 'vs/base/browser/dom'; <ins> import * as path from 'path'; </ins> import URI from 'vs/base/common/uri'; import { once } from 'vs/base/common/functional'; import * as paths from 'vs/base/common/paths';

Discussion:
Only one nitbit, now when we display the path in a multi folder setup we do not start with a and when we display the path in a single folder setup we show the relative folder with a at the start. I think that is wrong and the path should never show a since it is not absolute
Change:
import { IndexTreeModel, IIndexTreeModelOptions } from 'vs/base/browser/ui/tree/indexTreeModel'; import { Event } from 'vs/base/common/event'; import { ITreeModel, ITreeNode, ITreeElement, ITreeSorter, ICollapseStateChangeEvent, ITreeModelSpliceEvent } from 'vs/base/browser/ui/tree/tree'; <ins> import { IIdentityProvider } from 'vs/base/browser/ui/list/list'; </ins> export interface IObjectTreeModelOptions<T, TFilterData> extends IIndexTreeModelOptions<T, TFilterData> { readonly sorter?: ITreeSorter<T>; <ins> readonly identityProvider?: IIdentityProvider<T>; </ins> } export class ObjectTreeModel<T extends NonNullable<any>, TFilterData extends NonNullable<any> = void> implements ITreeModel<T | null, TFilterData, T | null> {

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
Change:
} if (!isPrimary || alwaysFillSecondary) { <del> const to = Array.isArray<IAction>(target) ? target : target.secondary; </del> <ins> const to = Array.isArray(target) ? target : target.secondary; </ins> if (to.length > 0) { to.push(new Separator());

Discussion:
What is the reasoning behind not allowing via the Monaco standalone editor checks? It seems to be valid ES6 when I look at where it is defined:
idk - requires at least edge 14, unsure what our edge minimum version is:
Looking at the compat tables, I think it should be safe to use it. I guess it must have been a left-over from the IE era. I don't remember adding any rule like this, so I don't know where to begin looking to remove it. Leaving it to you .
I opened to do this and it has the advantage that we can get rid of another file in our folder () which actually even seems to have the wrong signature compared to TS. According to , Edge 13 has very low usages and Edge 14 is out since 2016: !
Unsure how and are connected. Or is this two clean-ups in one? I have the latter because for the longest time there was a TS bug which would remove type info from arrays after checking E.g If that's now fixed, I am very happy with removing
ah good to know, I just checked both in our code and the playground and I see that this no longer seems to be the case: ! I will go ahead and merge my PR then.
it