fix: don't keep the startup finalized block pinned forever - #2266
Open
marian-radu wants to merge 2 commits into
Open
fix: don't keep the startup finalized block pinned forever#2266marian-radu wants to merge 2 commits into
marian-radu wants to merge 2 commits into
Conversation
marian-radu
commented
Jul 31, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
FollowStreamDriver's replay buffer holdsBlockRefs and entries only leave it when a laterFinalizedevent reports the block.At subscription start the node unconditionally reports the current best block. When best == finalized, always on instant-seal, a connect-time race otherwise, that block was finalized before we started watching, so no
Finalizedevent we receive ever reports it and the pin lasts for the life of the subscription, so the node can't prune state past that block.Fix
Keep only the latest
BestBlockChangedin the buffer. This behavior matches the node rather than diverging from it.Subscribers joining mid-stream now receive only the latest best-block event. Existing subscribers are unaffected.
Testing
startup_best_block_event_is_not_kept_alive_foreverasserts the replay buffer no longer references block 0 and that an unpin was issued for it.