fix: use the same sorting key for in memory impl of stacks chain tip #1282
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
Fix a difference between the in memory and pg implementation of
get_stacks_chain_tip
, follow up for the broken test after thefake
(non) bump in #1271.Changes
Bump
fake
and fix the in memory implementation ofget_stacks_chain_tip
to align it to the pg implementation, by changing the endianness of the stacks block hash used for tie breaking.Testing Information
The "broken" test now passes, and add two test to compare the get chain tip between the pg and in memory stores.
Checklist: