Unable to write to Folder Settings because no resource is provided. #3873

caochuansong · 2021-07-29T11:35:39Z

Web Browser: chrome
Local OS: macos
Remote OS: centos
Remote Architecture:
code-server --version: 3.11

every time I refresh web page, I got this error:
Unable to write to Folder Settings because no resource is provided.

how to config it?

Steps to reproduce

install code-server 3.11
code-server --auth none
open in browser
see error toast notification

Expected

No error

Actual

Screen.Recording.2021-07-30.at.10.49.08.AM.mov

The text was updated successfully, but these errors were encountered:

jsjoeio · 2021-07-29T22:02:21Z

Thanks for filing! I think we need to investigate this.

I noticed this happening in 3.11 - I wonder if something changed in VS Code upstream that we forgot to change. Any ideas @oxy @code-asher ?

code-asher · 2021-07-30T16:17:43Z

I can't think of anything off the top of my head. What are the full reproduction steps?

jsjoeio · 2021-07-30T17:51:07Z

Updated description with repro steps!

code-asher · 2021-08-02T19:05:50Z

Oh you were able to reproduce like that? Odd, it didn't reproduce for me. This couldn't somehow be related to the local OS being MacOS could it? Seems unlikely.

jsjoeio · 2021-08-02T19:11:28Z

Hmm...could question. Here is the stack trace:

ERR Unable to write to Folder Settings because no resource is provided.: Error: Unable to write to Folder Settings because no resource is provided.
    at b.reject (http://localhost:8080/static/4e8cd09ef0412dfc7b148b7639a692e20e4fd6dd/usr/local/Cellar/code-server/3.11.0/libexec/lib/vscode/out/vs/workbench/workbench.web.api.js:2403:15316)
    at b.resolveAndValidate (http://localhost:8080/static/4e8cd09ef0412dfc7b148b7639a692e20e4fd6dd/usr/local/Cellar/code-server/3.11.0/libexec/lib/vscode/out/vs/workbench/workbench.web.api.js:2403:19500)
    at b.doWriteConfiguration (http://localhost:8080/static/4e8cd09ef0412dfc7b148b7639a692e20e4fd6dd/usr/local/Cellar/code-server/3.11.0/libexec/lib/vscode/out/vs/workbench/workbench.web.api.js:2403:12506)
    at Object.factory (http://localhost:8080/static/4e8cd09ef0412dfc7b148b7639a692e20e4fd6dd/usr/local/Cellar/code-server/3.11.0/libexec/lib/vscode/out/vs/workbench/workbench.web.api.js:2403:12282)
    at y.consume (http://localhost:8080/static/4e8cd09ef0412dfc7b148b7639a692e20e4fd6dd/usr/local/Cellar/code-server/3.11.0/libexec/lib/vscode/out/vs/workbench/workbench.web.api.js:68:15342)
    at http://localhost:8080/static/4e8cd09ef0412dfc7b148b7639a692e20e4fd6dd/usr/local/Cellar/code-server/3.11.0/libexec/lib/vscode/out/vs/workbench/workbench.web.api.js:68:15157
    at new Promise (<anonymous>)
    at y.queue (http://localhost:8080/static/4e8cd09ef0412dfc7b148b7639a692e20e4fd6dd/usr/local/Cellar/code-server/3.11.0/libexec/lib/vscode/out/vs/workbench/workbench.web.api.js:68:15081)
    at b.writeConfiguration (http://localhost:8080/static/4e8cd09ef0412dfc7b148b7639a692e20e4fd6dd/usr/local/Cellar/code-server/3.11.0/libexec/lib/vscode/out/vs/workbench/workbench.web.api.js:2403:12267)
    at y.writeConfigurationValue (http://localhost:8080/static/4e8cd09ef0412dfc7b148b7639a692e20e4fd6dd/usr/local/Cellar/code-server/3.11.0/libexec/lib/vscode/out/vs/workbench/workbench.web.api.js:2403:41475)

Maybe something changed with how the configuration is stored locally on macOS?

wjziv · 2021-08-03T22:09:31Z

Chiming in to say I have the same experience every time I refresh the IDE window on a different OS.
Code-Server is hosted in a container by Unraid.

Web Browser: chrome
Local OS: chromeOS
Remote OS: Unraid
Remote Architecture: docker
code-server --version: 3.11

aryasenna · 2021-08-08T14:10:51Z

So.. This is not only limited to local OS being Mac OS or Chrome only, Windows is also affected.

Web Browser: Edge
Local OS: Windows 10
Remote OS: ubuntu 20.04
Remote Architecture: AMD64
code-server --version: 3.11

jason-weiser · 2021-08-09T21:23:57Z

Also chiming in to say that this happens to me as well.

Web Browser: Firefox 90.0.2
Local OS: MacOS 11.4
Remote OS: Ubuntu 20.04.2
Remote Architecture: used the install script?
Code-server version: 3.11.1

jsjoeio · 2021-08-10T18:30:31Z

Thanks all for the notes! I've added this to the next upcoming milestone so we'll work on it soon.

caochuansong · 2021-08-11T01:53:28Z

thanks @jsjoeio

jsjoeio · 2021-09-02T18:17:44Z

I'm starting to work on this and taking notes here. I'll update this message as I go so I'm not spamming the issue with new comments each update.

Notes

searching for "Unable to write to Folder Settings because no resource is provided" reveals lib/vscode/src/vs/workbench/services/configuration/common/configurationEditingService.ts which has a private method called toErrorMessage and a switch statement to handle each error case.

It looks like this is the key block where VS Code rejects and with this ConfigurationEditingErrorCode.ERROR_INVALID_FOLDER_CONFIGURATION error.

if (!(configurationProperties[operation.key].scope === ConfigurationScope.RESOURCE || configurationProperties[operation.key].scope === ConfigurationScope.LANGUAGE_OVERRIDABLE)) {
	return this.reject(ConfigurationEditingErrorCode.ERROR_INVALID_FOLDER_CONFIGURATION, target, operation);
}

Pulling that apart, it's an if statement with a single condition check consisting of two checks.
configurationProperties[operation.key].scope === ConfigurationScope.RESOURCE and configurationProperties[operation.key].scope === ConfigurationScope.LANGUAGE_OVERRIDABLE.

If either of those evaluate to false then this check fails, causing the rejection with the error.

Time to investigate ConfigurationScope.RESOURCE and ConfigurationScope.LANGUAGE_OVERRIDABLE.

Both belong to the same object: ConfigurationScope.

This value is imported into the file from vs/platform/configuration/common/configurationRegistry.

Looking at lib/vscode/src/vs/platform/configuration/common/configurationRegistry.ts, we see ConfigurationScope is an enum. Here's what it tells us:

/**
* Resource specific configuration, which can be configured in the user, workspace or folder settings.
*/
RESOURCE,
/**
* Resource specific configuration that can be configured in language specific settings
*/
LANGUAGE_OVERRIDABLE,

So now the question is, where are these resource configuration set? I'm going to search fo LANGUAGE_OVERRIDABLE since I imagine that is less common of a search term and will be easier to find.

It appears in lib/vscode/src/vs/platform/configuration/common/configurationRegistry.ts there is a class which has a private method called updateSchema to set this property.

Hmm...looking around, nothing specific stands out. Let's move on to RESOURCE

Hmm...still unsure where this could be happening. My guess is VS Code starts up and expects a RESOURCE when registering the configuration. I know in lib/vscode/src/vs/server/server.ts there is a configurationService created. My hunch would be to look there.

I think it makes sense run code-server locally with either the debugger or some console.log statements near the error to continue troubleshooting.

This is strange. I put a console.log on L508 in configurationEditingService but I'm not seeing it logged to the browser or the server 🤔 I think the error is happening elsewhere.

Let's follow the stack trace up:

at `ConfigurationEditingService.reject`

so the service calls the reject method which returns Promise.reject with a new message.

at `ConfigurationEditingService.resolveAndValidate`

adding a console log here to see if we see it. (we do)

going to see if I can use the debugger.

nope, debugger didn't work.

Okay following the stack trace, looks like we are here:

if (!operation.resource) {
			return this.reject(ConfigurationEditingErrorCode.ERROR_INVALID_FOLDER_TARGET, target, operation);
		}

This means operation.resouce is the culprit 🤔

After logging it, it looks like it's related to "jupyter.notebook.ipynb". I wonder if this error has to do with the Jupyter extension?

see if error appears with extension uninstalled

nope, even with extension uninstalled, it still happens.

next step will be to continue up the stack trace until we get to the root of the error.

I feel like I'm hitting a dead-end. Not sure but I found this in the Settings. I wonder if I remove if it will go away.

*.ipynb jupyter.notebook.ipynb

Previously:

    "workbench.editorAssociations": [

      {
        "viewType": "jupyter.notebook.ipynb",
        "filenamePattern": "*.ipynb"
      }
    ],

Wait a second...that made it go away? (I'm no longer seeing the error)

- "workbench.editorAssociations": [
-    {
-       "viewType": "jupyter.notebook.ipynb",
-       "filenamePattern": "*.ipynb"
-     }
- ],
+ "workbench.editorAssociations": {
+    "*.ipynb": "jupyter.notebook.ipynb"
+ },

Yup, adding it back causes the error toast. I think that's the culprit.

jsjoeio · 2021-09-02T22:21:48Z

@caochuansong @djasonweiser @aryasenna @wjziv can one of you confirm that this fixes it?

Solution

Open Command Palette
Open "Preferences: Open Settings (JSON)
Look for "workbench.editorAssociations"
Change it to this:

"workbench.editorAssociations": {
    "*.ipynb": "jupyter.notebook.ipynb"
},

And let me know if that fixes it?

wjziv · 2021-09-03T00:16:38Z

@jsjoeio
This appears to resolve the notification! I haven't seen it come back in existing directories. 🎉

I noticed at the same time as I the "Unable to write..." notification, when I navigated to subdirectories which did not exist, behavior changed from: "automatically create the subdirectory" to the familiar message "Unable to write to folder settings..."

Now I get the following response:

Unable to open 'new_subdir': Unable to read file 'vscode-remote://code.domain.com/config/workspace/dir/new_subdir' (Error: Unable to resolve non-existing file 'vscode-remote://code.domain.com/config/workspace/dir/new_subdir').

And it asks if I'd like to create the directory.

Sounds like a much better behavior, IMO!

However, there still exists a semi-related error on my end where Jupyter Notebooks aren't rendering... See #3874

GirlBossRush · 2021-09-03T00:25:25Z

@jsjoeio that's some incredible detective work. Incredible 👏🏻

jsjoeio · 2021-09-03T17:56:35Z

This appears to resolve the notification! I haven't seen it come back in existing directories. 🎉

Hooray! Thank you for confirming!

Unable to open 'new_subdir': Unable to read file 'vscode-remote://code.domain.com/config/workspace/dir/new_subdir' (Error: Unable to resolve non-existing file 'vscode-remote://code.domain.com/config/workspace/dir/new_subdir').

Weird...Well if you can easily reproduce, will you open an issue and I'll take a look?

However, there still exists a semi-related error on my end where Jupyter Notebooks aren't rendering... See #3874

Yeah, that's next on my list!

Going to close this for now!

rebelliousconformist · 2021-12-15T13:43:56Z

Reopening this isssue.
Unable to open 'selfpractice': Unable to resolve resource vscode-remote://wsl%2Bubuntu-20.04/home/bapatnext/nac_dev/selfpractice.

Unable to write to Folder Settings because no resource is provided.

getting the same problems again

vscode server is VS Code Server for x64 (7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e)

vscode version is

1.63.0 7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e x64

jsjoeio · 2021-12-15T17:02:30Z

@rebelliousconformist can you please open a new bug report with repro steps? Thank you!

jsjoeio added the needs-investigation This issue needs to be further investigated label Jul 29, 2021

jsjoeio added bug Something isn't working and removed needs-investigation This issue needs to be further investigated labels Aug 10, 2021

jsjoeio added this to the 3.12.0 milestone Aug 10, 2021

jsjoeio self-assigned this Aug 12, 2021

jsjoeio mentioned this issue Sep 2, 2021

fix: add resource for folder settings #4093

Closed

jsjoeio mentioned this issue Sep 2, 2021

Terminal text all black in Chrome only #4090

Closed

jsjoeio closed this as completed Sep 3, 2021

coder locked as resolved and limited conversation to collaborators Dec 15, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unable to write to Folder Settings because no resource is provided. #3873

Unable to write to Folder Settings because no resource is provided. #3873

caochuansong commented Jul 29, 2021 •

edited by jsjoeio

Loading

jsjoeio commented Jul 29, 2021

code-asher commented Jul 30, 2021 via email

jsjoeio commented Jul 30, 2021

code-asher commented Aug 2, 2021 via email

jsjoeio commented Aug 2, 2021

wjziv commented Aug 3, 2021

aryasenna commented Aug 8, 2021

jason-weiser commented Aug 9, 2021

jsjoeio commented Aug 10, 2021

caochuansong commented Aug 11, 2021

jsjoeio commented Sep 2, 2021 •

edited

Loading

jsjoeio commented Sep 2, 2021

wjziv commented Sep 3, 2021 •

edited

Loading

GirlBossRush commented Sep 3, 2021

jsjoeio commented Sep 3, 2021 •

edited

Loading

rebelliousconformist commented Dec 15, 2021

jsjoeio commented Dec 15, 2021

Unable to write to Folder Settings because no resource is provided. #3873

Unable to write to Folder Settings because no resource is provided. #3873

Comments

caochuansong commented Jul 29, 2021 • edited by jsjoeio Loading

Steps to reproduce

Expected

Actual

jsjoeio commented Jul 29, 2021

code-asher commented Jul 30, 2021 via email

jsjoeio commented Jul 30, 2021

code-asher commented Aug 2, 2021 via email

jsjoeio commented Aug 2, 2021

wjziv commented Aug 3, 2021

aryasenna commented Aug 8, 2021

jason-weiser commented Aug 9, 2021

jsjoeio commented Aug 10, 2021

caochuansong commented Aug 11, 2021

jsjoeio commented Sep 2, 2021 • edited Loading

Notes

at ConfigurationEditingService.reject

at ConfigurationEditingService.resolveAndValidate

jsjoeio commented Sep 2, 2021

Solution

wjziv commented Sep 3, 2021 • edited Loading

GirlBossRush commented Sep 3, 2021

jsjoeio commented Sep 3, 2021 • edited Loading

rebelliousconformist commented Dec 15, 2021

jsjoeio commented Dec 15, 2021

caochuansong commented Jul 29, 2021 •

edited by jsjoeio

Loading

jsjoeio commented Sep 2, 2021 •

edited

Loading

at `ConfigurationEditingService.reject`

at `ConfigurationEditingService.resolveAndValidate`

wjziv commented Sep 3, 2021 •

edited

Loading

jsjoeio commented Sep 3, 2021 •

edited

Loading