fix: Add a slightly better error message for dropped SSH connection #3131
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If an SSH connection drops, we typically get an
ssh.ExitMissingError
from the client, which doesn't have a very user-friendly error message:wait: remote command exited without exit status or exit signal
This PR looks for that error type and replaces it with message that, while not necessarily more helpful, at least doesn't incorrectly state the problem is on the remote side:
SSH connection ended unexpectedly
Partial fix for #1369