Rosetta: Short circuit recursive near tip #9802
Merged
Conversation
This file contains 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
Make sure the recursive query stops before going too far, and fallback to the historical query in that case with (min_recent_height-1)
bkase
added
the
ci-build-me
|
@bkase The old block queries rely on the chain status. For the new block queries, why not recurse until you see canonical status, instead of a fixed recursion length? |
psteckler
approved these changes
Nov 11, 2021
…/rosetta-quick-recursive
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.
Explain your changes:
to the historical query in that case with (min_recent_height-1)
Explain how you tested your changes: