WebSocketsClientHandler: Fix no await for websocket.close #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
omer9564
reviewed
Aug 29, 2024
omer9564
approved these changes
Aug 29, 2024
roekatz
force-pushed
the
rk/fix-no-await-for-websocket-close
branch
from
10a2c53
to
91fb73c
Compare
roekatz
force-pushed
the
rk/fix-no-await-for-websocket-close
branch
from
91fb73c
to
81b76bd
Compare
I'm in holiday, but looking at the code, it seems fine by me 🙂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@antoinetran If you can take a look as well I'll highly appreciate it