Skip to content
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

Merged
merged 8 commits into from
Aug 12, 2016
Merged

silence abnormal websocket close #1768

merged 8 commits into from
Aug 12, 2016

Conversation

rade
Copy link
Member

@rade rade commented Aug 7, 2016

  • silence websocket.CloseAbnormalClose since we get this when attach/exec windows are closed
  • reduce pipe log noise
  • improve some of the remaining pipe logging

Fixes #1202.

rade added 8 commits August 5, 2016 19:07
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.

This comment was marked as abuse.

This comment was marked as abuse.

@2opremio
Copy link
Contributor

2opremio commented Aug 8, 2016

LGTM

@davkal
Copy link
Contributor

davkal commented Aug 8, 2016

Is this purely about logging, or did some signalling change too?

@rade
Copy link
Member Author

rade commented Aug 8, 2016

did some signalling change too?

Not intentionally.

@rade rade merged commit 6334836 into master Aug 12, 2016
@rade rade deleted the 1202-silence-abnormal-close branch July 5, 2017 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Socket/websocket errors
4 participants