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
Follow-up to #295 (#287, merged as de6e83b4), from the round-3 review of #295, finding 1. It did not block the merge.
recomputeMergedRouteMask combines five evidence terms. The fifth is the header bits of the loser's observations after they are re-parented onto the survivor. That term is still not pinned by a test.
Mutant N2. Move recomputeMergedRouteMaskabove the UPDATE OR IGNORE observations move, so the scan only sees the survivor's own rows. N2 survives the full cmd/ingestor suite.
Probe RZ1:
the survivor is computed FLOOD, with one FLOOD observation;
the loser has route_mask NULL and route_type FLOOD, with one surviving DIRECT observation, so the loser's observation header is the only DIRECT evidence.
Tree
Result
head
6
N2
2
master
2
N2 is not worse than master, but for this shape it silently rolls the fix back.
Acceptance
A test with the RZ1 shape, where the loser's re-parented observation header is the only evidence for a bit. It is red under N2 and green on master.
Activity
Merge pull request #328 from dborup/codex/issue-324-route-mask-fifth-…
dborup commentedon Oct 7, 2026
Fixed by #328 (merged as
9205f56e12e8171c95af04f45356e6d7a0031589).