Rosetta, fix pending blocks balance query #9904
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.
Fix Rosetta balance queries when the given height is for a pending block.
Strategy:
RECURSIVE
query from the block of max height back to a canonical blockUNION
all canonical blocksJOIN
that entire chain on thebalances
tableFor the network status endpoint, use the latest block in the archive db to the get the "current block" height and state hash.
(Continue to use the GraphQL best tip for the sync status height.)
With these changes, rosetta-cli
check:data
on mainnet succeeds through all block in the archive db.Also: Change the
missing_blocks_auditor
to use individual bits for particular errors, rather than prime number factors, which was a crazy idea. Tested the app against the mainnet3
db.