Change:
Type: <bBug</bI got the following error randomly while changing workspace settings. I used the extension bisect feature to see if it was an extension, but nothing was identified on the very first pass. The issue continued to persist, until Visual Studio Code was reloaded. Here's the message that appeared in the problem pane: Problems loading reference 'vscode://schemas/settings/workspace': Unable to load schema from 'vscode://schemas/settings/workspace': cannot open vscode://schemas/settings/workspace. Detail: Unable to resolve text model content for resource vscode://schemas/settings/workspace. I found a similar issue regarding multi-root workspaces on github: My workspace has multiple folders. I only edited the workspace settings and I never touched the folder settings for the workspace. I did made some recent adjustments by installing/uninstalling extensions, switching profiles, and editing workspace settings. VS Code version: Code - Insiders 1.77.0-insider (, 2023-03-14T05:23:49.668Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<details<summaryExtensions (11)</summaryExtensionVersion ------ Ionide-fsharp7.5.1 csharp1.25.4 dotnet-interactive-vscode1.0. vscode-dotnet-pack1.0.12 python2023.4.1 vscode-pylance2023.3.20 jupyter2023.3. jupyter-keymap1.1.0 jupyter-renderers1.0.15 vscode-jupyter-cell-tags0.1.6 vscode-jupyter-slideshow0.1.5 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
This is probably caused by of the schema (and others) It would be better to register the schema immediately but empty, and to set it later again with content.
Can this be at least workarounded somehow? It's very irritating - I cant edit any workspace settings
I'm sure a hotfix will release the fix to all of us soon, but here's a workaround for now: I found that poking any settings key in restores proper autocomplete/hover in VSCode's until next VSCode restart. But a key must be poked after every restart. For example, put at the top of your and save the file. You will have to toggle and save this key every time you start VSCode. A detailed set of steps for doing this can be inspected at the end of this comment. If you use the VSCode extension , you can set up a hotfix keybind (like in this case), and press the keybind twice every time you restart VSCode. Or, just never restart VSCode until the patch drops! <details<summarydetails</summary<pI can confirm that setting allows hover hints and completion to function again, e.g. in VSCode's own modification. However, this workaround throws out all JSON linting and reporting in the "Problems" pane, so it's sort of the nuclear option. This issue just cropped up for me in the past few days, so it may be a regression associated with the latest release? After further investigation, I find that poking any settings key in restores proper autocomplete/hover in VSCode's until next VSCode restart. But a key must be poked after every restart. Here's a rundown: all tree of settings keys are initially at their defaults, e.g. none of these keys are explicitly specified in any of your (maybe unnecessary, but this is my starting state). VSCode (e.g. with ). Navigate to your user . The following warning presents in the Problems pane: a trivial setting modification in the tree of settings keys, even if that modification is a no-op, like explicitly specifying a default as its default value. For example, put at the top of your and save the file. (You could've also poked to be either or I think, maybe?) whether autocomplete/hover works properly in , completing settings names and such. It should work now. can even remove the edit you made in step (4), save again, and autocomplete/hover still works. VSCode. autocomplete/hover is broken again in , until some modification to the tree of settings keys is made again, like in step 4. For example, commenting out if it's there, and saving, restores autocomplete/hover. So this issue may have to do with unstable startup behavior of JSON schema handling, perhaps isolated to VSCode's own or perhaps all JSON schemas more broadly, and this unstable state can be temporarily fixed by poking a settings key, but the unstable behavior returns on the next program start. At least in my case. </p</details
I have encountered a similar error: So nothing I do in my file has any effect. Not only that, but when I type "" into the Settings search bar, the only thing that comes up is a reference to a file under .
In my case I think I found the culprit: The property above gives a "Value is not accepted" error even though it's a valid value that works when the is enabled (it's currently disabled). As soon as I delete this property, the "Unable to load schema" error goes away. Weird. Update: I spoke too soon -- after reloading VS Code, the "Unable to load schema" error is back
A few days/restarts later, and the error is gone. Looks like a Heisenbug.
For me the problem message appears in a typescript node project when I have open. Close this file and the problem message goes away. (The file contains no known issues). While others report either user or workspace settings reference loading problems, for me it is configurationDefaults:
is there any update on it? it's very frustrating and I don't see a reliable workaround
<!-- 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!
I still see this <img width="1619" alt="image" src=""Repro: a syntax error in , which will result in some setting's value being "changed" that forces restart of vscode dialog to restart vscode shows up, click on "Restart" restarted vscode will likely have this error
I cannot reproduce this, are you seeing this consistently?
I can't repro deterministically, but I feel like it has to do with loading/reloading the window
Can others subscribed to this issue, please try our latest insiders and let us know if you still see the issue?
/verified
I confirm this is fixed in (tested under Ubuntu 22), and without the need for .
I just upgraded to the regular version and it also seems to be fixed there as expected ^^.
Can U confirm it is now fixed in version 1.80.0 and close the issue ?
The message is still there for me in 1.80.0.
Thanks for confirmation. I will close this as fixed and verified. Please reopen a new issue if you are still seeing it (may be new) with steps to repro.
For me the message showed up in 1.80.0
For me too
Currently experiencing this issue. I can overcome it temporarily following a suggestion elsewhere where I add or remove "": true to my file. I keep adjusting the file to see if there is something in there ausing the issue. Even old, known settings are causing the error to kick in regularly. I put a single setting in there and the error comes up unless it's empty Version: 1.80.0 (user setup) Commit: Date: 2023-07-04T15:06:02.407Z (1 wk ago) Electron: 22.3.14 ElectronBuildId: Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.
Currently experiencing the issue on my linux machine. On my Windows machine (with the same configuration file, since it's synchronized) it works fine on stable, but not on insiders. Can confirm that toggling as a workaround works until restart. Linux version: Version: 1.80.0 Commit: Date: 2023-07-04T13:39:48.236Z (1 wk ago) Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.80.0 Chrome/108.0.5359.215 Electron/22.3.14 Safari/537.36 Windows version (stable): Version: 1.80.0 Commit: Date: 2023-07-04T15:06:02.407Z (1 wk ago) Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.80.0 Chrome/108.0.5359.215 Electron/22.3.14 Safari/537.36 Windows version (insiders): Version: 1.81.0-insider Commit: Date: 2023-07-13T05:33:32.822Z (2 hrs ago) Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code-Insiders/1.81.0-insider Chrome/108.0.5359.215 Electron/22.3.14 Safari/537.36
Reopening this because it can be still reproduced.
I am getting this error and I can't figure out how to fix it.
Please try our and see if you are still seeing it
Currently seeing this while in a file on GitHub Codespaces, in the following form:
Can you please try insiders and see if you are still seeing this?
I still saw this issue when opening on: Version: 1.80.1 (user setup) Commit: Date: 2023-07-12T17:22:07.651Z Electron: 22.3.14 ElectronBuildId: Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.
As I mentioned, this was in GitHub Codespaces. I can't change the version of VS Code they serve to the browser.
There should be an action Switch to Insiders... in the settings gear icon in the bottom left corner, do you have that?
uninstalled installed all extensions, including- C# v2.0.328, autopep8 -for python, ctrl+shift+p - selected -format this document with - seleceted C#- All things worked again.

Discussion:
) { super(); <ins> this.registerSchemas({ defaultSettingsSchema: {}, userSettingsSchema: {}, profileSettingsSchema: {}, machineSettingsSchema: {}, workspaceSettingsSchema: {}, folderSettingsSchema: {}, configDefaultsSchema: {}, }); </ins> extensionService.whenInstalledExtensionsRegistered().then(() => { this.registerConfigurationSchemas();

} private registerConfigurationSchemas(): void { <del> const jsonRegistry = Registry.as<IJSONContributionRegistry>(JSONExtensions.JSONContribution); </del> const allSettingsSchema: IJSONSchema = { properties: allSettings.properties, patternProperties: allSettings.patternProperties,

allowComments: true }; <del> jsonRegistry.registerSchema(defaultSettingsSchemaId, { </del> <ins> const defaultSettingsSchema = { </ins> properties: Object.keys(allSettings.properties).reduce<IJSONSchemaMap>((result, key) => { result[key] = Object.assign({ deprecationMessage: undefined }, allSettings.properties[key]); return result;

additionalProperties: true, allowTrailingCommas: true, allowComments: true <del> }); jsonRegistry.registerSchema(userSettingsSchemaId, userSettingsSchema); jsonRegistry.registerSchema(profileSettingsSchemaId, profileSettingsSchema); jsonRegistry.registerSchema(machineSettingsSchemaId, machineSettingsSchema); </del> <ins> }; </ins> <del> if (WorkbenchState.WORKSPACE === this.workspaceContextService.getWorkbenchState()) { const folderSettingsSchema: IJSONSchema = { </del> <ins> const folderSettingsSchema: IJSONSchema = WorkbenchState.WORKSPACE === this.workspaceContextService.getWorkbenchState() ? { </ins> properties: Object.assign({}, this.checkAndFilterPropertiesRequiringTrust(machineOverridableSettings.properties), this.checkAndFilterPropertiesRequiringTrust(resourceSettings.properties)

additionalProperties: true, allowTrailingCommas: true, allowComments: true <del> }; jsonRegistry.registerSchema(workspaceSettingsSchemaId, workspaceSettingsSchema); jsonRegistry.registerSchema(folderSettingsSchemaId, folderSettingsSchema); } else { jsonRegistry.registerSchema(workspaceSettingsSchemaId, workspaceSettingsSchema); jsonRegistry.registerSchema(folderSettingsSchemaId, workspaceSettingsSchema); } </del> <ins> } : workspaceSettingsSchema; </ins> <del> jsonRegistry.registerSchema(configurationDefaultsSchemaId, { </del> <ins> const configDefaultsSchema: IJSONSchema = { </ins> type: 'object', description: localize('configurationDefaults.description', 'Contribute defaults for configurations'), properties: Object.assign({},

} }, additionalProperties: false <ins> }; this.registerSchemas({ defaultSettingsSchema, userSettingsSchema, profileSettingsSchema, machineSettingsSchema, workspaceSettingsSchema, folderSettingsSchema, configDefaultsSchema, </ins> }); } <ins> private registerSchemas(schemas: { defaultSettingsSchema: IJSONSchema; userSettingsSchema: IJSONSchema; profileSettingsSchema: IJSONSchema; machineSettingsSchema: IJSONSchema; workspaceSettingsSchema: IJSONSchema; folderSettingsSchema: IJSONSchema; configDefaultsSchema: IJSONSchema; }): void { const jsonRegistry = Registry.as<IJSONContributionRegistry>(JSONExtensions.JSONContribution); jsonRegistry.registerSchema(defaultSettingsSchemaId, schemas.defaultSettingsSchema); jsonRegistry.registerSchema(userSettingsSchemaId, schemas.userSettingsSchema); jsonRegistry.registerSchema(profileSettingsSchemaId, schemas.profileSettingsSchema); jsonRegistry.registerSchema(machineSettingsSchemaId, schemas.machineSettingsSchema); jsonRegistry.registerSchema(workspaceSettingsSchemaId, schemas.workspaceSettingsSchema); jsonRegistry.registerSchema(folderSettingsSchemaId, schemas.folderSettingsSchema); jsonRegistry.registerSchema(configurationDefaultsSchemaId, schemas.configDefaultsSchema); } </ins> private checkAndFilterPropertiesRequiringTrust(properties: IStringDictionary<IConfigurationPropertySchema>): IStringDictionary<IConfigurationPropertySchema> { if (this.workspaceTrustManagementService.isWorkspaceTrusted()) { return properties;