Design 47 H: section 10, findings 62-71

This commit is contained in:
2026-11-20 21:31:31 +01:00
parent 9c61151f1f
commit d2ccf4f3bd
@@ -573,3 +573,18 @@ Added by the lead at 19:50 CET, from the run of 18:40 to 19:50; a row met again
| Met again: the step outputs store keeps 0 bytes, so a failed test's words are lost (the row of 18:40); the pipeline runner. | H2 |
| The proof of the runbook's step 7 is still owed: proof 1 failed on the version race, proof 2 twice, on stale pins and on the composition step of a module no machine holds (settled by H-A-179), both settled; the freeze is not lifted (step 8). | H1 |
| Four hand placements more (the distribution tools bundle, the assigner, the builder's program, the node-engine twice) and five hand restarts were needed to break circles, each said to the operator; the runbook. | H1, the runbook |
Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again names the row it adds to.
| finding | milestone |
|---|---|
| A pin named the newest release of the module holding a package (its release number), while a Go package's version is its tag, so every importer of a nested package failed on "unknown revision" (main.39), and pipelines kept failing on old pins; the indexer (`mesh-delivery-indexer`). Settled by H-A-183, H-A-184 and H-A-185 (the pin is the newest version the registry published for the package path, within the series the module's manifest accepts), built in the indexer and placed by hand, because its own pipeline could not deliver it. | settled in H1 |
| Nine Go packages other modules import were never declared artifacts of their modules (among them the builder's `builds`, the bus module's `busgrants`, disk-load's `diskreadings`), so no release published them and their importers' builds wait past the bound; the owning modules' manifests in the catalog. Settled by H-A-186 (an imported mesh package is a declared artifact of its module); still owed: the catalog's check that refuses a manifest whose Go module imports a mesh package path no module of the catalog declares. | H2 |
| A package artifact's declared series (0.1) differed from its module's version series (0.3 for the assigner), so its publishes would pin nothing; the manifests in the catalog. Settled by H-A-188 (a package artifact's series is its module's version series, or left out); still owed: the catalog's check that refuses a mismatch, and the gate's manifest (`mesh-delivery-gate`) naming the series 0.3 in its `packages` so it accepts the assigner's asks, in the catalog's next change. | H2 |
| A pipeline record of 112 or 129 movers exceeded the bus's 1 MiB message limit (the row of 19:50 on the record's shape); the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-187 (steps one key per mover), H-A-189 (a mover's unlogged step-log entries under its mover key), H-A-190 (a step-log entry names its mover) and H-A-191 (`list` answers counts, `mover-count` and `step-count`). Still owed: a tool that reconciles a record whose mover-key writes failed; and a bound on every kept value (64 KiB) and on every tool answer, in mesh-sdk, the lead's proposal, whose scope waits on the operator. | H2 |
| The builder's step path pinned a package of the same pipeline at the module's release number, and the Go build module (`mesh-build-go`), given no pin, took another package's version of the same repository (its "askedFor" fallback), so both built against versions never published; the builder and the Go build module. Settled by H-A-192 (the builder takes a pin from the catalog entry or the registry's package-published event alone; a build module given no pin refuses the build, loud); still owed: the Go build module's half, in the catalog. | H2 |
| The builder's lane narrowed a module's single fetch to the paths of its package artifacts, so a program build found no main module; the builder. Fixed in the builder, by ADR 0499 clause 1. | settled in H1 |
| The indexer's tools bundle missed a catalog-revision event in silence, so the pipeline runner waited 12 minutes for the next revision: the SDK's adopted-view reader throws a handler's error away and acknowledges an event no handler matched; mesh-sdk and the indexer's tools bundle. Owed: the SDK says a handler's error and offers the event again; the bundle logs a line per event it is handed; and a tool that reads the bundle's trunk view again. | H2 |
| 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. Cause not yet known. | H2 |
| The node-engine (`mesh-host`) on one machine cannot create a new version's folder ("operation not permitted"), met twice, two days apart; the node-engine. Cause not yet known. | 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 |