-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
fix: use legacy server as default with additional warnings #204377
Conversation
As @deepak1556 pointed out there are layering issues So it looks like the changes we did in common/remote.contribution.ts should be in @bpasero @alexdima @aeschli can you help with the layering warnings? Suggestions? We could just ignore for the recovery release.
|
I think the warning can be ignored if you are certain that the But I also think the contribution could be moved over to the |
Moved it to browser layer, thanks @bpasero |
src/vs/workbench/contrib/remote/browser/remoteConnectionHealth.ts
Outdated
Show resolved
Hide resolved
44cc6b1
to
4b53bfa
Compare
4b53bfa
to
7bcd639
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed and tested all the items and found no signs of any damage to the unit or anything else that may have occurred during the installation of the system or the unit itself and all other components of the system that were installed in the unit as needed for the job or any damage to the home or any other activity in the unit.🫶❤️
* ci: switch to glibc 2.17 remote server * chore: signal user about unsupported connection * chore: address review comments * chore: update nodejs build * chore: bump distro * chore: lower the minimum requirements * fix: glibc version check * chore: remove explicit connection disposal
…204482) * fix: use legacy server as default with additional warnings (#204377) * ci: switch to glibc 2.17 remote server * chore: signal user about unsupported connection * chore: address review comments * chore: update nodejs build * chore: bump distro * chore: lower the minimum requirements * fix: glibc version check * chore: remove explicit connection disposal * chore: update distro
Refs #204344
Depends on https://github.com/microsoft/vscode-node/pull/56