core: Log / UX improvements for node operators - #660
Closed
Jason-W123 wants to merge 4 commits into
Closed
Conversation
pmikolajczyk41
changed the title
pmikolajczyk41
previously approved these changes
Apr 24, 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
4 participants
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.
Summary
Log and error message improvements for node operator UX, companion to nitro#4607.
pulled in by OffchainLabs/nitro#4607
Changes
core/rawdb/database.go:databaseVersionnow shows "not set (new or uninitialized database)" instead of cryptic<nil>. Other nil metadata fields keep<nil>to avoid misleading diagnostic output.core/rawdb/chain_iterator.go: "Unindexing transactions" first log explains it is normal maintenance; subsequent periodic logs downgraded to DEBUG to avoid log spam (12+ hour runs previously flooded INFO).core/state/pruner/pruner.go: Updated comment from "around 2 hours for mainnet" to "several days for large databases (e.g. Arbitrum One)" to match observed user reports.