Repository navigation
Cover channel creation during connection restoration - #718
Merged
Merged
Conversation
|
coverage: 92.723%. remained the same — test/channels-created-during-reconnect into master |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add regression coverage for channels created while a connection is restoring its existing channels. Concurrent channel registration must not invalidate the restoration iterator, and newly created channels must remain usable and participate in subsequent reconnects.
The runtime fix for #589 was already introduced by Daniele Varrazzo in cf10462 and released in 9.3.1. This adds coverage for that behavior without changing runtime code.
Closes #589.