This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
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.
Fix sending out of order
POSITION
over replication #16639Fix sending out of order
POSITION
over replication #16639Changes from 4 commits
dbc3d50
19f0a22
5ce8684
0d2ba21
bc01c8d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will_should_announce_positions
sets_should_announce_positions
to false, so we're essentially saying that we've now announced positions, don't do it again next time around the loop?Is it possible for another
REPLICATE
to come in after this? I guess that's fine, we'll just send them again next loop?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, pretty much.
We say we are about to send positions (to handle the race where something asks us to send out positions after we've just sent them out but before we clear the flag)