jiebi/CodeConvo huggingface dataset:
Change:
assertMatches('.', 'log', 'log', anyScore); }); <ins> test('anyScore should not require a strong first match', function () { assertMatches('bar', 'foobAr', 'foo^b^A^r', anyScore); assertMatches('bar', 'foobar', 'foo^b^a^r', anyScore); }); </ins> test('configurable full match boost', function () { const prefix = 'create'; const a = 'createModelServices';

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: (2022-12-06) OS Version: Steps to Reproduce: that returns an item with and (filtertext doesn't matter, as long as it matches whatever is typed) should be , but you get (the o should be highlighted and is not) some examples from typescript (typing in ): <img width="289" alt="Screenshot 2022-12-06 at 10 41 36 PM" src="https://user-"<img width="351" alt="Screenshot 2022-12-06 at 10 41 03 PM" src="https://user-"
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.73.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
<!-- 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!
Change:
logLevel: this._logService.getLevel(), logsLocation: this._extensionHostLogsLocation, logFile: this._extensionHostLogFile, <del> autoStart: true, </del> <ins> autoStart: initData.autoStart, </ins> remote: { authority: this._environmentService.remoteAuthority, connectionData: null,

Discussion:
When running a web worker extension on vscode desktop, the error appears. To reproduce, you can use the following extension: : :
Change:
if (this._isDisposed) { return; } <del> const trusted = await this._trust(); if (!trusted) { </del> <ins> const activeWorkspaceRootUri = this._historyService.getLastActiveWorkspaceRoot(Schemas.file); if (activeWorkspaceRootUri) { const trusted = await this._trust(); if (!trusted) { this._onProcessExit({ message: nls.localize('workspaceNotTrustedCreateTerminal', "Cannot launch a terminal process in an untrusted workspace") }); } } else if (this._userHome && this._cwd !== this._userHome) { // ensure that the process is launched in userHome for an empty workspace this._shellLaunchConfig.cwd = this._userHome; } else if (!this._userHome) { </ins> this._onProcessExit({ message: nls.localize('workspaceNotTrustedCreateTerminal', "Cannot launch a terminal process in an untrusted workspace") }); }

Discussion:
It's an edge case but worthwhile considering 1) Ensure that all new windows are in restricted mode by default 2) Open a new empty window (no open files at all, no open folder) 3) Use <kbdCmd</kbd+<kbd`</kbd-prompt for trusting the workspace, but there is nothing there to be trusted
In this case, it definitely gets in the way that we ask about trust, and also doesn't make too much to limit access to the terminal. However, what considerations should be in place for when someone decides to bring in untrusted content into the workspace after the terminal is opened? Does this matter for empty workspaces
it's only useful for the terminal if the folder is of a potentially foreign origin. I could special case this since it's going to open in the home directory anyway, but should it even be possible to have an empty window in restricted mode? Might need to handle this special case in multiple places if it's not handled by the trust request service?
we have settings to configure the empty window experience... this allows empty windows to bring in untrusted content easily without prompting.
Ok, let's allow opening the terminal if the active workspace root is undefined then as it's safe in that case.
Change:
height: number; } <ins> interface IChatMarkdownRenderResult extends IMarkdownRenderResult { codeBlockCount: number; } </ins> const forceVerboseLayoutTracing = false; export interface IChatRendererDelegate {

Discussion:
Steps to Reproduce: multiple markdown strings with code blocks interleaved with commands/warnings. (see sample chat extension ) progressive streaming of chat content. The markdown code blocks at the beginning of the stream are replaced with the last streamed code block content. See below gif: !
Change:
const keybinding = this._keybindingService.lookupKeybinding(actionOptions.commandId); const keybindingLabel = keybinding ? keybinding.getLabel() : null; this._hasContent = true; <del> return this._register(HoverAction.render(this.actionsElement, actionOptions, keybindingLabel)); </del> <ins> const action = this._register(HoverAction.render(this.actionsElement, actionOptions, keybindingLabel)); this.actions.push(action); return action; </ins> } public append(element: HTMLElement): HTMLElement {

Discussion:
Testing Once again, I'm not sure what the norms are here, but would it be useful to have the actions in the status bar show in the accessibly view? <img width="607" alt="image" src=""
Hi yes that would make sense. Good point!
Change:
public readonly cursorColor: string | null; public readonly themeType: 'light' | 'dark' | 'hcLight' | 'hcDark'; <del> public readonly backgroundColor: string | null; </del> <ins> public readonly backgroundColor: Color | null; </ins> public readonly top: number; public readonly right: number;

Discussion:
Ruler background is set to black with 50% transparency, but vscode shows solid black! ! ! Description for editorOverviewRuler.background also says: , but vscode use this background if minimap is enabled or not!
The color description is out of date. We changed the behavior of via so we now always respect . However, it never supported transparency, so we could add support for that.
Change:
import { TerminalLinkQuickpick } from 'vs/workbench/contrib/terminal/browser/links/terminalLinkQuickpick'; import { IRequestAddInstanceToGroupEvent, ITerminalQuickFixOptions, ITerminalExternalLinkProvider, ITerminalInstance, TerminalDataTransfers } from 'vs/workbench/contrib/terminal/browser/terminal'; import { TerminalLaunchHelpAction } from 'vs/workbench/contrib/terminal/browser/terminalActions'; <del> import { gitSimilarCommand, gitCreatePr, gitPushSetUpstream, freePort } from 'vs/workbench/contrib/terminal/browser/terminalQuickFixBuiltinActions'; </del> <ins> import { gitSimilarCommand, gitCreatePr, gitPushSetUpstream, freePort, gitTwoDashes } from 'vs/workbench/contrib/terminal/browser/terminalQuickFixBuiltinActions'; </ins> import { TerminalConfigHelper } from 'vs/workbench/contrib/terminal/browser/terminalConfigHelper'; import { TerminalEditorInput } from 'vs/workbench/contrib/terminal/browser/terminalEditorInput'; import { TerminalFindWidget } from 'vs/workbench/contrib/terminal/browser/terminalFindWidget';

Discussion:
With we're getting some initial terminal quick fixes. We have a bunch more ideas, let's use this issue to track adding more at a later date when we have more information on how the feature is received.
Also want to consider the setting to disable one or more of these
The open URL one (the only one I’ve seen so far) was a really pleasant surprise and I immediately adopted it into my workflow for opening a GitHub PR after pushing a new branch. Another one I would love to see is opening files with merge conflicts: <img width="615" alt="image" src="https://user-"
great idea!
I think this can be closed since we have individual issues tracking ideas
Change:
"elliptic": "^6.5.3", "nwmatcher": "^1.4.4" } <del> } </del> <ins> } </ins>  No newline at end of file

Discussion:
OS Version: Ubuntu 22.04 LTS + Xfce 4.16 When create desktop icon, it shows generic icon instead of VSCode icon. ! When I tried to dig deeper, I observed that, the icon file is saved with name inside directory. The issue is occurring because of the file name. If I simply rename the file name to , then it works. So, adding multiple extension causes the issue. !
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.70.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
This works in most desktop managers, we'd want to verify it still works in ubuntu + gnome
Seems an easily fixable bug which hits xfce4 specifically: it can't handle 's in path.
<!-- 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!
Change:
return clb(startPort); }); <del> client.connect(startPort); </del> <ins> client.connect(startPort, '127.0.0.1'); </ins> } function dispose(socket: net.Socket): void {

Discussion:
VSCode Version: 1.6.0 OS Version: windows7 Steps to Reproduce: Create a vscode extension project. Pull off the cable to keep offine. Launch Extension (F5) I cant set breakpoint in my source file. And I find some warn information in Extension Development Host Window : I change the code in Its works. fyi
Sounds like a potential PR fyi
Yeah, PR welcome.
can you elaborate why your change is fixing this? If I look at the docs of I can see that host per default is .
can`t be resolved when being offline. And fyi
thanks
Change:
); } <ins> const wordSeparators = new Set<number>(); '`~!@#$%^&*()-=+[{]}|;:'",.<>/?' .split('') .forEach(s => wordSeparators.add(s.charCodeAt(0))); function isWordSeparator(code: number): boolean { return wordSeparators.has(code); } </ins> function isAlphanumeric(code: number): boolean { return isLower(code) || isUpper(code) || isNumber(code); }

Discussion:
VSCode Version: Code - Insiders 1.13.0-insider (, 2017-05-30T05:12:15.312Z) OS Version: Linux x64 4.10.0-21-generic Extensions: ; fyi ! !
The command palette doesn't use the new fuzzyScore-logic. It maybe should tho
Welcome to
I've noticed that it does in fact match characters inside parentheses, but won't match them if they're right next to the parentheses. In my example GIF below you can see the following: to match completely, due to the being next to the parentheses if I actually type the parentheses if I type words inside the parentheses but aren't next to them ! EDIT (2018-11-12): It matches if all of the the characters in inside the parentheses: ! However it won't match if i search two different parts of the text inside: !
Thanks you
Change:
assertRangeEqual(link.range, new vscode.Range(0, 6, 0, 25)); }); <ins> // #35245 test('Should handle links with escaped characters in name', () => { const links = getLinksForFile('a [b]](./file)'); assert.strictEqual(links.length, 1); const [link] = links; assertRangeEqual(link.range, new vscode.Range(0, 8, 0, 14)); }); </ins> test('Should handle links with balanced parens', () => { {

Discussion:
From In a markdown file: Does not detect as a link
Did you mean auto]save?
Added a merge request with some tweaks to the regex that is used to detect links. With the fix it should now correctly detect links with "]" in their names.
Change:
connectTo: new ManagedRemoteConnection(socketFactoryId), connectionToken: result.connectionToken }; <ins> } else { authority = { authority: remoteAuthority, connectTo: new WebSocketRemoteConnection(result.host, result.port), connectionToken: result.connectionToken }; </ins> } return {

Discussion:
Version: 1.79.0-insider Commit: Date: 2023-05-16T05:23:57.470Z Electron: 22.5.2 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Linux x64 5.14.0-1048-oem open a wsl or a dev containers window fails with a notification: Could not fetch remote environment. this.c.makeConnection is not a function
I see the same error, yesterdays version worked fine.
and it is fixed: it seems they rolled back to yesterdays version Version: 1.79.0-insider (user setup) Commit: Date: 2023-05-15T05:20:50.327Z Electron: 22.5.2 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.

ERR this.factory.makeConnection is not a function: TypeError: this.factory.makeConnection is not a function at ExtHostManagedSockets.$openRemoteSocket (c:Usersmartinaeworkspacesvscodeoutvsworkbenchapicommon) at RPCProtocol.doInvokeHandler (c:Usersmartinaeworkspacesvscodeoutvsworkbenchservicesextensionscommon) at RPCProtocol.invokeHandler (c:Usersmartinaeworkspacesvscodeoutvsworkbenchservicesextensionscommon) at RPCProtocol.receiveRequest (c:Usersmartinaeworkspacesvscodeoutvsworkbenchservicesextensionscommon) at RPCProtocol.receiveOneMessage (c:Usersmartinaeworkspacesvscodeoutvsworkbenchservicesextensionscommon) at c:Usersmartinaeworkspacesvscodeoutvsworkbenchservicesextensionscommon at (c:Usersmartinaeworkspacesvscodeoutvsbasecommon) at PrivateEventDeliveryQueue.deliver (c:Usersmartinaeworkspacesvscodeoutvsbasecommon) at (c:Usersmartinaeworkspacesvscodeoutvsbasecommon) at (c:Usersmartinaeworkspacesvscodeoutvsbasepartsipccommon) at c:Usersmartinaeworkspacesvscodeoutvsworkbenchapinode at (c:Usersmartinaeworkspacesvscodeoutvsbasecommon) at PrivateEventDeliveryQueue.deliver (c:Usersmartinaeworkspacesvscodeoutvsbasecommon) at (c:Usersmartinaeworkspacesvscodeoutvsbasecommon) at (c:Usersmartinaeworkspacesvscodeoutvsbasepartsipccommon) at MessagePortMain.<anonymous(c:Usersmartinaeworkspacesvscodeoutvsworkbenchapinode) at (node:events:513:28) at (node:electron/js2c/utilityinit:2:367)
for me now the forwarded ports on remote hosts are broken:
Change:
async function copyVscodeDevLink(gitAPI: GitAPI, useSelection: boolean, context: LinkContext, includeRange = true) { try { <del> const permalink = getLink(gitAPI, useSelection, getVscodeDevHost(), 'headlink', context, includeRange); </del> <ins> const permalink = await getLink(gitAPI, useSelection, getVscodeDevHost(), 'headlink', context, includeRange); </ins> if (permalink) { return vscode.env.clipboard.writeText(permalink); } } catch (err) { <del> vscode.window.showErrorMessage(err.message); </del> <ins> if (!(err instanceof vscode.CancellationError)) { vscode.window.showErrorMessage(err.message); } </ins> } } async function openVscodeDevLink(gitAPI: GitAPI): Promise<vscode.Uri | undefined> { try { <del> const headlink = getLink(gitAPI, true, getVscodeDevHost(), 'headlink'); </del> <ins> const headlink = await getLink(gitAPI, true, getVscodeDevHost(), 'headlink'); </ins> return headlink ? vscode.Uri.parse(headlink) : undefined; } catch (err) { <del> vscode.window.showErrorMessage(err.message); </del> <ins> if (!(err instanceof vscode.CancellationError)) { vscode.window.showErrorMessage(err.message); } </ins> return undefined; } }

Discussion:
Testing One can copy links to & github & azure repos even though I just created the file and copying such a link will result in empty or 404 on GH. Seeing links to just created file : <img width="451" alt="image" src="https://user-"
No progress on this one yet, but would you expect the actions to be hidden, or would you want to be prompted to commit the file to the remote when the command is invoked?
I think users could be confused if the actions wouldn't appear (eg they might've forgotten the file isn't pushed), so the latter sounds better. But I wonder whether checking whether the file is available on remote would be slow
Change:
].forEach(testFixRegexNewline); }); <ins> test('fixNewline', () => { function testFixNewline([inputReg, testStr, shouldMatch = true]): void { const fixed = fixNewline(inputReg); const reg = new RegExp(fixed); assert.equal(reg.test(testStr), shouldMatch, `${inputReg} => ${reg}, ${testStr}, ${shouldMatch}`); } [ ['foo', 'foo'], ['foon', 'foorn'], ['foon', 'foon'], ['foonabc', 'foornabc'], ['foonabc', 'foonabc'], ['foorn', 'foorn'], ['foonbarc', 'foobar', false], ['foobar', 'foonbar', false], ].forEach(testFixNewline); }); </ins> suite('RipgrepParser', () => { const TEST_FOLDER = URI.file('/foo/bar');

Discussion:
Open folder containing CRLF files (typically on windows) Copy multiple lines of text, paste into search viewlet Close that file Do multiline search The file is not found cc Candidate because the feature is essentially completely broken on windows.
Change:
return this.onWorkspaceFolderConfigurationChanged(folder); } <del> private async loadConfiguration(applicationConfigurationModel: ConfigurationModel, userConfigurationModel: ConfigurationModel, remoteUserConfigurationModel: ConfigurationModel): Promise<void> { </del> <ins> private async loadConfiguration(applicationConfigurationModel: ConfigurationModel, userConfigurationModel: ConfigurationModel, remoteUserConfigurationModel: ConfigurationModel, trigger: boolean): Promise<void> { </ins> // reset caches this.cachedFolderConfigs = new ResourceMap<FolderConfiguration>();

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?: not applicable <!-- 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.79.0-insider OS Version: Windows 11 x64 Steps to Reproduce: an extension that implements a FileSystemProvider and serves a file containing a setting. a workspace that uses this FSP. that the setting has no effect until the workspace is reloaded. I will prepare a branch of fsprovider-sample to demonstrate the issue.
Repro steps: project () and VSIX (). an empty profile and install the VSIX into it. no folder or workspace open, run . Explorer find and open that though this specifies a font size of 24 it is displayed in the default font size. and observe that the font size is now correct. !
/assign I will submit a PR to fix this.
<!-- 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!
/verified
Change:
/* Expressions */ <ins> .monaco-workbench .debug-pane .monaco-list-row .expression, .monaco-workbench .debug-hover-widget .monaco-list-row .expression { display: flex; } </ins> .monaco-workbench .debug-pane .monaco-list-row .expression, .monaco-workbench .debug-hover-widget .monaco-list-row .expression { font-size: 13px;

Discussion:
The new lazy variable evaluation button line-height or dimensions appear to be too large. The button creates frequent gaps in-between node items and creates unsightly misalignment. This is not a settings font issue because the issue appeared with the change to the lazy evaluation button in version 1.67.1. This new button does not improve JavaScript debugging. The ellipsis button did not do this. Version: 1.67.1 (user setup) Commit: Date: 2022-05-06T12:37:03.389Z Electron: 17.4.1 Chromium: 98.0.4758.141 16.13.0 V8: 9.8.177.13-electron.0 OS: Windows_NT x64 10.0. Does this issue occur when all extensions are disabled?: Yes Steps to Reproduce: JavaScript object to console window the gaps between expandable nodes any collapsed variable to evaluate. The item will jump and become misaligned. !
Hey is there a reason that the variables view tree is 22px tall while the hover variables rows are 18px tall? I just noticed this.
I think the idea is to make the debugHover tree smaller, while the other trees in views should be larger. The problem here seems to be that the debugHover reuses the and by that the height of the hover items is 22. So the height should be configurable, and debugHover should be able to say to the variableDelagate that the height is 18 in this case.
The variables tree in the debug hover is correctly sized. It's just a CSS issue on that one button. I guess it's intentional, and that's fine, so I'll just fix the css.
okey. Thanks for fixing
This broke the alignment of the lazy button in the debug console because the text wraps there
Change:
private _addNamedHeaders(md: MarkdownIt): void { const original = md.renderer.rules.heading_open; md.renderer.rules.heading_open = (tokens: Token[], idx: number, options, env, self) => { <del> const title = tokens[idx + 1].children!.reduce<string>((acc, t) => acc + t.content, ''); </del> <ins> const title = this._tokenToPlainText(tokens[idx + 1]); </ins> let slug = this.slugifier.fromHeading(title); if (this._slugCount.has(slug.value)) {

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.91.0.0 OS Version: Windows 10 build .4598 Steps to Reproduce: a header with a raw HTML element HTML is included in markdown header anchors ( is included!)
Note: links without the HTML tag work in editor mode only
This is for path completions, right? Seems to work fine for me ! Does this reproduce in the with all ?
I'm not referring to autocompletion, but what I mean is for the anchor links to work in preview mode (editor mode is fine) they have to include raw HTML tags I.e., the attribute values generated for headers include raw HTML tags I tested it in with all extensions disabled and same result, but still I will test it in insiders build
tested at (clean), same results