You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sync status logger only fired while the downloader was inside a bulk
historical sync. Once the node is caught up, new blocks are followed
through the block fetcher / BFT announcements, so Synchronising() stays
false and the warn log appeared only once or never over hours of normal
operation instead of every 10 minutes.
The logger now emits a status line on every 10-minute cycle with a
neutral message (current / highest / behind / peers). While the downloader
is actively synchronising it reports the downloader's discovered target
and the fast-sync snap block; otherwise it uses the local head merged
with a per-peer live high-water mark fed by block announcements
(NewBlockMsg / NewBlockHashesMsg). The announced numbers are only trusted
after passing the fetcher's plausibility window, exposed as
IsPlausibleAnnouncement, so a peer cannot inflate the reported gap.
0 commit comments