db/state: log reorg-safe block and step in BuildFilesInBackground#21527
Draft
sudeepdino008 wants to merge 1 commit into
Draft
db/state: log reorg-safe block and step in BuildFilesInBackground#21527sudeepdino008 wants to merge 1 commit into
sudeepdino008 wants to merge 1 commit into
Conversation
Add reorgSafeBlock/reorgSafeStep (the highest block safe to freeze, tip minus reorg depth, and its fractional step) to the BuildFilesInBackground log for visibility into how far collation can advance relative to the chain tip.
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
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.
Change
Adds
reorgSafeBlock/reorgSafeStepto theBuildFilesInBackgroundlog line: the highest block safe to freeze (chain tip − reorg depth) and its fractional step. Gives visibility into how far state collation can advance relative to the chain tip.Diagnostic logging only; no behavior change.
Draft — full
make lintverification pending.