Use import-time is_new_best for newHeads notifications
#1781
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
Fixes a race condition where intermediate blocks during reorgs were not being notified to
eth_subscribe("newHeads")subscribers (issue reported on Moonbeam).The issue was that
MappingSyncWorkerdeterminedis_new_bestby queryingclient.info().best_hashat sync time, not at import time. During rapid reorgs, the best hash could change between import and sync, causing intermediate blocks to incorrectly haveis_new_best=falseand be filtered out byEthPubSub.Changes:
best_at_importHashSetto track blocks that wereis_new_bestat the time of theirBlockImportNotificationnotification.is_new_bestfrom import notifications