fix: ignore I/O error after close sent succesfully #115
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.
This PR fixes that after the close reason has been sent soketto is trying to close down the I/O stream but it's possible that it's already closed down by the other end when it receives the close message.
So, after this change the actual websocket close message is prioritized and the actual I/O close status is ignored because once the websocket close reason is sent to the other side then it's regarded as clean shutdown.
Behavior before this PR
Behavior after this PR