vscode-remote-release
vscode-remote-release copied to clipboard
Manual reconnect
Maybe this exists already, but if it does, it's non-obvious.
I would like a way to manually reconnect a remote ssh session. The UI brings up a reconnect box automatically. But sometimes you are not ready to reconnect. And the UI seems to give up on reconnecting pretty quickly. Then you are stuck with a dead workspace and need to reload the whole window.
I know, not a priority, but it would be fantastic if there was a one or two click way to trigger the reconnect logic.
Thank you.
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:
Similarly, it would be nice to disable automatic reconnect. And just block the editor and require that I hit enter
to reconnect.
If you are:
- Suspending the machine,
- Have 2FA like a yubikey to touch on reconnect,
- Have spotty internet in current spot.
It might be nice that it doesn't attempt to reconnect without my say so.
I figure control could just be an option.
Please fix this for daily suspenders.
@BernierCR just curious if the command: Developer: Reload Window
suffices for manual reconnect?
@tanhakabir I can't speak for BenierCR here, but in my experience Developer: Reload Window
does not always work 100% of the time. Sometimes yes, but often I've found it will just hang (I'm not entirely sure how to reproduce it deterministically. It may be related to switching between networks or interfaces).
My solution to this is generally to use Remote: Close Remote Connection
followed by Remote-SSH: Connect Current Window to Host...
, but this requires that I go dig up the hostname of my remote container again, which is a bit circuitous. Since my container (and as a result, its hostname) changes every few days, I never save them in my ssh config, so they don't show up in the suggested hosts list in the connect dialog either.
Adding to this, if you have unsaved files you have to abort the automatic reconnect otherwise you lose your files. Then the only way to save them is to either open an entirely new window and reconnect there, or copy-paste your files elsewhere and reload , then whichever path you chose you have copy them back, and then save.
Extremely unfriendly workflow
Remote vscode windows are not designed to operate in a disconnected state, so yes we force reconnection. You should not lose unsaved files, please open a separate issue with more details if that's still an issue