-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
build: remove legacy server support #235232
base: main
Are you sure you want to change the base?
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Behavior moving forward
|
Thank you for your work on this. I appreciate your efforts to get this out early enough that we can build confidence in whatever workarounds we may choose to use. |
This Insiders build can't connect to any host, all with the same env as VSCode: 1.96.0-insiderVersion: 1.96.0-insider (Universal) Commit: 785c2b4 Date: 2024-12-04T09:42:59.065Z Electron: 32.2.6 ElectronBuildId: 10629634 Chromium: 128.0.6613.186 Node.js: 20.18.1 V8: 12.8.374.38-electron.0 OS: Darwin arm64 24.1.0
1.95.3 (Universal)Version: 1.95.3 (Universal) Commit: f1a4fb1 Date: 2024-11-13T14:50:04.152Z Electron: 32.2.1 ElectronBuildId: 10427718 Chromium: 128.0.6613.186 Node.js: 20.18.0 V8: 12.8.374.38-electron.0 OS: Darwin arm64 24.1.0there is no output, it just connects:
|
f9ac576
to
33f45d6
Compare
We are exploring an option for Remote SSH that allows providing a custom glibc path to the vscode server which could serve as a temporary workaround, this mode will be tagged as unsupported but provides a way to not disable vscode updates until your system can be transitioned. The flow would be as follows,
Here is a quick demo of the above, @murkvin and others please provide feedback if this helps your case. I will provide links to the builds once they are ready later today. Screen.Recording.2025-01-16.at.23.29.01.mov |
d205d43
to
0b72af9
Compare
9da9d68
to
05e3e50
Compare
Fixes #231623
DO NOT MERGE until March 2025