jiebi/CodeConvo huggingface dataset:
Change:
<!-- 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.58.0 OS Version: Arch Linux x86_64 5.12.15-arch1-1 Steps to Reproduce: the VSCode interactive playground. down to the JavaScript Type Checking section. Description: The walkthrough section currently advises setting to get TS checks in JavaScript files. ! The property's been deprecated in favour of . ! The walkthrough should be updated to reflect the same.

Discussion:
easy = 42; ||| <del> >**Tip:** You can also enable the checks workspace or application wide by adding |"javascript.implicitProjectConfig.checkJs": true| to your workspace or user settings and explicitly ignoring files or lines using |// @ts-nocheck| and |// @ts-expect-error|. Check out the docs on [JavaScript in VS Code](https://code.visualstudio.com/docs/languages/javascript) to learn more. </del> <ins> >**Tip:** You can also enable the checks workspace or application wide by adding |"js/ts.implicitProjectConfig.checkJs": true| to your workspace or user settings and explicitly ignoring files or lines using |// @ts-nocheck| and |// @ts-expect-error|. Check out the docs on [JavaScript in VS Code](https://code.visualstudio.com/docs/languages/javascript) to learn more. </ins> ## Thanks!
Change:
Testing disassembly view scrolling, look at the scroll bar and notice the aggressive jumping suggest to use a much bigger initial view size so the scrolling will be much smoother. Current experience is very rough.
will fix this.

Discussion:
if (this._disassembledInstructions) { this._disassembledInstructions.splice(0, this._disassembledInstructions.length); this._instructionBpList = this._debugService.getModel().getInstructionBreakpoints(); <del> this.loadDisassembledInstructions(targetAddress, -DisassemblyView.NUM_INSTRUCTIONS_TO_LOAD, DisassemblyView.NUM_INSTRUCTIONS_TO_LOAD * 2).then(() => { </del> <ins> this.loadDisassembledInstructions(targetAddress, -DisassemblyView.NUM_INSTRUCTIONS_TO_LOAD * 4, DisassemblyView.NUM_INSTRUCTIONS_TO_LOAD * 8).then(() => { </ins> // on load, set the target instruction in the middle of the page. if (this._disassembledInstructions!.length > 0) { const targetIndex = Math.floor(this._disassembledInstructions!.length / 2);
Change:
Issue Type: <bBug</bRelated to and Steps to reproduce: and or corresponding JS settings. Create new TS or JS file and paste next code: and ! TS Version 4.4.0-dev. VS Code version: Code - Insiders 1.59.0-insider (, 2021-07-28T05:13:47.114Z) OS version: WindowsNT x64 10.0. Restricted Mode: No <details<summarySystem Info</summary </detailsExtensions: none<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
/assign
/ Can you please take a look? I believe that folding generates two new requests for inlay hints that VS Code then displays incorrectly. Here's the TS server trace from folding with only : The position of the hints seem correct to me. I don't know why VS Code requests the hints twice here though (or why it needs to re-request any hints on folding in this case since no new code became visible)
These are the visible ranges: ! And vscode sends two requests, one for each range. For some reason, each reuqest returns one inlay hint, so in total, there are 2 inlay hints: ! do you have an idea why this is? To me, it looks like a bug in the provider, there should not be a result for the second request.
Emmmmmm... I think I know the reason. In the tsserver. For each request, we will get the hint in the area that overlay with the visible range (not strictly included). Honestly, I don't know about this behavior. We may could de-duplicate these items?
Can't you just filter out all inlay hints whose position is not in the requested range?
Well, do you prefer to do it in vscode or ts side?
Hmm, maybe actually in vscode.
Verified fixed with TypeScript Nightly in

Discussion:
export async function getInlayHints(model: ITextModel, ranges: Range[], token: CancellationToken): Promise<InlayHintsData[]> { const datas: InlayHintsData[] = []; const providers = InlayHintsProviderRegistry.ordered(model).reverse(); <del> const promises = flatten(providers.map(provider => ranges.map(range => Promise.resolve(provider.provideInlayHints(model, range, token)).then(result => { if (result) { datas.push({ list: result, provider }); } }, err => { onUnexpectedExternalError(err); })))); </del> <ins> const promises = flatten(providers.map(provider => ranges.map(range => { return Promise.resolve(provider.provideInlayHints(model, range, token)).then(result => { const itemsInRange = result?.filter(hint => range.containsPosition(hint.position)); if (itemsInRange?.length) { datas.push({ list: itemsInRange, provider }); } }, err => { onUnexpectedExternalError(err); }); }))); </ins> await Promise.all(promises);
Change:
Issue Type: <bBug</bThe toolbar (hover or main) doesn't allow me to enter a cell above other cells. I have to select the first cell and hit 'a', or use the command palette and pick 'Insert Cell Above' VS Code version: Code - Insiders 1.59.0-insider (, 2021-07-28T19:37:22.975Z) OS version: WindowsNT x64 10.0. Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (14)</summaryExtensionVersion ------ vscode-eslint2.1.23 prettier-vscode8.1.0 python2021.8.-dev vscode-pylance2021.7.8-pre.1 jupyter2021.8. remote-containers0.190.0 remote-ssh0.65.7 remote-ssh-edit0.65.7 remote-wsl0.58.2 vscode-remote-extensionpack0.21.0 hexeditor1.8.2 js-debug-nightly2021.7.2717 live-server0.2.6 vscode-typescript-next4.4. (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
With our insert toolbar styling update, we didn't update the insert toolbar above the first cell, which is intended for inserting cells above first cell.
Fixed in both release and main branch.
closedWith
closedWith

Discussion:
opacity: 1; } */ <ins> .monaco-workbench .notebookOverlay .cell-list-top-cell-toolbar-container:focus-within, .monaco-workbench .notebookOverlay .cell-list-top-cell-toolbar-container:hover, </ins> .monaco-workbench .notebookOverlay.notebook-editor-editable > .cell-list-container > .monaco-list > .monaco-scrollable-element > .monaco-list-rows > .monaco-list-row .cell-bottom-toolbar-container:hover, .monaco-workbench .notebookOverlay.notebook-editor-editable > .cell-list-container > .monaco-list > .monaco-scrollable-element > .monaco-list-rows > .monaco-list-row .cell-bottom-toolbar-container:focus-within { opacity: 1;
Change:
Open Make the file dirty, disable autosave Use the pencil icon to try to change a setting Get an error that the file is dirty Click "Save and retry" Nothing happens Press cmd+s to save Get an error that the 'contents of the file are newer' because the pencil actually wrote to the backing file without updating the editor
Do you still see this on the latest Insiders? I'm unable to reproduce the issue.
I can still repro

Discussion:
const reference = await this.resolveModelReference(resource); try { const formattingOptions = this.getFormattingOptions(reference.object.textEditorModel); <del> if (this.uriIdentityService.extUri.isEqual(resource, this.environmentService.settingsResource)) { </del> <ins> if (!this.textFileService.isDirty(resource) /* go through text model save if the model is dirty */ && this.uriIdentityService.extUri.isEqual(resource, this.environmentService.settingsResource)) { </ins> await this.userConfigurationFileService.updateSettings({ path: operation.jsonPath, value: operation.value }, formattingOptions); } else { await this.updateConfiguration(operation, reference.object.textEditorModel, formattingOptions);
Change:
<!-- 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. --There's currently an issue on the terminal of the VSCode that slows down the refactoring process of files specially on frameworks that relies heavily on the dollar sign for file structure like or . Any tool or place that spells out the path + filename containing $ is ignored by the cmd + click. Folders are even worse because it breaks their children. <!-- 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.58.2 OS Version: macOS Big Sur 11.5 (20G71) Steps to Reproduce: a file or a folder with the dollar sign on it it out using any tool or just run: !
Code pointer:

Discussion:
const pathSeparatorClause = '/'; // '":; are allowed in paths but they are often separators so ignore them // Also disallow  to prevent a catastropic backtracking case #24795 <del> const excludedPathCharactersClause = '[^0s!$`&*()[]'":;]'; </del> <ins> const excludedPathCharactersClause = '[^0s!`&*()[]'":;]'; </ins> /** A regex that matches paths in the form /foo, ~/foo, ./foo, ../foo, foo/bar */ export const unixLocalLinkClause = '((' + pathPrefix + '|(' + excludedPathCharactersClause + ')+)?(' + pathSeparatorClause + '(' + excludedPathCharactersClause + ')+)+)'; export const winDrivePrefix = '(?:?)?[a-zA-Z]:'; const winPathPrefix = '(' + winDrivePrefix + '|..?|~)'; const winPathSeparatorClause = '(|/)'; <del> const winExcludedPathCharactersClause = '[^0<>?|/s!$`&*()[]'":;]'; </del> <ins> const winExcludedPathCharactersClause = '[^0<>?|/s!`&*()[]'":;]'; </ins> /** A regex that matches paths in the form ?c:foo c:foo, ~foo, .foo, ..foo, foobar */ export const winLocalLinkClause = '((' + winPathPrefix + '|(' + winExcludedPathCharactersClause + ')+)?(' + winPathSeparatorClause + '(' + winExcludedPathCharactersClause + ')+)+)';

'/foo', '~/foo', './foo', <ins> './$foo', </ins> '../foo', '/foo/bar', '/foo/bar+more',

'c:/foo', '.foo', './foo', <ins> './$foo', </ins> '..foo', '~foo', '~/foo',
Change:
<!-- 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?: N/A <!-- 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. --OS version: Darwin x64 20.5.0 This is originally reported on This is a new release issue (1.59) as I have tested on 1.58. Steps to Reproduce: extension to uninstall VSpaceCode I get the following error: !
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.531 --- <!-- score: 0.445 --<!-- potentialduplicatescomment --
Related to
Thanks for filing the bug and also providing the fix. I will be pushing the fix to insiders which will be available tomorrow and fix will be included in next stable. Here is a workaround for now to use in stable - To uninstall open extensions folder using command and remove the extension.

Discussion:
for (const extension of extensionsToUninstall) { const dependents = this.getDependents(extension, installed); if (dependents.length) { <del> const remainingDependents = dependents.filter(dependent => extensionsToUninstall.indexOf(dependent) === -1); </del> <ins> const remainingDependents = dependents.filter(dependent => !extensionsToUninstall.some(e => areSameExtensions(e.identifier, dependent.identifier))); </ins> if (remainingDependents.length) { throw new Error(this.getDependentsErrorMessage(extension, remainingDependents, extensionToUninstall)); }
Change:
This code seems to reach into the module: When trying to update to the file is no longer found and seems gone.

Discussion:
*--------------------------------------------------------------------------------------------*/ Object.defineProperty(exports, "__esModule", { value: true }); const retry_1 = require("./retry"); <del> const { installBrowsersWithProgressBar } = require('playwright/lib/install/installer'); </del> <ins> const { installDefaultBrowsersForNpmInstall } = require('playwright/lib/utils/registry'); </ins> async function install() { <del> await (0, retry_1.retry)(() => installBrowsersWithProgressBar()); </del> <ins> await (0, retry_1.retry)(() => installDefaultBrowsersForNpmInstall()); </ins> } install();

*--------------------------------------------------------------------------------------------*/ import { retry } from './retry'; <del> const { installBrowsersWithProgressBar } = require('playwright/lib/install/installer'); </del> <ins> const { installDefaultBrowsersForNpmInstall } = require('playwright/lib/utils/registry'); </ins> async function install() { <del> await retry(() => installBrowsersWithProgressBar()); </del> <ins> await retry(() => installDefaultBrowsersForNpmInstall()); </ins> } install();

"optimist": "0.3.5", "p-all": "^1.0.0", "path-browserify": "^1.0.1", <del> "playwright": "1.12.3", </del> <ins> "playwright": "1.14.1", </ins> "pump": "^1.0.1", "queue": "3.0.6", "rcedit": "^1.1.0",

"elliptic": "^6.5.3", "nwmatcher": "^1.4.4" } <del> } </del>  No newline at end of file <ins> } </ins>

dependencies: find-up "^4.0.0" <del> playwright@1.12.3: version "1.12.3" resolved "https://registry.yarnpkg.com/playwright/-/playwright-1.12.3.tgz#113afa2cba10fb56e9a5b307377343e32a155a99" integrity sha512-eyhHvZV7dMAUltqjQsgJ9CjZM8dznzN1+rcfCI6W6lfQ7IlPvTFGLuKOCcI4ETbjfbxqaS5FKIkb1WDDzq2Nww== </del> <ins> playwright@1.14.1: version "1.14.1" resolved "https://registry.yarnpkg.com/playwright/-/playwright-1.14.1.tgz#73913d3044a85a58edf13148245279231072532e" integrity sha512-JYNjhwWcfsBkg0FMGLbFO9e58FVdmICE4k97/glIQV7cBULL7oxNjRQC7Ffe+Y70XVNnP0HSJLaA0W5SukyftQ== </ins> dependencies: commander "^6.1.0" debug "^4.1.1"
Change:
<!-- 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 sure --the only reliable way I know how to reproduce it is by creating a spelling error with Code Spell Checker. If anyone has any tips how I can try to repro this with all exts enabled, I'm happy to take that on and post a new GIF. <!-- 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. --Version: 1.59.0 (user setup) Commit: Date: 2021-08-04T23:13:12.822Z Electron: 13.1.7 Chrome: 91.0.4472.124 14.16.0 V8: 9.1.269.36-electron.0 OS: WindowsNT x64 10.0. Steps to Reproduce: exactly one information status to be reported in the status bar and observe the tooltip tooltip will read instead of !
It shows up in plural form for all 3(errors, warnings and infos) even if only 1 of them is present. Source
If you want to implement different cases, this would involve having separate translation strings for the singular and plural, as well as a third case for the 0 value. But is it really necessary? One could easily avoid the grammatical discussion if you put like this: , , .
Seems very reasonable to me
This looks better and is understandable
Can I take on this issue( If it is not assigned to someone else )? It looks fairly simple to me. But as I'm quite new to this so I might need some guidance.
I have made the changes to correct the typos. Should I make a PR or it is already completed?

Discussion:
} private getMarkersTooltip(stats: MarkerStatistics): string { <del> const errorTitle = (n: number) => localize('totalErrors', "{0} Errors", n); const warningTitle = (n: number) => localize('totalWarnings', "{0} Warnings", n); const infoTitle = (n: number) => localize('totalInfos', "{0} Infos", n); </del> <ins> const errorTitle = (n: number) => localize('totalErrors', "Errors: {0}", n); const warningTitle = (n: number) => localize('totalWarnings', "Warnings: {0}", n); const infoTitle = (n: number) => localize('totalInfos', "Infos: {0}", n); </ins> const titles: string[] = [];
Change:
Issue Type: <bBug</bDetails and reproduction steps are in this video clip: I have reproduced this on two different computers (both Windows 10) VS Code version: Code 1.59.0 (, 2021-08-04T23:13:12.822Z) OS version: WindowsNT x64 10.0. Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (26)</summaryExtensionVersion ------ shaderlabvscodefree1.2.6 better-toml0.3.2 vscode-markdownlint0.39.0 gitlens10.2.3 EditorConfig0.15.1 todo-tree0.0.188 vscode-nuget-package-manager1.1.6 csharpfixformat0.0.84 rainbow-csv1.8.1 csharp1.23.14 python2020.5. remote-wsl0.44.2 vscode-unitymeta0.0.7 ruby0.27.0 shader1.1.4 shader-toy0.10.15 code-spell-checker1.8.0 unity-tools1.2.12 org-mode0.5.0 vscode-lua0.12.4 sort-lines1.9.0 unity-debug3.0.2 vim1.18.9 vscode-ruby0.27.0 moonsharp-debug1.8.3 json1.0.4 </details<!-- generated by issue reporter --
Thanks for the detailed repro steps, this is an issue with occlusion tracker in the runtime. Please add the following flag to the vscode launch arguments as a temporary workaround.
Duplicates

Discussion:
} }); <ins> /* Following features are disabled from the runtime. * `CalculateNativeWinOcclusion` - Disable native window occlusion tracker, *	Refs https://groups.google.com/a/chromium.org/g/embedder-dev/c/ZF3uHHyWLKw/m/VDN2hDXMAAAJ */ app.commandLine.appendSwitch('disable-features', 'CalculateNativeWinOcclusion'); </ins> // Support JS Flags const jsFlags = getJSFlags(cliArgs); if (jsFlags) {
Change:
<!-- 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.59.0 OS Version: macOS 11.5.2 (20G95) Steps to Reproduce: -click on an extension. "Copy Extension Id". Both "Id" and "ID" are used: Language Id Copy Extension Id Copy Command ID Copy Setting ID The use of "ID" appears to be consistent in the translations, in for example.

Discussion:
const details = $('details', { open: true, ontoggle: onDetailsToggle }, $('summary', { tabindex: '0' }, localize('localizations', "Localizations ({0})", localizations.length)), $('table', undefined, <del> $('tr', undefined, $('th', undefined, localize('localizations language id', "Language Id")), $('th', undefined, localize('localizations language name', "Language Name")), $('th', undefined, localize('localizations localized language name', "Language Name (Localized)"))), </del> <ins> $('tr', undefined, $('th', undefined, localize('localizations language id', "Language ID")), $('th', undefined, localize('localizations language name', "Language Name")), $('th', undefined, localize('localizations localized language name', "Language Name (Localized)"))), </ins> ...localizations.map(localization => $('tr', undefined, $('td', undefined, localization.languageId), $('td', undefined, localization.languageName || ''), $('td', undefined, localization.localizedLanguageName || ''))) ) );

this.registerExtensionAction({ id: 'workbench.extensions.action.copyExtensionId', <del> title: { value: localize('workbench.extensions.action.copyExtensionId', "Copy Extension Id"), original: 'Copy Extension Id' }, </del> <ins> title: { value: localize('workbench.extensions.action.copyExtensionId', "Copy Extension ID"), original: 'Copy Extension ID' }, </ins> menu: { id: MenuId.ExtensionContext, group: '1_copy'
Change:
See Code pointer:
Hi. Is this issue under progress? If not, I'd like to take it up
if you could hold off a few days to give a chance to take it if they want that would be good (see ).
file code preferences keyboardstype "scm view"

Discussion:
registerSendSequenceKeybinding(String.fromCharCode('E'.charCodeAt(0) - 64), { mac: { primary: KeyMod.CtrlCmd | KeyCode.RightArrow } }); <ins> // Break: ctrl+C registerSendSequenceKeybinding(String.fromCharCode('C'.charCodeAt(0) - 64), { mac: { primary: KeyMod.CtrlCmd | KeyCode.US_DOT } }); </ins> setupTerminalCommands();