-
Notifications
You must be signed in to change notification settings - Fork 6k
nbin: Make extract location more robust #1287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm having this same behavior too. Not sure if it's related but I'm also unable to open a terminal, it's stuck at "Starting...". If that's something different I can open a separate issue. I see this in docker logs:
|
There seems to be a root requirement newly introduced by
|
@mirekphd Interesting, I got that too but figured it was something weird with my build process. That error goes away when I |
Ahh yeah we moved to XDG_CACHE_HOME because some hosts don't allow
execution from /tmp. Even without that requirement it seemed like the
more appropriate option. If you want to move it back you should be able to
set XDG_CACHE_HOME to /tmp.
Does the `NODE_MODULE_VERSION` error persist if you `rm -r
/home/code/.cache/nbin/`?
|
The most common permissions for /tmp are: Therefore I would reverse the default cache location, defaulting to /tmp as before (where majority have all rights by default) and alowing the "special needs" users to set a non-standard location within /home/coder (where UID and thus access rights can vary with every user on secure platforms such as Openshift). Not only for backward compatibility, but also for frequency of use - only minority cannot execute from /tmp folder, most users can. |
@code-asher I'll give that a try and let you know. Thanks for the tip |
Opened coder/nbin#40 to address this. |
See #1306 |
code-server
version: 2.1698-vsc1.41.1Description
When running VS Code, the "Open Folder" command produces the error
"Unable to open {folder}: Unable to read file (Error: File not found)..."
Version 2.1692-vsc1.39.2 works correctly.
Steps to Reproduce
Examples
Expected Behavior (2.1692-vsc1.39.2):
Current Behavior (2.1698-vsc1.41.1):
The text was updated successfully, but these errors were encountered: