backlog: file #1290 and #1291 -- a required CI leg flaking on main, and a latent NULL unroll - #449
Merged
Merged
Conversation
…ed Windows runners A required status check is intermittently red on main. CI run 32255231838 at de896e0 failed `test (windows-2022, py3.14)` on test_subtree_re_resolution_picks_up_a_late_spawned_child: the process-table walk returned None on all 6 attempts in 30s. The identical leg passed on PR #448 in the same hour on the same runner image, and neither branch touches the probe, so the nondeterminism is measured rather than assumed. The assertion that fires is the one the test's author separated out as an environment problem, so the re-resolution assertion below it never runs -- the test is silent on the defect it exists to catch exactly when this fires. Filed distinct from #1014 (a fixed port-block collision in the smoke test) and #1210 arm 2 (FD/RSS provenance in the same probe). parse_items before/after: 306/226 open -> 307/227 open, the expected +1/+1/0 for filing one item.
Measured in pwsh 7 via AST extraction: missing-file and zero-tool both return NULL; one tool returns a bare String, so .Contains() answers True on a substring of it. Filed as a LATENT trap, not a live defect. The single caller wraps in @(...), so shipped behaviour is correct today and a present-tense bug claim would be false. Recorded that way deliberately. Two details that decide how it gets fixed and tested: the missing-file early return unrolls the same as the tail, and that path is the normal one on a box where the gate was never installed; and a test through -Status cannot discriminate fixed from unfixed because the caller re-wraps, so the test must reach the function by AST extraction -- install-gate.ps1 cannot be dot-sourced without performing a machine-global install. parse_items 307/227 open -> 308/228 open, the expected +1/+1/0.
Re-running the failed job alone on PR #447 head 4ccbf81, with no code change, returned completed/success. Identical commit, identical leg, opposite outcome, which settles nondeterminism more directly than the cross-branch pair the item was filed on. Bounded deliberately: it establishes that the failure is not a property of the tree under test, and establishes nothing about frequency or the runner load that triggers it, which is what sizing a fix actually needs. parse_items unchanged at 308/228 open, the expected 0/0/0 for amending a body.
wshallwshall
enabled auto-merge (squash)
August 19, 2026 13:42
…erved at intake The assertion names a CONFIRMED send that engine_read did not see. The harness already excludes the benign case in the same message (a send with no ACK before close is explicitly not counted as loss), so the remaining branch is either a harness reconciliation race or a count-and-log invariant failure. Filed because nobody has separated those two, and they have very different severities. Calling it a flake picks the comfortable branch without evidence. Red on main (run 32255231838, windows-2022) and on PR 448's rebased head (run 32259244062, ubuntu-latest), with different record shapes -- two platforms, two branches, which is evidence against a single fixed off-by-one. It already carries flaky(reruns=2) and failed anyway, so it exhausted its retries. Kept distinct from #1014 (port-block collision, same file) and #1290 (CPU-probe walk timeout, same suite). Two of the three sit inside required contexts, which is why the queue keeps stalling. Severity written in the conditional per CLAUDE.md section 0: zero instances, so nothing is affected today. P1 rests on the branch not yet ruled out. parse_items 308/228 -> 309/229, the expected +1/+1/0.
owns() (ledger_check.py:219-231) compares the current worktree path to the one recorded at allocation, with no fallback when that directory is gone. Ownership is non-transferable, so an orphaned number can never be satisfied again. PR #397 is stranded by this now: #1264 was allocated by a worktree that no longer exists, is not on main, and #397's only conflict is docs/BACKLOG.md. Resolving re-introduces a heading absent from main, which counts as an addition, so ownership is consulted and refuses -- for everyone, permanently. The gate is failing closed and is correct. The defect is that there is no route back, and that the refusal only arrives after the resolution work is done. Records three candidate routes without picking one, and notes the fix must not be "widen the gate" -- the --ci leg already skips ownership by design. Also records the operational sweep that falls out: before removing a worktree, check whether it owns an allocation not yet on main. Run against the 16 worktrees proposed for removal today; returned zero, with #1264 as the positive control proving the sweep can detect the class. The first draft named a worktree slug and the forbidden-content gate refused it. Rewritten generically rather than allowlisted, per the rule that a refused slug is the gate working.
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.
Two ledger items filed from the merge queue, plus one amendment. Docs-only:
docs/BACKLOG.md.#1290 -- the connscale CPU-probe walk times out on hosted Windows runners
test (windows-2022, py3.14)is a REQUIRED context and it failed onmainatde896e0f(CI run 32255231838), on
test_connscale_cpu_probe.py::test_subtree_re_resolution_picks_up_a_late_spawned_child.The process-table walk returned
Noneon all 6 attempts inside 30s.Verified independently rather than relayed, and confirmed twice:
The second is the stronger one -- identical commit, opposite outcome -- so the failure is not a
property of the tree under test. The item states that bound explicitly and records that it
establishes nothing about frequency or the runner load that triggers it, which is what sizing
a fix actually needs.
The assertion that trips is
walked_ok, which the test's own comment deliberately separates fromthe re-resolution regression. So while this is red the test is not merely failing, it is silent
on the defect it exists to catch -- the worse half.
Filed distinct from #1014 (a fixed 24-port block collision in the smoke test) and #1210 arm 2
(FD/RSS provenance in the same probe). Neither is a walk that never completes.
#1291 --
Get-HandledToolsunrolls to NULL on two pathsFiled as a latent trap, not a live defect, and worded that way on purpose: the single caller
wraps in
@(...), so shipped behaviour is correct today and a present-tense bug claim would befalse. The function is correct only by its caller's grace.
Measured via AST extraction: missing-file and zero-tool both yield NULL; one tool yields a bare
String, so.Contains('Edi')answers True on a substring of it.Two details that decide how it gets fixed and tested, both recorded: the missing-file early return
unrolls exactly as the tail does and is the normal path on a box where the gate was never
installed; and a test through
-Statuscannot discriminate fixed from unfixed, so it must reachthe function by AST extraction --
install-gate.ps1cannot be dot-sourced without performing amachine-global install.
Ledger control
parse_itemsrun before and after each edit:306/226to307/227to308/228, the expected+1/+1/0per filing, and0/0/0for the amendment. Both numbers allocated withalloc.ps1.