From 3a9739da9a06b214f7e99526175c540ac441cce5 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 22:14:10 +0100 Subject: [PATCH] Design 47 H: section 10, findings 72-74 --- .../01-to-be/47-milestones/H-deliver-the-delivery-system.md | 3 +++ 1 file changed, 3 insertions(+) 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 5ef2ea3f..be997d70 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 @@ -588,3 +588,6 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | The seat mesh-grants's verb `grants-for` was cut after 5 s in two pipelines' composition steps (a widening entry on the vault); the grants part. The cause: the verb answers in 3.4 to 5.0 s, because on every call it reads two whole catalog revisions (about 1.4 MB each) page by page through the seat mesh-catalog's revision verb and composes every account twice, with no cache, while the pipeline runner's read bound is 5 s. A revision read whole over the bus is the same habit as the row of 21:30 on the pipeline record over 1 MiB. The fix chosen (thorough): the grants holder keeps each revision it read, a revision never changing; in build now. Not chosen: raising the runner's bound. | H2 | | The node-engine (`mesh-host`) on one machine said it cannot create a new version's folder ("operation not permitted"), met twice, two days apart; the node-engine. The cause: an immutable attribute a person set by hand on the engine's versions folder during the recovery of the mixed state of 2026-11-13, since removed; the engine keeps repeating the stale words of its last applied record. No fix in code or unit: the words clear at the next applied composition. Owed: a tool of the seat node-files that shows a file's attributes (none exists), and the engine's record says when its words date from. | H2 | | Two hand placements more (the assigner's compositions fix and the indexer with pins by package path), each on its machine, because their own pipelines could not deliver them; the runbook. | H1, the runbook | +| The "unknown revision" kind, its cause read at 22:12: the Go build module (`mesh-build-go`), given no pin for a requirement at the zero version (a transitive one, or one a sibling names), borrowed the version of the first package of the same repository in the ask, wrong since pins became per-package versions; the registry, the indexer's pins and the publishes were right for the paths they name; the Go build module and the indexer (`mesh-delivery-indexer`). Settled by H-A-192 (a build module given no pin refuses the build; the catalog's change, in build) and H-A-201 (the entry pins every requirement of the module graph, transitively; in build in the indexer). | settled in H1 once delivered | +| The builder writes a git tag `go/v` for every Go package, while the Go toolchain's direct fallback for a nested module looks for `/v`, so the tags serve nothing; secondary, as the registry seat holds every real version; the builder. Owed: the tag takes the package's directory, or no tag is written at all. | H2 | +| A build that fails this way is asked again every 30 to 40 s, and the builder reserves a new version number each time (`mesh-build-go` 0.1.65 to 0.1.70 in five minutes): the builder never gives up a failing build of an unchanged fingerprint; the builder. Owed: a failed build of a fingerprint is not asked again until its inputs change, and no version is reserved for a build that failed before. | H2 |