Code-server: settings.json in code server v3.6.2 and v3.6.1 is no longer populated.

Created on 4 Nov 2020  路  16Comments  路  Source: cdr/code-server

  • Web Browser: Chrome latest
  • Local OS: Mac latest
  • Remote OS: Linux
  • Remote Architecture: google cloud vm
  • code-server --version: 3.6.2 and 3.6.1

Recently upgraded to v3.6.2.

one thing seems a bit odd is that the settings.json was supposed to be populated under this directory: ~/.local/share/code-server/User if user has any vscode related settings change like a color theme.

the settings.json file was there in~/.local/share/code-server/User under v3.6.0
but the same settings.json can't be found in the same directory under v3.6.1 or v3.6.2

We are using the settings.json to control the default looking feel of the vscode, so this part is broken when upgrading to the latest.

bug

Most helpful comment

Will be in v3.7.3 which I'll get out today!

All 16 comments

discuss with @code-asher ,

it seems vscode starting to read/set settings.json by using browser storage instead of on a remote disk.

wondering if anyone come across the same situation that needs to set default view when cod-server starts for the first time.

I'm not aware of a way to do this but I think maybe what we do is patch VS Code to use the filesystem again. https://github.com/cdr/code-server/issues/2231#issuecomment-721900830

awesome, thanks for letting me know, will keep an eye on the release log in the future about this change.

Thank you. @code-asher you are amazing!

Thanks for your investigations, @code-asher.

I create customised Docker Images containing code-server and pre-populate ~/.local/share/code-server/User/settings.json. Using the filesystem again covers this use case, too.

Keep up the great work on code-server!

Any news on this? I'm using a custom path for user data directory and just read this https://github.com/cdr/code-server/issues/2231. Placing a pre-populated settings.json isn't working.

# Starting code-server using a custom user data path
code-server /home/demyx --user-data-dir=/home/demyx/.code/data

# Pre-populated settings.json
/home/demyx/.code/data/User/settings.json

Nothing yet; still working on the 1.51 VS Code update.

The settings.json local to code-server (~/.local/share/code-server/User/settings.json) still seem to work and can be accessed from "Open Remote Settings" inside vscode, but I believe the settings.json stored in the browser's local storage has priority and will override anything you set there.

Yeah looks like I'll have to update all my code-server repos and hardcode it to 3.6.0 until this is resolved.

I have a settings.json that I place into my container to restore my User-Settings and with 3.7.2 the problem still exist.

have to downgrade to 3.6.0

I can also confirm that the problem still exists with 3.7.2.

As a consequence, it's not possible, at all, to set a custom settings.json file that "persists" and that code-server picks it. 馃槥

Hello,

First of all, thank you for your work, is more than appreciated !
Do you have any news about this bug ?

I have a fix in a PR so hopefully we can make a new release soon.

Will be in v3.7.3 which I'll get out today!

@nhooyr Great stuff! Much appreciated!

Looking forward to test v3.7.3!

Thank you very much!

v3.7.3 works 馃憤

Was this page helpful?
0 / 5 - 0 ratings

Related issues

tecosaur picture tecosaur  路  3Comments

balazssoltesz picture balazssoltesz  路  3Comments

chrischabot picture chrischabot  路  3Comments

broady picture broady  路  3Comments

infogulch picture infogulch  路  3Comments