-
Notifications
You must be signed in to change notification settings - Fork 429
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugsshIssue in vscode-remote SSHIssue in vscode-remote SSHupstreamIssue identified as 'upstream' component related (exists outside of VS Code Remote)Issue identified as 'upstream' component related (exists outside of VS Code Remote)verifiedVerification succeededVerification succeeded
Milestone
Description
- VSCode Version: 1.35.0
- Local OS Version:Ubuntu 18.04.2 LTS
- Remote OS Version:Ubuntu 18.04.2 LTS
- Remote Extension/Connection Type: SSH
Steps to Reproduce:
- Add to your
.ssh/config(from https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Proxies_and_Jump_Hosts):
Host *+*
ProxyCommand ssh $(echo %h | sed 's/+[^+]*$//;s/\([^+%%]*\)%%\([^+]*\)$/\2 -l \1/;s/:/ -p /') nc $(echo %h | sed 's/^.*+//;/:/!s/$/ %p/;s/:/ /')
- Reload the Connections list and connect to one of the hosts listed elsewhere in your config
- Observe the "Checking ... is reachable" notification, but beyond that nothing happens. No error message either.
- Change the plus sign to "foo". Reload, connect, observe it succeeds
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: No
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugsshIssue in vscode-remote SSHIssue in vscode-remote SSHupstreamIssue identified as 'upstream' component related (exists outside of VS Code Remote)Issue identified as 'upstream' component related (exists outside of VS Code Remote)verifiedVerification succeededVerification succeeded