fix: avoid double conns, better state tracking#1505
Merged
Conversation
fe5d473 to
1ba1941
Compare
1ba1941 to
78263bb
Compare
divagant-martian
approved these changes
Sep 21, 2023
divagant-martian
left a comment
Contributor
There was a problem hiding this comment.
the only things that jump to me is doing explicit imports of std::result::Result if you are using anyhow::Result, setting the error will overwrite the generic so that's not necessary (if that's the reason)
dignifiedquire
approved these changes
Sep 21, 2023
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
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.
Description
On
mainthe testsync_full_basicis flakey. This PR (hopefully) fixes it.The reason was: We have the situation that two peers initiate connections to each other at (roughly) the same time. In #1491 this was sometimes prevented, but not reliably.
This PR fixes it by:
SyncState::Dialingfor the(namespace, peer)Dialingfor the incoming request for(namespace, peer)we compare our peer id with that of the incoming request, and abort if ours is higher (doesn't matter which way, we care about a predictable outcome onlyAbortframe to the wire protocol to transfer to inform the dialer about the reason of the declined request, which is either "we do double sync, and will take the other conn" (AlreadySyncing) or "this replica is not here" (NotAvailable)This PR also:
Notes & open questions
Change checklist