-
Notifications
You must be signed in to change notification settings - Fork 5.9k
[Bug]: (install.sh) Cannot install preferred version via yarn #4832
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 too am having a similar issue with the latest version and the 1006 error. It would be nice to get a solution that works with Apache to solve this issue. For now I'm deferring the update. |
What is the latest working version for you? I would like to stay as up-to-date as possible. |
I updated to 3.11.0, but it introduces an error of |
I've upgraded to 3.12.0 now, and I'm not seeing any issues. It would seem the next releases are 4.x, so I won't be upgrading any further for now. |
I took a look at our install script. It looks like it always defaults to latest, and doesn't use
Thanks for catching this! Apologies for the errors y'all. The team was 4 last year this time. Now I'm the only one full-time. Hoping I can get the 1006 error and others resolved so y'all can upgrade. In the meantime, thanks for the patience! |
Is there an existing issue for this?
OS/Web Information
code-server --version
: (not applicable)Steps to Reproduce
sh install.sh --version 3.11.1
Expected
Version 3.11.1 should be installed
Actual
The latest version is installed
Logs
yarn global add [email protected]
does not result in any errors.When installed via this method, the correct version is installed.
Screenshot/Video
Does this issue happen in VS Code?
Are you accessing code-server over HTTPS?
Notes
I am installing this version because I believe it is the version I had before upgrading. The latest version does not work for me, since it throws this error every time I open it:
"The workbench failed to connect to the server (Error: WebSocket close with status code 1006)"
I know that #4443 addresses this issue, but the solutions provided are only for nginx, and I use Apache.
The text was updated successfully, but these errors were encountered: