Design 47 H: section 10, finding 162

This commit is contained in:
2026-11-21 18:55:44 +01:00
parent 4a39cfc912
commit f0bed6acc3
@@ -678,3 +678,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
| 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 |
| With the two fixes of the pipeline runner live, the queue ran through: three re-pin pipelines passed between 18:39 and 18:45 (each with few movers), and the tool runner's pipeline was fourth in line at 18:47. Its release's publish had reached the front of the builder's publish queue at 18:27, in the very minute the control-node's tool runner restarted for a hand pack's bundle, and failed with no responders; the builder did not retry it in eighteen minutes, so the lead asked the publish again through the builder's own tool at 18:46, and it was published at 18:46:46 (the publish-queue fix of rows 158 and 160, in review, makes the retry the builder's own). The passed pipelines reached the control-node as the evening's first asks for a person's approval: the store and the identity provider, each recorded as a module a person moves, asked on the operator's channel at 18:45 and 18:46 before their containers are made again (rows 158, 159 and 160); the pipeline runner (`mesh-delivery-pipeline`), the builder and the node-engine. | H1 |
| The large pipeline of the SDK's release (853 steps, row 159) ended failed at 18:37: the private network module's unit and integration tests failed, and every other mover passed; its movers get no pipeline by themselves (row 147's rule) and will ride the next merge that touches them. The review of the publish-queue change (rows 158 and 160) found one thing: its read tool reads the builder's own states in pages, which H-A-255 forbade for H1 because each page replays the bucket; H-A-292 allows it for a module's own tool when one page of about 768 KB holds the whole state (one replay instead of a request per key), and the review judges the same head again (rows 158, 159 and 160); the pipeline runner (`mesh-delivery-pipeline`) and the builder. Owed: a failed pipeline's movers put in a pipeline again. | H1 (the review); H2 (the re-pipelining) |