-
Notifications
You must be signed in to change notification settings - Fork 712
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
silence abnormal websocket close #1768
Conversation
We get this when windows are closed, so really should treat it just like any other close.
NB: the m/t version remains unchanged since it is generally a lot noisier
since we don't log the start either
both occur in various states of disconnectedness
since we can get this when a pipe has been closed normally
if err := pipe.CopyToWebsocket(remote, conn); err != nil && !xfer.IsExpectedWSCloseError(err) { | ||
return false, err | ||
} | ||
return false, nil |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
LGTM |
Is this purely about logging, or did some signalling change too? |
Not intentionally. |
websocket.CloseAbnormalClose
since we get this when attach/exec windows are closedFixes #1202.