Design 47 H: H-A-311, a placing cut by a concurrent write is done again; a late progress still places; a stalled pipeline is unhealthy

This commit is contained in:
2026-11-21 20:36:57 +01:00
parent 30fcc6f9af
commit 336b9024b8
@@ -1847,3 +1847,13 @@ Where two preparers disagreed, the chosen one is named.
allowances per node; the interface name's form; "no interface" rendered as one negated match on the private
network's interface; disallow all or nothing; input path only; the rule comment "allowance <key>"; the holder says
allowances-changed with change started at every start; allowed bound to 10 s). P7, design-it-as-it-should-be.
- **H-A-311 (a placing cut by a concurrent write is done again; a late progress still places; a pipeline with nothing
open and nothing placed is unhealthy, 20:36)** Met twice: the catalog repository's 36-mover pipeline stood seventeen
minutes with eleven steps placed because its placing was cut at 20:15:59 ("written meanwhile, so nothing is placed
in it now") and never done again, the last test's progress was dropped as late without placing what followed, and
the runner's health said healthy; a restart's start pass placed 392 steps in twenty seconds. Fixed in the runner
now: (1) a placing refused because the pipeline was written meanwhile is done again at once from the record as
re-read, until it lands or the pipeline ends; (2) a step-progress or step-end that arrives late still places what
the step's end unlocks, even when it moves nothing of its own; (3) the runner's health names a running pipeline
that has had nothing open and nothing newly placed for five minutes, and the journal says it. P3, P-failure-loud,
nothing-moved-in-five-minutes, H-A-286, H-A-288.