-
Notifications
You must be signed in to change notification settings - Fork 217
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
Setting NODE_OPTIONS in remoteEnv irretrievably breaks Codespace ⚠️ #351
Comments
I assume this also affects the Dev Containers extension @chrmarti? Not sure if this is a CLI thing or Dev Containers/Codespaces. |
With Dev Containers the extension host crashes when adding One difference to Codespaces is that for Codespaces we pass Passing @edgonmsft To improve recovery, Codespaces could offer using a recovery container. I thought this is already implemented, but maybe this case isn't covered yet? |
Wouldn't it make sense to ensure that the crash doesn't happen? I believe that was what the original report was about - they went into a recovery container, but the reason why was not particularly clear. |
It would be interesting to figure out if there is a way to detect that we have this issue when connecting to the codespace or how to prevent it. |
We could remove |
I noticed that Codespaces now get a |
Discussed in https://github.com/orgs/devcontainers/discussions/14
Originally posted by davetapley December 29, 2022
I inadvertently added a
NODE_OPTIONS
toremoteEnv
instead ofcontainerEnv
, and it makes the Codespace irretrievably inaccessible as it get stuck in an infinite loop at "Setting up remote connection: Connecting to Codespace" (full output below).Luckily I could use the
Export Changes to a Branch
feature to get my changes out, but still not ideal.The text was updated successfully, but these errors were encountered: