jiebi/CodeConvo huggingface dataset:
Change:
import { Snippet, SnippetSource } from 'vs/workbench/contrib/snippets/browser/snippetsFile'; import { LanguageConfigurationRegistry } from 'vs/editor/common/modes/languageConfigurationRegistry'; import { CompletionContext, CompletionTriggerKind } from 'vs/editor/common/modes'; <ins> import { DisposableStore } from 'vs/base/common/lifecycle'; </ins> class SimpleSnippetService implements ISnippetsService { declare readonly _serviceBrand: undefined;

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. --Version: 1.49.0-insider Commit: Date: 2020-08-17T17:11:16.078Z (1 day ago) Electron: 9.2.0 Chrome: 83.0.4103.122 12.14.1 V8: 8.3.110.13-electron.0 OS: Darwin x64 19.6.0 Steps to Reproduce: Add the following python snippet: or PowerShell snippet: : which will cause auto-closing pair... (at this point you have where is the cursor) add a or and hit TAB or ENTER on the intellisense item NOTE THE TRAILING . Snippets and auto-closing pairs should play nice together so that the whole experience generates valid code. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Here's a javascript example for array destructuring: which gets you: when you type:
better example! A javascript example for : which gets you: when you type:
for verification, this: should get you: on insert mode replace (default is SHIFT + ENTER)
I'll note that it works fine in non-json files, but is reversed in a json file (as are the insert/replace hints in the suggestion box). W10
that seems like a separate issue not related to this fix. Can you open a new issue?
Yes, I'll open another issue.
Change:
"config.decorations.enabled": "Controls whether Git contributes colors and badges to the Explorer and the Open Editors view.", "config.enableStatusBarSync": "Controls whether the Git Sync command appears in the status bar.", "config.followTagsWhenSync": "Push all annotated tags when running the sync command.", <ins> "config.replaceTagsWhenPull": "Automatically replace the local tags with the remote tags in case of a conflict when running the pull command.", </ins> "config.promptToSaveFilesBeforeStash": "Controls whether Git should check for unsaved files before stashing changes.", "config.promptToSaveFilesBeforeStash.always": "Check for any unsaved files.", "config.promptToSaveFilesBeforeStash.staged": "Check only for unsaved staged files.",

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:
this._itemsConstructed = 0; this._itemsFromCache = 0; <del> let result = this.parseList(SmallImmutableSet.getEmpty()); </del> <ins> let result = this.parseList(SmallImmutableSet.getEmpty(), 0); </ins> if (!result) { result = ListAstNode.getEmpty(); }

Discussion:
copy the contents of paste into a untitled editor it takes seconds for me before the content appears, sometimes not at all !
Oh, there is this in the console:
Change:
}, { "type": "string", <del> "pattern": "^([a-z0-9-]+):(d{1,5})$" </del> <ins> "pattern": "^([a-z0-9_-]+):(d{1,5})$" </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.81.1 OS Version: Windows 10 Pro (.2965) Steps to Reproduce: to add a port forward for example to "webservice1:80" (either via the view or command) UI gives the error "Forwarded port should be a number or a host:port" ! Using dashes would work. ! But that would not be so practical. Especially when working with dev containers, tunneling to other containers mostly happens via their name, which a lot of times includes underscores.
Change:
"editorLineNumber.activeForeground": "#ffffffc5", "editorLineNumber.foreground": "#6e7681", "editorOverviewRuler.border": "#010409", <del> "editorWhitespace.foreground": "#484f58", </del> "editorWidget.background": "#1f1f1f", "errorForeground": "#f85149", "focusBorder": "#2488d8",

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.75.0-insider OS Version: Linux Hello, Thanks for the new color themes. I have few observations related to whitespace character visibility. Can you please take a look into these? (default) option, the whitespace characters are hard to see. Default Dark+ Experimental (v2): ! Default Dark+: ! the whitespace foreground could use some alpha Default Dark+ Experimental (v2): ! Default Dark+ Experimental (v2): with some alpha ! Default Dark+: ! Thanks
Change:
vscode-languageserver-types "^3.13.0" vscode-nls "^4.0.0" <del> vscode-html-languageservice@^2.1.11-next.3: version "2.1.11-next.3" resolved "https://registry.yarnpkg.com/vscode-html-languageservice/-/vscode-html-languageservice-2.1.11-next.3.tgz#f8eaee042c161f47fb71850c558428d0d91c881f" integrity sha512-621+f1nbRvMgLyvW1Aa9shZ9r9qBIXMi4fF8o0voooHjIggrIbstUpYmaQIFRNill3b9HCNdluTZnAQlQGU6Ew== </del> <ins> vscode-html-languageservice@^2.1.11-next.4: version "2.1.11-next.4" resolved "https://registry.yarnpkg.com/vscode-html-languageservice/-/vscode-html-languageservice-2.1.11-next.4.tgz#bcfe68ca17300d7f845889be3cb947af95dab409" integrity sha512-dQOcdqLhMZuAWhSoe/AqqvVo2klkWpCHwp14dWvgrAfUyKM7l0e0kk9lbf8kt1Kn2J9ukDTySIcOkbHaVSwcHA== </ins> dependencies: vscode-languageserver-types "^3.13.0" vscode-nls "^4.0.0"

Discussion:
Semantic selections: LSP: works CSS/SCSS/LESS: doesn't work, but it works in Atom. Probably need to update our dependencies. The plan now is to use emmet's "balance" commands. The challenge is that HTML/CSS language service need to include emmet. Alternatively, we can implement these commands ourselves.
Please review the animated gifs in the original thread: Seems to me the emmet functionality as it stands is wholly inadequate.
This will be available in tomorrow's insiders: !
is this suppose to work in Javascript? It's not nearly as functional as Webstorm. Also fails dramatically with HTML in .Vue files. Oh well.
Vue — it'll be available once we update the dependencies. JavaScript — we'll need to wait for TypeScript to add the semantic selection. I don't have any estimate.
Change:
'libc.so.6(GLIBC_2.8)', 'libc.so.6(GLIBC_2.9)', 'libcairo.so.2', <del> 'libcups.so.2', </del> 'libcurl.so.4()(64bit)', 'libdbus-1.so.3', 'libdl.so.2',

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.73.1 OS Version: Gentoo Linux Starting with 1.72, vscode has a hard dependency on a printing library, otherwise it refuses to even start. CUPS is quite a heavy dependency and not all Linux installations have it. This is a bug for two reasons: does not even support printing () then, such heavy libraries shall be only loaded on demand.
So, can you arrange with electron to not include the dependency on a heavy printing library? Nobody has printers these days.
Do you know which vscode release is going to start using Electron 22?
Verified with
Change:
overflow: hidden; text-overflow: ellipsis; font-family: var(--monaco-monospace-font); <ins> white-space: pre; </ins> } .monaco-workbench.mac .debug-viewlet .monaco-list-row .expression,

Discussion:
Issue Type: <bBug</bHi. I am assigning trade.occId = occId; i.e. to a property (in this case it contains 4 spaces. In the JavaScript hover view however, the property on 'trade' reads (only one space) [btw, I copied both these values right out of the IDE view]. I've just been chasing ghosts for some time because of this discrepancy and not expecting the IDE altering assigned values when viewing objects. Update ---Alright, sorry. I am not sure how to submit the first value on GitHub with the 4 spaces between GS and 1 preserved, even when using 'code' quotes (same as the VSC issue...). So the first value is "GD....190517P00155000" when replacing spaces with dots... Thanks for VS Code otherwise :-) VS Code version: Code 1.33.1 (, 2019-04-11T08:27:14.102Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (4)</summaryExtensionVersion ------ vscode-scss0.6.2 debugger-for-chrome4.11.3 vscode-scss-formatter1.4.1 vscodeintellicode1.1.5 </details<!-- generated by issue reporter --
Can you please provide a screenshot of what you see? Also try disabling all extensions. I am not sure if such an hover is provided by out of the box typescript/javascript extension.
Hi. Please see below. I disabled all extensions besides Debugger for Chrome, which I need to set a break-point to be able to inspect values. The issue is in most obvious in the field 'occId', which in fact has 4 spaces after 'GD' and not just one as displayed. Thanks for following up. [image: ] !
Ah I see.. its an hover while debugging.
You did not attach an image. So please attach an image and some reproducable steps so we can investigate more. Thanks
It did, (please check below the quote). Anyway, your question made me come up with a better/simpler example that should make things clear. Here you go: ! Btw, Gruetzi to all you guys in Zuerich.

I'm originally from Basel :)
Thanks for the image. Cheers back to Basel :)
VSCode insiders will have the fix for this on monday. Try it out and let us know if it is ok for you. Though I verified and the fix from looks good
Thanks for the work and update. Unfortunately I can't switch from VSCode stable, so I'll take your word for it until this hits release :-)
Change:
"git": { "name": "seti-ui", "repositoryUrl": "https://github.com/jesseweed/seti-ui", <del> "commitHash": "fd20793e5a75b350eab8d489165fb9b420df3f62" </del> <ins> "commitHash": "8eec7f2e37cd8fd91a98c61d129468bb49735a94" </ins> } }, "version": "0.1.0"

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. --Can the default file icon theme be updated in VS Code (seems just need to follow the to run the script) files should by now have the Maven (mvnw) icon but are still showing regular XML icon.
Verify that the files now have the Maven (mvnw) icon
Change:
bubble: true, tooltip: markers.length === 1 ? localize('tooltip.1', "1 problem in this file") : localize('tooltip.N', "{0} problems in this file", markers.length), letter: markers.length < 10 ? markers.length.toString() : '+9', <del> color: first.severity === MarkerSeverity.Error ? editorErrorForeground : editorWarningForeground, </del> <ins> color: first.severity === MarkerSeverity.Error ? listErrorForeground : listWarningForeground, </ins> }; } }

Discussion:
The new error highlight in the explorer window is great, but for some reason the colours are all black for me. I've tried different themes, but it doesn't make any difference: !
Ah - I've figured it out. It's using the colour from 'editorError.foreground' from 'workbench.colorCustomizations'. I can see the logic in doing this, but I have the foreground colour set to black to hide the squigglies and use the border colour instead to show a double underline, which makes the stand out more. The theme has different colours for the editor area and the explorer area, so is it sensible to use the same colours? Maybe there should be a separate setting?
It's especially bad when you have transparent editor warnings and errors.
didn't you tweak the colors in the last endgame? is this still the same symbolic color?
This is what I've done:
Alright
I'd like to take this as my first issue. Can you point me where I can start?
Sure - here is the code that adds the decorations (using the squiggle colors): You can use the -function to define new colors, like here: I'd define two colors, for errors and for warnings.
Change:
this._input = ''; } <ins> private _sendText(): void { this._terminalService.activeInstance?.sendText(this._input, false); alert(localize('terminalVoiceTextInserted', '{0} inserted', this._input)); } </ins> private _updateInput(e: ISpeechToTextEvent): void { if (e.text) { let input = e.text.replaceAll(/[.,?;!]/g, '');

Discussion:
Sighted users see preview text as a voice recording occurs and they see the resultant output, which could be drastically different from what they might expect. To make this clear for SR users, after the recording has stopped, we should alert with the content that was inserted in at least the terminal. Unclear if this would also be desirable to do in the chat input boxes
Do you move over to using braille when using the speech functionality Otherwise, doesn't the mic pick up on what the screen reader is saying?

It seems that the mic icon requires at least one line above the prompt to show: ! It does not appear for me in the above case.
Thanks for the issue. Should be an easy fix and in this case the mic will have to go on the cursor line
Change:
if (!this.domNodes) { return; } const fontInfo = this.editor.getOption(EditorOption.fontInfo); <del> this.domNodes.element.style.fontSize = `${fontInfo.fontSize}px`; this.domNodes.element.style.lineHeight = `${fontInfo.lineHeight / fontInfo.fontSize}`; </del> <ins> const element = this.domNodes.element; element.style.fontSize = `${fontInfo.fontSize}px`; element.style.lineHeight = `${fontInfo.lineHeight / fontInfo.fontSize}`; element.style.setProperty('--vscode-parameterHintsWidget-editorFontFamily', fontInfo.fontFamily); element.style.setProperty('--vscode-parameterHintsWidget-editorFontFamilyDefault', EDITOR_FONT_DEFAULTS.fontFamily); </ins> }; updateFont();

Discussion:
I got the default font rendered in the parameter hint widget. It looks alien compared to the rest of the hover widget UI. Steps: chat sample line 21 type the following: will see the parameter hints with a weird font (default system?) ! fyi
I haven't been able to reproduce this Are you still seeing this issue? Does it only show up with specific functions?
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
Yes, I still see this. I see this for all parameter hovers. I have nailed this down to be due to this setting I got a new mac, so most likely I do not have Fira Code installed. So the Editor seems to fall back nicely to a good default font, and Parameter Hints falls back to a non coding font. Which looks like the gist of this bug. I will reopen this so you can chime in. Thanks
Change:
*--------------------------------------------------------------------------------------------*/ import { ContextSubMenu } from 'vs/base/browser/contextmenu'; <del> import { getDomNodePagePosition } from 'vs/base/browser/dom'; </del> <ins> import { EventHelper, getDomNodePagePosition } from 'vs/base/browser/dom'; </ins> import { IAction } from 'vs/base/common/actions'; import { Delayer } from 'vs/base/common/async'; import { Emitter, Event } from 'vs/base/common/event';

Discussion:
<!-- 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: --From but he wasn't willing to open his issue. Left click is broken but right click works. It's introduced in 1.34.0. I can reproduce it by upgrading from 1.33.1 to 1.34.0. Is it by designed that only right click works? <!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.34.0 and 1.35.0 OS Version: Windows 10 1903 and Windows 7 and Debian 10 Steps to Reproduce: The same as <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <details</details
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.455 --<!-- potentialduplicatescomment --
Now I can reproduce it. You can disable custom menus with to work around it if that helps
Yes, takes effects.
I pushed a PR to fix this but in a duplicated issue (just found this one sorry about the duplicate)
Tried the latest insider version, works.

Steps to Reproduce: settings JSON editor click on any next to a setting context menu shown If I use right click, context menu does show. Related to
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.624 --- <!-- score: 0.498 --- <!-- score: 0.462 --- <!-- score: 0.447 --<!-- potentialduplicatescomment --
My bad. This is a duplicate of
/duplicate
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 existing issues . See also our guidelines. Happy Coding!
Change:
this.jumpToCursorSupported.set(session ? !!session.capabilities.supportsGotoTargetsRequest : false); this.setVariableSupported.set(session ? !!session.capabilities.supportsSetVariable : false); this.terminateDebuggeeSuported.set(session ? !!session.capabilities.supportTerminateDebuggee : false); <del> this.disassembleRequestSupported.set(!!stackFrame?.instructionPointerReference && !!session?.capabilities.supportsDisassembleRequest); </del> <ins> this.disassembleRequestSupported.set(!!session?.capabilities.supportsDisassembleRequest); this.focusedStackFrameHasInstructionPointerReference.set(!!stackFrame?.instructionPointerReference); </ins> const attach = !!session && isSessionAttach(session); this.focusedSessionIsAttach.set(attach); });

Discussion:
Testing As already pointed out The "Open Disassembly View" command is now only visible when the active stackframe has a instructionPointerReference property. This makes it hard to discover. I suggest to have the context menu's "Open Disassembly View" command always visible if a debug adapter has the supportsDisassembleRequest capability. But the command should only be enabled if the active stackframe has a instructionPointerReference property. That results in a more stable user experience. Apart from that we should have the Open Disassembly View command in the command palette.
That's a fair suggestion. However, we are not sure how to disable a command...
commands have clauses and . clause determines if the command is present at all and if it is disabled. So please use the when registering the editor command for disablement.
Also we should consider to introduce a call stack context menu action for the Open Disassembly View.
will fix this.
Change:
import { TerminalBaseLinkProvider } from 'vs/workbench/contrib/terminal/browser/links/terminalBaseLinkProvider'; import { normalize } from 'vs/base/common/path'; import { convertLinkRangeToBuffer, getXtermLineContent } from 'vs/workbench/contrib/terminal/browser/links/terminalLinkHelpers'; <ins> import { isWindows } from 'vs/base/common/platform'; </ins> const MAX_LENGTH = 2000;

Discussion:
Issue Type: <bBug</b! by ctrl+leftclick to open a file in Terminal, a path like xx/xxx/xx/xx.c could be open and xx.c:13:3 could be open because recently opened, and auto jump to line/col but a path with line/col number like xx/xxx/xx/xx.c:13:3 can't be open VS Code version: Code 1.56.2 (, 2021-05-12T17:13:13.157Z) OS version: WindowsNT x64 10.0. Remote OS version: Linux x64 5.4.72-microsoft-standard-WSL2 <details<summarySystem Info</summary </details<details<summaryExtensions (7)</summaryExtensionVersion ------ remote-ssh0.65.4 remote-ssh-edit0.65.6 remote-wsl0.56.4 vim1.20.3 githistory0.6.16 cpptools1.4.0 hexeditor1.6.0 </details<!-- generated by issue reporter --
Links of that form work, your issue is because you have the folder opened and files are only resolved relative to the root folder. So it would work fine if you opened the parent folder of . I guess we could special case this to remove the first path segment if it matches the opened folder (ie. the initial cwd of the terminal).
Code pointer:
Thanks for your reply, Its very helpful for me to understand that, I add parent folder of codec to workspace, and it works as expect, much appreciated.
I suppose I can work on this. From what I understand, all I have to do is check if the prefix of the search query matches the root folder directory. If it does, we erase that first part and resume the code as usual, right?
pretty much yep, make sure it's a folder (link contains /, or  on windows) and a test would be good too which should be fairly easy to write in the existing test file.
I checked the code pointer that you sent above, but it doesn't seem like it points to the right place (this is my first time navigating the VS Code repository so there's a good chance that I'm wrong). I did some research and ended up in "", specifically .

I one line (just to make sure I'm in the right place) that logs a message to the console whenever the user enters a new character in Quick Open, and it worked. Isn't that where I should be working? How is the terminal related to this issue?
we wouldn't want to change the quick access code but what the terminal sends to it: