fix(ec2): give warning when OpenSSH client is outdated. #6018
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
| } | ||
|
|
||
| function parseSshVersion(output: string): string | undefined { | ||
| const match = output.match(/OpenSSH_(\d+)\.(\d+)/) |
There was a problem hiding this comment.
Instead of all this, could we we just triy to connect to the remote and surface any error messages (plus ssh version) on failure? We already do that for the "terminal" feature, right? So for vscode, we could do that as a pre-step, to really check that things are working.
An extra benefit is that this gives a much better experience if there is an ssh issue, compared to checking vscode-remote's ssh window.
There was a problem hiding this comment.
The error is coming from the connect script, i.e. the child process that launches the new instance of VSCode so I am not sure how to surface it. Especially since the child process is successfully opening VSCode, but then the newly opened VSCode instance throws an error. We would have to route that error back to this instance of VSCode somehow.
Problem
See #6015
Solution
Logs + Error:
(Ignore version number)
Notes
Believe test failures are unrelated as they are currently on master. pending fix.
License: I confirm that my contribution is made under the terms of the Apache 2.0 license.