Design 47 H: section 10, finding 160

This commit is contained in:
2026-11-21 18:29:47 +01:00
parent 933ee50a41
commit 9e8bb7917d
@@ -676,3 +676,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
| The cause of row 156's held slot, read from the pipeline runner's code and the control-node's journal: the pipeline did judge its end at 17:45, but never wrote it; the runner computed every mover's widens inside the end's compare-and-set loop (126 movers, each asking the seat mesh-grants and cut after five seconds, about eleven minutes per try) while the pipeline's key kept changing under it, so every write was refused and the reads were made again (212 cuts between 17:45 and 18:05) until the restart, and the start pass judged no ends (rows 112 and 156); the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-289 (the reads an end needs are made once before the compare-and-set and shared by every mover and every retry; a retry reads only the key again), beside H-A-288's end pass at the start; in build in the runner. Owed: the five-second cut of the seat mesh-grants's answer itself (rows 69 and 115). | H1 |
| The tool runner's release 0.1.55 (queued at 17:47) waited more than forty minutes to publish, not lost but at the back of the builder's publish queue: a state bucket with one key per holder and version, worked one version at a time, oldest first, the whole bucket listed and read again before every send (about 1,900 subjects; the read tool timed out on it), and every start of the builder asks a publish again for every done build without a release, so old versions of many modules ride ahead of the ones a pipeline waits on; the second slow drain in the builder today (row 149 was the first) (rows 149, 152 and 155); the builder. Settled in H1 by H-A-290 (a publish a pipeline's step waits on goes before any asked again at a start; a withdrawn or taken-over build never publishes; one listing per pass and four sends at a time; a send that does not send says why; the read tool answers at any size), in build in the builder. Owed: the publish queue as a work-queue stream per holder, with tools to drop one item or put it first. | H1 (the five parts); H2 (the stream) |
| The fix of rows 156 and 157 (a pipeline with nothing open ends at once; an end's reads are made once; a journal line at every end) was approved at its first review round without findings and merged at 18:22 into a pipeline of its own; its hand pack goes onto the control-node at about 18:30, the pipeline runner's second hand pack of the evening, after the re-pin fix at 18:05. After the cancel of 18:08 the queue runs again: the next pipeline took the slot at 18:08 with 853 steps; the tool runner rides the eighth pipeline behind it, and its release of 17:47 still waits in the builder's publish queue (rows 156, 157 and 158); the pipeline runner (`mesh-delivery-pipeline`) and the runbook. | H1 |
| The fix that ends an empty pipeline (row 159) runs on the control-node since 18:26; its start pass found nothing to end, the cancelled pipeline having ended at 18:08; the evening's second pipeline runs since 18:08, with the tool runner's seven pipelines behind it. The builder's publish-queue change (row 158) was built with two gaps its developer named: at a start every old unreleased version still rode ahead of the live ones, and a live build waited for a whole start list. H-A-291 settles both (a start asks a publish again only for each module's newest reservation and retires the ones a newer reservation or release supersedes; a live enqueue makes the pass list again after its sends in flight), added before the review, together with a lock on two test fakes that failed the race detector on main (rows 158 and 159); the pipeline runner (`mesh-delivery-pipeline`) and the builder. | H1 |