Design 47 H: section 10, finding 102

This commit is contained in:
2026-11-21 01:33:30 +01:00
parent 48c7e35bd1
commit 5d46e2f48b
@@ -618,3 +618,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
| The builder was restarted by hand while Go asks ran in the Go build module's runtime (`mesh-build-go`), whose step list showed none because it does not list the builder's own delivery asks (row 86); the asks survived the restart because the build module runs them, but the "no running step" check before a hand restart is blind to them; the build modules and the runbook. Owed: one tool across the build seats that lists every running ask, whoever asked it. | H2 |
| The watchman's entry still pinned no client that its same-repository `buildrun` module requires, because the watchman's go.mod names `buildrun` in a replace directive without a require line, and the reading of the module graph (H-A-201) followed require lines only; six test steps were refused "no pin" (rows 79 and 82); the indexer (`mesh-delivery-indexer`). Settled by H-A-224 (a same-repository module named only by a replace counts as required; its requirements are pinned transitively), in build in the indexer. | settled in H1 once delivered |
| The builder keeps one reservation per module and series and bumped its number on any new run of a build (a restart's re-run included), while the run already building carried the old number, so its publish was refused "has no version reserved or released"; and a take-over of the series by another fingerprint dropped the older reservation without stopping the older build, which then published a dropped number; the builder. Settled by H-A-225 (a reservation is kept for the same fingerprint until it is released; a taken-over build is withdrawn; a number never published is freed), in build in the builder. Also seen: after the builder's start it logged "no seat builds an artifact of language go and kind package" dozens of times a second (the journal suppressed over a thousand lines); cause under study. | settled in H1 once delivered |
| A restart of a node's tool runner (`node-tools`), to load one module's new tools bundle, silences the seat verbs of every module whose tools run inside it: the artifact registry seat answered "no responders" for about two minutes while the control-node's tool runner restarted, and the builder's publishes failed meanwhile; the tool runner and the builder. Owed: a tool runner serves one module's bundle again without restarting (H-A-158's make before break, for a bundle), and a publisher retries a seat that answers no responders, within a bound. Also seen there: the registry seat's list answer exceeds the bus (1.5 MB; pages are owed, the same habit as row 65), and a finding of kind read-side-down raised by one writer cannot be cleared by the tools' writer (owed: one owner per finding kind). | H2 |