From a1d073139be3c482bbef77b9d6c97d7c9991b1f4 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 16:43:48 +0100 Subject: [PATCH] Design 47 H: section 10, finding 149 --- .../01-to-be/47-milestones/H-deliver-the-delivery-system.md | 1 + 1 file changed, 1 insertion(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md b/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md index f167a96d..a61c5712 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md +++ b/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md @@ -665,3 +665,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | Row 144's four fixes were built and reviewed by 16:00: the Node build module's and the bus module's test (merged at 15:49 as a pipeline of 36 movers; the Node build module's pack goes onto the build node by hand, so the forge module's build can pass in it); the builder's (approved in two rounds; the second found that every artifact carries its version at build time, so a build whose number a registry holds at another digest is built again at the next free number rather than moved: H-A-279); and the pipeline runner's and the assigner's (approved in two rounds; the first found that a passed mover with no version yet must hold its tier, else a later tier is wanted before it: H-A-277). The merge of the runner's and the assigner's waits on the operator's word, because the session's permission check refused the lead's dispatch of it (row 144); the Node build module, the bus module, the builder, the pipeline runner (`mesh-delivery-pipeline`) and the assigner (`mesh-delivery-assigner`). | H1 | | The tool runner (`node-tools`) sits in no live pipeline: its last one failed on other movers (row 143) and its fingerprint has not moved since, so nothing builds it again until a merge re-pins it; a module stranded by a failed pipeline gets no pipeline by itself, the kind of row 133's cancelled movers (rows 133, 142 and 143); the pipeline runner. Proof 2 therefore runs a second time, with a new one-line merge of the SDK and the tool runner once the fixes are live. Owed, as one rule: the movers of an ended pipeline that have no passed end are put in a pipeline again at the next kept revision. | H1 (the second run); H2 (the rule) | | The builder's fix (rows 144 (c) and 145) merged at 15:59 and went onto the build node as a hand pack at 16:09 (its program only, the tools bundle left, so the mesh MCP server stays up; a publish in flight was cut by the restart and is asked again). Within three minutes the builder dropped the tool runner's held release 0.1.37 for a new fingerprint of the tool runner that a fresh pipeline carries, and reserved 0.1.38 for it; its loop that asks a publish again now waits, saying so every thirty seconds, while its events consumer's backlog of about 3,800 messages drains under the bound of a hundred at about one and a half a second (some forty minutes). The Node build module's pack went onto the build node at 15:59 too, and the forge module's build moved into the newest pipeline behind the Node build module's files (rows 144, 145 and 146); the builder, the Node build module and the runbook. | H1 | +| The builder's events backlog (row 148) drained at only fifty a minute under the new builder, holding up every publish and so every pipeline waiting on one: a published at a version many reservations share still cost three seconds (the fallback by version read every reservation at the version, and the journal line read them all again), and the SDK's event hub pulls five hundred messages per pull and handles them one by one, so buffered messages outlive the thirty-second ack wait and are given again (almost every outstanding message redelivered) and handled twice. Every recovery loses something (a purge of the consumer would drop take-ins, source moves and conditions among the publisheds), so the backlog drains while the fixes build (rows 144 and 148); the builder and mesh-sdk. Settled by H-A-280 (each reservation read once, the fallback only over the unbuilt ones, in-progress sent before long work) in the builder and H-A-281 (the hub pulls at most twenty per pull and keeps a slow handler alive with in-progress) in the SDK for every module, both in build. | H1 |