This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Wait peers to connect before doing anything else #7375
Merged
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.
There is a race condition in
NetworkBridgeRx
between registering incoming peers and handling overseer signals. While the peer connection was sent toNetworkBridgeRx
first, sometimes the peer would be added tovalidation/collation_peers
with enough delay that the bridge handled an overseer signal that was meant do send notifications to the registered peer and as the peer was not present in the bridge, the notification was never sent and the test would hang.When peers are registered to
NetworkBridgeRx
usingconnect_peer()
, wait until they show up inshared.validation/collation_peers
before doing anything else.Fixes #7367