VSR/Sync: Allow tables to queue for sync twice #1278
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.
Timeline of the VOPR seed in #1273 (seed
2812334640525749465
on commit47c03651ff08ee547b4baefda1b5b40f7f95e191
):address=62 checksum=145957321580082356891479597489273601427 level=0
for sync (GridBlocksMissing.enqueue_table()
).address=62
to level 1.address=62 checksum=145957321580082356891479597489273601427 level=1
for sync (GridBlocksMissing.enqueue_table()
).The
ForestTableIterator
doesn't repeat tables... except when the table in question has moved to the next level.This commit loosens the assertion to allow for this case.
Fixes #1273.