feat(scripts): add consolidated multi-chain sync progress bar#1210
Open
theguysaccount wants to merge 1 commit into
Open
feat(scripts): add consolidated multi-chain sync progress bar#1210theguysaccount wants to merge 1 commit into
theguysaccount wants to merge 1 commit into
Conversation
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.
Closes #1211
Summary
During
./start-node, the backing Bitcoin Core nodes (btc-node,tbtc-node,signet-node, …) emit oneUpdateTip … progress=log line per block during initial block download. The result is a multi-thousand-line firehose that buries the Gatekeeper/Keymaster/IPFS logs and makes it hard to see how far along a sync is.This adds
scripts/sync-progress.mjs, a zero-dependency Node filter that consumes the compose log stream and renders a single in-place display: one combined OVERALL bar plus a per-chain bar with height and block date.Usage
Only lines containing
progress=are consumed, so non-Bitcoin service logs are ignored.Notes
node:readline), no new dependencies, consistent with the existingscripts/btc-logs/scripts/signet-logshelpers.getblockchaininfo(verificationprogress) over RPC instead of scraping stdout — happy to follow up with that if maintainers prefer.Opening as a discussion-starter per CONTRIBUTING.md; glad to file a tracking issue and re-link if you'd like.