From c27f280237c1d5b76ce77fb140e1b0f1a5aa43e2 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 20:04:00 +0100 Subject: [PATCH] Design 47 H: section 10, finding 178 --- .../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 ca45f1b2..b9612a4a 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 @@ -694,3 +694,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | The catalog repository's two test fixes (rows 165 and 170) merged as one call at 19:29 and became one pipeline of 36 movers: a commit touching two test files moved every module of the repository, because a module's fingerprint takes the repository's commit rather than its artifacts' declared paths; the take-in took eleven minutes, seven of them without a journal line, while the indexer waited on the forge's listing under a busy control-node (the forge at over five cores). This branch's pull request (#797) was opened at 19:35 and had no delivery record or check seven minutes later; the chain from the forge's event to the gate and the checker is being read (rows 168, 170 and 174); the indexer (`mesh-delivery-indexer`), the forge module and the gate. Owed, by H-A-298: a module's fingerprint over its artifacts' declared paths and its manifest, so a commit outside them moves nothing; and a take-in that says what it waits on after a minute, naming the part. | H1 (recorded); H2 (the fingerprint, the take-in's word) | | The read of this branch's pull request (row 175) found the chain from the forge's event to the gate whole, and the cause elsewhere: hq is not a source repository of the gate, so an hq pull request gets no delivery and no check from the mesh, as none of the day's earlier hq pull requests did (the row of 14:22 on hq's registration); it merges on hq's own checks, run before every commit (ADR 0527); whether hq becomes a watched source with a mesh check is the operator's question (H-A-299). The same read met four live faults after the pipeline of 36 movers: the forge refuses the mesh's admin account since 19:41, which stops the forge watcher and the gate's acts on the forge (796 owed; being read: its cause, and the tool that provisions the account again); the gate's ledger records for two revisions exceed the bus's message size; the forge bridge's store of performed acts is full ("maximum bytes exceeded"); and the deliveries read tool cannot answer per repository (rows 150, 166 and 175); the forge module, the gate (`mesh-delivery-gate`) and the forge bridge. Owed, by H-A-299: one ledger key per module and revision; every store with a cap it prunes toward, a read of its fill and a limits tool; and a read tool that filters before it sizes. | H1 (recorded); H2 (the three); open (the forge account) | | The forge's refusal of the mesh's admin account (row 176) was the store's absence: the store's container was replaced between 19:41:04 and 19:41:32 (a move the operator approved on their channel), the forge answered 401 for that minute and said the account was refused, and it recovered by itself at 19:42:11 with a fresh token; the gate's views owed on the catalog repository's two merged pull requests failed in that minute and ended could-not-be-performed, with nothing performing them again; the forge module and the gate (`mesh-delivery-gate`). The record's own pull request (rows 175 and 176) was refused by the mesh's merge verb ("its base main is no watched branch"); the day's earlier hq merges went through the forge's own interface, and the lead's session refused to dispatch that, as it refused the two code merges of row 174, so the three wait on the operator. The private network module's pipeline (the fix of rows 168 and 169) passed at 19:46, the first pipeline of the day with that module's tests green (rows 169, 174 and 176). Owed, by H-A-300: an act failing while a part is away stays owed and is tried again with a back-off; the forge module names the cause it can read; one token mint at a time; a tool that performs every owed act of one record again. Owed too: hq registered as a watched source, so the mesh merges and checks it (H-A-299's question). | H1 (recorded); H2 (the owed acts, hq as a source) | +| One more pipeline fell to the store's half-minute absence (row 177): the re-pin pipeline that followed the tool runner's ended failed at 19:43, with many build steps failed and lint steps could-not-run, because the builder's fetch of each source met the forge's 401 in that minute and the builder read the refusal as the build's verdict; the builder. Meanwhile the pipeline of 856 steps holds the slot since 19:46, and the catalog repository's pipeline of 36 movers waits behind it (rows 170, 175 and 177). Owed, by H-A-301, the same kind as H-A-296 and H-A-300: a step whose fetch meets the forge away is asked again with a back-off until its bound, and a fetch failure is said apart from a build failure. | H2 (owed) |