Skip to content

store: do not clear leftover hop-dump on the next resolve batch - #318

Merged
reardencode merged 1 commit into
masterfrom
store/leftover-diag-clear
Sep 3, 2026
Merged

store: do not clear leftover hop-dump on the next resolve batch#318
reardencode merged 1 commit into
masterfrom
store/leftover-diag-clear

Conversation

@rearden-grok

@rearden-grok rearden-grok Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Why

Master ci / test after #316 failed on archive::tests::leftover_miss_dumps_probe_diag (leftover miss must hop-dump once).

clear_leftover_miss runs at the start of every TipOnly/leftover get_fk_by_txid_batch. It also wiped LAST_PROBE_DIAG. Parallel tests then saw leftover_probe_diag_ready() == false after a real leftover dump. The operator reject line (diag=1) could lose the same dump.

Fix

  • Miss classification stays per-batch.
  • Hop-dump is consumed only by take_leftover_probe_diag.
  • Tests pin this parent via a short recorded-txid ring (not a process-wide ready flag).

Does not merge #317 (IBD tick cadence).

clear_leftover_miss ran at the start of every TipOnly/leftover resolve
and wiped LAST_PROBE_DIAG. Parallel cargo test then failed
leftover_miss_dumps_probe_diag (ready flag already gone). The operator
reject line could also lose diag=1. Miss classification stays per-batch;
the hop-dump is consumed by take() only. Pin this parent via a short
recorded-txid ring so the query test does not depend on a process flag.
@reardencode
reardencode merged commit 9708844 into master Sep 3, 2026
13 checks passed
@rearden-grok
rearden-grok Bot deleted the store/leftover-diag-clear branch September 4, 2026 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant