-
Notifications
You must be signed in to change notification settings - Fork 259
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
devcontainer build fails, VS Code Server SHA mismatch #9670
Comments
Can reproduced this, I think SHA need to be fixed ASAP. @jdhenry08 , or any one stuck with this issue can downgrade to the previous version: vscode-insiders@1.88.0-9ccb0fa738a2f7a1c5328800c9fe18f4dd5b4f8a since the server binary version are aligned with the vscode client version. |
Can reproduce as well. |
Getting same issue here:
|
"Me too":
Version: 1.88.0-insider (user setup) |
Same issue:
Version: 1.88.0-insider
Commit: 7c51753f7ce936a7aeb84ac881818c35c5a9ab8d
Date: 2024-03-19T05:50:42.450Z
Electron: 28.2.6
ElectronBuildId: 27476517
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Linux x64 6.7.9-1-default For now I downgraded to code-insiders-1.88.0-1710742424, where I don't get the issue.
|
This is fixed in the latest Insiders. Thanks! |
ssh remote can not work yet, after 2 ~ 3 versions. the last working version is |
This was only reported for Dev Containers, could you post your Remote-SSH log here from when this happens? |
SSH issue is unrelated to the SHA mismatch as the reporter mentions it is broken for past versions as well. @specter119 can you open a separate issue with relevant logs. |
Steps for verification:
|
how to solve it ? |
@AlexYangGitHub This looks like a different issue. I'll copy your report to a new issue to track it. Thanks. |
Attempting to rebuild a known working dev container fails and gives me the following error:
Does this issue occur when you try this locally?: No, it's specific to dev container startup
Does this issue occur when you try this locally and all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: