jiebi/CodeConvo huggingface dataset:
Change:
<!-- 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. --- VSCode Version: 1.47.0 OS Version: macOS Catalina 10.15.5 Steps to Reproduce: Every time when I click File -New File, vscode always asks to select an Editor, but in the list, there is only one Built-in Text editor. it's just a very annoying unnecessary click. I don't know since when this has been , I believe it's a recent change. Tried to remove all the User settings and start without extensions, didn't help. See the screenshot. <img width="1086" alt="Screen Shot 2020-07-12 at 9 35 03 pm" src="https://user-"<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No Yes
Hi, I would like to work on this issue if no one else is.
Sorry I did't claim before starting, I have fixed it, please correct me if the solution is not ok.
I removed all the User settings and extensions, useless
No worries. Go ahead

Discussion:
return; } <del> const overrideToUse = typeof id === 'string' && allEditorOverrides.find(([_, entry]) => entry.id === id); </del> <ins> let overrideToUse; if (typeof id === 'string') { overrideToUse = allEditorOverrides.find(([_, entry]) => entry.id === id); } else if (allEditorOverrides.length === 1) { overrideToUse = allEditorOverrides[0]; } </ins> if (overrideToUse) { return overrideToUse[0].open(input, overrideOptions, group, OpenEditorContext.NEW_EDITOR)?.override; }
Change:
Some extensions only apply languages to files with an exact name by default. They should instead include all files ending with the relevant extension, regardless of the prefix. Examples I found are: The npm extension applies the language only to files named exactly , e.g. not to The npm extension applies the language only to files named exactly , e.g. not to The git extension applies the language only to files named exactly , e.g. not The built-in file icon theme recognizes these files by their extension and shows the matching icons besides them, but some extensions don't apply the relevant language to it. A project might include multiple files of the same type in the same folder, and configure their tools to use one or the other, depending on the need. All of the files should have the correct language regardless of their filename, all that should matter is the file extension. Repro: Create and open a file named Expected: The language mode will be set to the "Ignore" language Actual: The language mode is "Plain Text"

Discussion:
"Ignore", "ignore" ], <del> "filenames": [ </del> <ins> "extensions": [ </ins> ".gitignore_global", ".gitignore" ],

"languages": [ { "id": "ignore", <del> "filenames": [ </del> <ins> "extensions": [ </ins> ".npmignore" ] }, { "id": "properties", <del> "filenames": [ </del> <ins> "extensions": [ </ins> ".npmrc" ] }
Change:
Some extensions only apply languages to files with an exact name by default. They should instead include all files ending with the relevant extension, regardless of the prefix. Examples I found are: The npm extension applies the language only to files named exactly , e.g. not to The npm extension applies the language only to files named exactly , e.g. not to The git extension applies the language only to files named exactly , e.g. not The built-in file icon theme recognizes these files by their extension and shows the matching icons besides them, but some extensions don't apply the relevant language to it. A project might include multiple files of the same type in the same folder, and configure their tools to use one or the other, depending on the need. All of the files should have the correct language regardless of their filename, all that should matter is the file extension. Repro: Create and open a file named Expected: The language mode will be set to the "Ignore" language Actual: The language mode is "Plain Text"

Discussion:
}, { "id": "properties", <del> "extensions": [ ".properties", ".cfg", ".conf", ".directory" ], "filenames": [ ".gitattributes", ".gitconfig", "gitconfig", ".gitmodules", ".editorconfig" ], </del> <ins> "extensions": [ ".properties", ".cfg", ".conf", ".directory", ".gitattributes", ".gitconfig", ".gitmodules", ".editorconfig" ], "filenames": [ "gitconfig" ], </ins> "filenamePatterns": [ "**/.config/git/config", "**/.git/config" ], "aliases": [ "Properties", "properties" ], "configuration": "./properties.language-configuration.json"
Change:
<!-- 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. --- VSCode Version: 1.47.2 (user setup) OS Version: Windows_NT x64 10.0. Steps to Reproduce: a file named in any directory. the file with VS Code. file is opened with the "JSON" language mode (instead of the expected "JSON with Comments" mode). Other file names, e.g. , are also opened in "JSON" language mode. In contrast, is opened in "JSON with Comments" mode even if the file name contains suffixes, e.g. . <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
This is easily fixable, look at the relevant code: Submit a PR
Thank you. Is a local build/test warranted, or would a direct PR suffice? Asking because I don't have a local build environment right now (and setting up one would take some time)

Discussion:
], "filenamePatterns": [ "tsconfig.*.json", <del> "tsconfig-*.json" </del> <ins> "jsconfig.*.json", "tsconfig-*.json", "jsconfig-*.json" </ins> ] } ],
Change:
<!-- 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. --Issue Type: <bBug</bAppears here in the logs: [userDataSync] [info] Auto sync: Canelled sync that is in progress VS Code version: Code - Insiders 1.48.0-insider (, 2020-07-24T05:57:10.466Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (47)</summaryExtensionVersion ------ user-secrets2.0.1 Bookmarks11.3.1 ng-template0.1000.4 vscode-eslint2.1.8 docs-markdown0.2.76 gitlens10.2.2 EditorConfig0.15.1 prettier-vscode5.1.3 vscode-firefox-debug2.9.0 dotnet-test-explorer0.7.3 todo-tree0.0.178 vscode-edit-csv0.3.0 rainbow-csv1.7.0 git-graph1.24.0 vscode-docker1.3.1 csharp1.22.1 vscode-kubernetes-tools1.2.1 vscode-postgresql0.3.0 anaconda-extension-pack1.0.1 python2020.7. vscode-pylance2020.7.2 remote-containers0.128.0 remote-ssh0.51.0 remote-ssh-edit0.51.0 remote-wsl0.44.4 vscode-remote-extensionpack0.20.0 vscode-typescript-tslint-plugin1.2.3 debugger-for-chrome4.12.9 debugger-for-edge1.0.15 sqltools0.22.10 sqltools-driver-sqlite0.1.0 material-icon-theme4.2.0 polacode0.3.4 java0.64.1 vscode-yaml0.9.1 multi-command1.4.0 scala0.4.1 metals1.9.2 code-spell-checker1.9.0 pdf1.1.0 vscodeintellicode1.2.9 vscode-java-debug0.27.0 vscode-java-dependency0.10.2 vscode-java-pack0.9.1 vscode-java-test0.24.0 vscode-maven0.22.0 vscode-nginx0.7.2 (1 theme extensions excluded) </details<!-- generated by issue reporter --

Discussion:
this._register(toDisposable(() => { if (this.syncPromise) { this.syncPromise.cancel(); <del> this.logService.info('Auto sync: Canelled sync that is in progress'); </del> <ins> this.logService.info('Auto sync: Cancelled sync that is in progress'); </ins> this.syncPromise = undefined; } if (this.syncTask) {
Change:
Testing 1) VSCode Smoke Tests (Web) VSCode Smoke Tests (Web) Language Features verifies settings: Error: Timeout: get element '.view-overlays .cdr.squiggly-error' after 20 seconds. at D:Sourcegithubmicrosoftvscodetestautomationout at (<anonymous) at fulfilled (D:Sourcegithubmicrosoftvscodetestautomationout)
What was the exact command line you used to run the smoke test?
Please double check this, since I believe the issue doesn't happen if you skip the notebook tests altogether. Simply replace with here: And recompile the smoketests with .
I am able to reproduce this failure even after commenting out all the notebook tests.
I also have it reproducible on my machine, although I believe it's a timing issue. No configuration event is triggered here after the settings file is updated.

Discussion:
IFileSystemProviderWithOpenReadWriteCloseCapability, IFileSystemProviderWithFileReadStreamCapability { <del> readonly capabilities: FileSystemProviderCapabilities = this.fileSystemProvider.capabilities; </del> readonly onDidChangeCapabilities: Event<void> = this.fileSystemProvider.onDidChangeCapabilities; private readonly _onDidChangeFile = this._register(new Emitter<readonly IFileChange[]>());

this._register(this.fileSystemProvider.watch(this.fileSystemUserDataHome, { recursive: false, excludes: [] })); this._register(this.fileSystemProvider.onDidChangeFile(e => this.handleFileChanges(e))); } <ins> get capabilities() { return this.fileSystemProvider.capabilities; } </ins> watch(resource: URI, opts: IWatchOptions): IDisposable { return this.fileSystemProvider.watch(this.toFileSystemResource(resource), opts);
Change:
<!-- 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. --- VSCode Version: 1.47.3 OS Version: macOS Steps to Reproduce: and to your settings. JavaScript file and write , press Tab to autocomplete. Actual behavior, parameter hints are visible even though config is false. Expected behavior, parameter hints are invisible. /cc
Same happens for TypeScript.
Hi I am currently attempting to work on this issue and I have a quick question. With "editor.parameterHints.enabled" set to false and "*.suggest.completeFunctionCalls" set to true is the expected behavior to have the parentheses still be inserted but just not have the popup appear or should the parentheses not be inserted?
You just need to disable parameter hints. The problem is they appear even if they are disabled. Imagine this pseudo code:
I know I fixed it. Im gonna submit a PR now.

Discussion:
const { snippet, parameterCount } = snippetForFunctionCall(item, detail.displayParts); item.insertText = snippet; if (parameterCount > 0) { <del> commands.push({ title: 'triggerParameterHints', command: 'editor.action.triggerParameterHints' }); </del> <ins> //Fix for https://github.com/microsoft/vscode/issues/104059 //Don't show parameter hints if "editor.parameterHints.enabled": false if (vscode.workspace.getConfiguration('editor.parameterHints').get('enabled')) { commands.push({ title: 'triggerParameterHints', command: 'editor.action.triggerParameterHints' }); } </ins> } } }
Change:
Oh, these are deprecated. Maybe the error only shows up because I have configured them. Anyway I can add a simple change so that they show up (configured deprecated settings will be shown in the settings UI)
Closing this since PR got merged
To verify Open Developer tools console Open Settings editor (UI) make sure above warning is not shown

Discussion:
{ id: 'application/settingsSync', label: localize('settingsSync', "Settings Sync"), <del> settings: ['settingsSync.*'] </del> <ins> settings: ['settingsSync.*', 'sync.*'] </ins> } ] }
Change:
<!-- 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. --This is essentially a more general issue of the closed Markdown styling support are missing in the following, missing bold and italic: Solarized Light Red Abyss Solarized Dark Tomrrow Night Blue See screenshot below for an example. For High Contrast, section heading () are not in bold. I am unclear if it's a bug or intentional. Screenshot for Solarized Dark !
Hi, I tried bold and italic with these themes: theme-tomorrow-night-blue theme-solarized-dark theme-solarized-light theme-red theme-kimbie-dark theme-abyss hcblackdefaults(High Contrast)

Discussion:
} }, { <del> "name": "Markup Setext Header", "scope": "markup.heading.setext", </del> <ins> "name": "Markup Headings", "scope": [ "markup.heading", "markup.heading.setext" ], </ins> "settings": { <del> "fontStyle": "", "foreground": "#ddbb88" </del> <ins> "fontStyle": "bold", "foreground": "#6688cc" </ins> } } ],

{ "scope": "markup.heading", "settings": { <ins> "fontStyle": "bold", </ins> "foreground": "#6796e6" } },

"entity.name.section" ], "settings": { <del> "fontStyle": "", </del> <ins> "fontStyle": "bold", </ins> "foreground": "#8ab1b0" } },

} }, { <del> "name": "Markup Inline", "scope": "markup.inline.raw", </del> <ins> "name": "Markup: Strong", "scope": "markup.bold", </ins> "settings": { <del> "fontStyle": "", "foreground": "#cd8d8dff" </del> <ins> "fontStyle": "bold" </ins> } }, { <del> "name": "Markup Headings", "scope": "markup.heading", </del> <ins> "name": "Markup: Emphasis", "scope": "markup.italic", </ins> "settings": { <del> "foreground": "#fec758ff" </del> <ins> "fontStyle": "italic" </ins> } }, { <del> "name": "Markup Setext Header", "scope": "markup.heading.setext", </del> <ins> "name": "Markup Inline", "scope": "markup.inline.raw", </ins> "settings": { "fontStyle": "", <ins> "foreground": "#cd8d8dff" } }, { "name": "Headings", "scope": [ "markup.heading", "markup.heading.setext", "punctuation.definition.heading", "entity.name.section" ], "settings": { "fontStyle": "bold", </ins> "foreground": "#fec758ff" } },

"name": "Markup Headings", "scope": "markup.heading", "settings": { <ins> "fontStyle": "bold", </ins> "foreground": "#268BD2" } },

} }, { <ins> "name": "Markup: Strong", "scope": "markup.bold", "settings": { "fontStyle": "bold" } }, { "name": "Markup: Emphasis", "scope": "markup.italic", "settings": { "fontStyle": "italic" } }, { </ins> "name": "Markup Inline", "scope": "markup.inline.raw", "settings": {

} }, { <ins> "name": "Markup Headings", "scope": "markup.heading", "settings": { "fontStyle": "bold" } }, { </ins> "scope": "token.info-token", "settings": { "foreground": "#6796e6"
Change:
[x] Add category to marketplace [x] Update completions for [x] Update completions for extensions view [x] Update completions for cli [x] Update documentation
VSCE doesn't hardcode categories, removed that checkbox from the initial post.
Thanks I wasn't sure so figured I'd cover it just in case. :) I opened an issue with the marketplace team to get this onto the sprint plan.
Reopening for the last 2 tasks
I think we can check off 4th item right?
Ah I didn't test this but if the constants fix this too then sounds good!
Reference is updated here:

Discussion:
'Data Science', 'Debuggers', 'Extension Packs', <ins> 'Education', </ins> 'Formatters', 'Keymaps', 'Language Packs',
Change:
<!-- 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: --Same issue as , just on a different version. <!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.48 OS Version: Windows 10 <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes Edit Possible reason: In , is missing. imports this script but it is not there. This might explain why the submit action does nothing. Edit 2 Thanks, for the workaround:  it in
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.803 --- <!-- score: 0.503 --- <!-- score: 0.499 --- <!-- score: 0.459 --- <!-- score: 0.449 --<!-- potentialduplicatescomment --
FYI, I was able to get it working by downloading and placing the following file.
Confirm, an old bug returned.
Where to place it?
Not exactly an old bug. It's more like the devs team forgot to bundle the 1 single script. See my edit of the OP.
I think the easiest workaround is to install the downgraded VSCode from the following link.
same on MacOS. Makes the whole tool useless as you can't click anything than force quit the application.
looks like this file needs to be explicitly listed somewhere here to be included in the build (I think the does not exist anymore and can be removed):
Sorry about the breakage. Thanks for narrowing down the issue.
Steps to verify: Clone cd basic-auth && open code-insiders Settings Proxy http://127.0.0.1:3129 Open developer tools fetch('') or perform any network request play with the auth dialog verify the auth dialog can be opened again once proxy config is changed

Discussion:
'out-build/vs/code/electron-browser/sharedProcess/sharedProcess.js', 'out-build/vs/code/electron-sandbox/issue/issueReporter.js', 'out-build/vs/code/electron-sandbox/processExplorer/processExplorer.js', <del> 'out-build/vs/platform/auth/common/auth.css', </del> <ins> 'out-build/vs/code/electron-sandbox/proxy/auth.js', </ins> '!**/test/**' ];
Change:
<!-- 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. --- VSCode Version: 1.48.0 OS Version: Ubuntu 18.04 Steps to Reproduce: some folders into a workplace a folder (folder A) that contains only 1 file into the same workplace all folders "Collapse Folders In Explorer" button the result The interesting thing is: if you collapse the folder A, the "Collapse Folders In Explorer" button works normally again This is an animation to demonstrate that: ! <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Works fine for me. Thanks for filling this issue. Can you reproduce using Visual Studio Code Insiders Also if you F1 developer tools console do you see some errors? fyi
I tried with Insider version, the result is the same, the bug still happens. And when I open the console log, there is nothing. I guess the logic in code is incorrect, so it doesn't throw any error. Please check this gif below (for Insider version): ! This was captured in my MacBook at home, so this bug happened in both Ubuntu 18.04 and Mac OS 10.15.6
I can easily reproduce with a workspace containing just two folders: rootfolder 1 rootfolder 2 I'll create a PR with a fix.

Discussion:
for (const folder of treeInput) { if (tree.hasNode(folder) && !tree.isCollapsed(folder)) { for (const [, child] of folder.children.entries()) { <del> if (tree.hasNode(child) && !tree.isCollapsed(child)) { </del> <ins> if (tree.hasNode(child) && tree.isCollapsible(child) && !tree.isCollapsed(child)) { </ins> return true; } }
Change:
On previous versions of VSCode (1.47) you received a message when attempting to save a file that was marked read only: ! As of 1.48, you receive a different message that lacks an overwrite option: ! When a file is simply marked as read only, retrying as admin is not an appropriate option and fails to resolve the issue. Please restore Overwrite functionality as it is very useful for us that use archaic source control systems that rely on making files read only. VSCode Version: 1.48.0 OS Version: Windows 10 (1903) Steps to Reproduce: a file with the read only flag set a change to the file the file Does this issue occur on the latest insiders build?: Yes Does this issue occur when all extensions are disabled?: Yes
Thanks, a regression we can probably fix for recovery.
Was just about to post this as well. This changed about 3-4 weeks back in VSCode Insiders as well if that time frame helps.
Works great, I have verified the fix on windows with read-only files.

Discussion:
} try { <del> return super.write(resource, value, options); </del> <ins> return await super.write(resource, value, options); </ins> } catch (error) { // In case of permission denied, we need to check for readonly
Change:
Issue Type: <bBug</bRecent update to 1.48.0 seems to have killed sorting the Run Build Task list by most recently used. In fact, the list doesn't appear to change order at all (not sorting lexicographically, either). VS Code version: Code 1.48.0 (, 2020-08-13T07:50:42.600Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (7)</summaryExtensionVersion ------ vscode-open-in-application1.0.5 cortex-debug0.3.7 cpptools0.29.0 cmake0.0.17 vscodeintellicode1.2.10 clang-format1.9.0 linkerscript1.0.1 </details<!-- generated by issue reporter --
To verify: Open a folder with build tasks, such as the VS Code repo. If you use the VS Code repo, in the change the of the task to simply be (no ). Run the Tasks: Run Build Task command Choose a build task and run it from that quick pick Run the Tasks: Run Build Task command again. Verify that the task you just ran shows at the top of the list in the recently used section. Repeat with another build task.
Verified in Version: 1.48.1 Commit: Date: 2020-08-18T17:06:48.722Z

Discussion:
} if (buildTasks.length === 1) { this.tryResolveTask(buildTasks[0]).then(resolvedTask => { <del> this.run(resolvedTask).then(undefined, reason => { </del> <ins> this.run(resolvedTask, undefined, TaskRunSource.User).then(undefined, reason => { </ins> // eat the error, it has already been surfaced to the user and we don't care about it here }); });

this.runConfigureDefaultBuildTask(); return; } <del> this.run(task, { attachProblemMatcher: true }).then(undefined, reason => { </del> <ins> this.run(task, { attachProblemMatcher: true }, TaskRunSource.User).then(undefined, reason => { </ins> // eat the error, it has already been surfaced to the user and we don't care about it here }); });

if (tasks.length > 0) { let { defaults, users } = this.splitPerGroupType(tasks); if (defaults.length === 1) { <del> this.run(defaults[0]).then(undefined, reason => { </del> <ins> this.run(defaults[0], undefined, TaskRunSource.User).then(undefined, reason => { </ins> // eat the error, it has already been surfaced to the user and we don't care about it here }); return;

this.runConfigureTasks(); return; } <del> this.run(task).then(undefined, reason => { </del> <ins> this.run(task, undefined, TaskRunSource.User).then(undefined, reason => { </ins> // eat the error, it has already been surfaced to the user and we don't care about it here }); });