Will investigate. Is this using the docker command?

Will investigate. Is this using the docker command?

Yes, I use docker command, and use -d option to specify data directory to a docker volumn. So when I rerun docker command, the old data will be used.

@kylecarbs should we modify the one-liner to also mount a data directory?

That's probably a good idea.

So in order to fix this, code-server needs to stop putting binaries into the data directory and reusing them as it'll screw with things on macOS for example. Best to use a temp dir or name the binaries with their OS and arch.

I have the same issue in

Distributor ID: Debian
Description:    Debian GNU/Linux 9.8 (stretch)
Release:        9.8
Codename:       stretch

With binary version:

server/0.0.0 linux-x64 node-v8.9.3
1.31.1-100

I use server without root permission.

@nhooyr the only binary we unpack is ripgrep. That shouldn't prevent any loads though.

There is some pty.node binary in .code-server.

Yes. My data folder is in /var/lib/vscode and pty.node is in /var/lib/vscode/dependencies.

It's probably best if we keep data in one place, and move temporary unpacked items to another folder. I suppose we could just keep them in <tmpdir>/code-server/

Hi,
I run the server with this code:

/opt/vscode/code-server -d /var/lib/vscode --cert=fullchain.pem --cert-key=privkey.pem development

Can you explain me what I have to change?

Same issue to me, extensions are disabled on restart and if i change folders they become disabled. the only way for me to re-enable is to uninstall / install again

Running on CentOS7, manual build with yarn.

Same here using docker build from Dockerfile.

I notice that when refreshing the browser, the file user-data-dir/CachedExtensions/user will be regenerated. However it cannot be generated correctly.

It is always like following:
{ "input": { "ourVersion": "1.32.0", "locale": "en", "devMode": false, "absoluteFolderPath": "/root/.local/share/.code-server/extensions", "isBuiltin": false, "isUnderDevelopment": false, "tanslations": {} }, "result": [] }

"result": [] is always empty, including no information of installed extensions. Normally it should contain all extensions information.

Again another file user-data-dir/globalStorage/stage.json is not properly generated in the same way.

For example, if the extension "Markdown All in One" is manually disabled, this file supposes to include the information whether a extension is disabled or not, like
"extensionsIdentifiers/disabled":"[{\"id\":\"yzhang.markdown-all-in-one\",\"uuid\":null}]"
However it is not in the file.

With this release 1.32.0-245 my issue is solved. Now the extensions are enabled also after restart.

@wwbmmm did release 1.32.0-245 fix the issue for you as well?

I can say based on my testing with #209 I have seen the issue still come up on CentOS 7 on the new release, it happened when i would use 'open folder' and then i would try to disable the extensions all together and then Enable (workspace), when I swap folders around my python extension was unable to work for me (I could not re-enable it).

Seeing this issue with the latest release (code-server1.696-vsc1.33.0-linux-x64 ). Any workaround for the issue?
Extension:

Name: Python
Id: ms-python.python
Version: 2019.3.6558
Publisher: ms-python

Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.5 LTS
Release:	16.04
Codename:	xenial

Seeing this without the docker and using just the binary.

Should be fixed with latest versions.