From 9f7619d3c470e6e31d080c770e507385b9aebeb4 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 23:23:32 +0100 Subject: [PATCH] Design 47 H: H-A-371 and H-A-372, archive-only lanes without Go code; a bundle's publish names its version --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index b3c65e3d..957cd1e8 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -2302,3 +2302,16 @@ Where two preparers disagreed, the chosen one is named. setting by its key from that word, in a process and a bundle alike, with typed readers (a duration with a default); the per-module file words (the runner's *_FILE words) go. The node-engine's developer builds the word (E3's counterpart), the SDK's the reader. P9, P3. +- **H-A-371 (an archive-only lane of a module without Go code, 23:23)** Since A-447a the Go build seat refuses a fetch + whose module directory chooses no Go module; the builder sends that directory with every lane, and an archive is + packed by the Go build seat, so every module with an archive artifact and no Go code (the packet filter holder and + 36 others) cannot build: five failures of one fingerprint on three build nodes tonight, sixteen modules at 23:17. + Fix in the Go build module: a directory that chooses no Go module is an empty scope (the empty scope file written), + never a refusal; a Go bundle or package whose directory holds no go.mod still fails at its build step, naming it. + A-447a's "none chosen fails naming it" ends for the fetch. Test: an archive-only lane of a module with no Go code + fetches and packs. Recovery: rerun the build step of each failed pipeline's movers once the Go build module is + delivered. fix-a-bug-met-twice (the kind, 37 modules), P-failure-loud. +- **H-A-372 (a bundle published by digest marks no reservation, 23:23)** The Node build module publishes every bundle + with an empty version, so the builder says "package-published not said … a by-digest publish" and the bundle is + not marked against its reservation. Fix in the Node build module: the publish carries the version the ask + reserved. Test: a bundle's publish names the ask's version. P3, P-failure-loud.