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.
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
Gracefully shutdown of the websocket client #213
Gracefully shutdown of the websocket client #213
Changes from all commits
b1d96eb
b40a598
43db955
90b9944
8dde9d9
598cf25
bbe2d3f
4c03472
84113b9
35ffed8
c6851ed
35c8b8d
998431d
25644c2
fb226bb
6e88dba
1446c8a
6ec846c
574baa6
d5c6e3a
eb60625
0c4dab0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 263 in client/wsclient.go
Codecov / codecov/patch
client/wsclient.go#L263
Check warning on line 290 in client/wsclient.go
Codecov / codecov/patch
client/wsclient.go#L290
Check warning on line 294 in client/wsclient.go
Codecov / codecov/patch
client/wsclient.go#L292-L294
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason we
break
here? If the sender stopping failed shouldn't we still try to stop the receiver and close the connection?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this
break
was introduced during the updates of the PR. The initial code does not wait for the receiver to stop, leaving the closing of the connection to the defer. I update the branch to close the conneciton explicitly and wait for the receiver to stop before break.