Reconnect improvements, avoid ClientDisconnectedError in _onPing #79
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
Closed
|
Hey @FZambia 👋 Do we know when this may be merged & released? Thanks! |
|
@TomBeckett just released v0.9.4 - I suggest spending a bit more time than usual testing centrifuge-dart behaviour before moving to prod, hopefully it will work fine and exceptions go away. |
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.
This should generally improve reconnect process by only scheduling reconnect routine in onDone handler of the transport. Thus reducing a chance of leaking connections. Also addresses #76 – no exception should be raised when pong message can't be written to closed transport.