From 11d257516a51b8c5d08edd66dcffedd1ead8d923 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 15:56:00 +0100 Subject: [PATCH] Design 47 fix: U8, the refused key is written on the failed build's event --- .../01-to-be/47-milestones/fix-unpublished-placed-module.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/fix-unpublished-placed-module.md b/03-DESIGN/01-to-be/47-milestones/fix-unpublished-placed-module.md index 59b4bfb8..53ea0d9e 100644 --- a/03-DESIGN/01-to-be/47-milestones/fix-unpublished-placed-module.md +++ b/03-DESIGN/01-to-be/47-milestones/fix-unpublished-placed-module.md @@ -29,3 +29,6 @@ goes alone on main and milestone G joins it, since G rewrites the same files. - **U7** (the provisioner's retiring asks whose id is over 64 characters are refused at every pass, and the key's why says it waits for an open ask): the ask id is bounded, made from the key, and a refused ask is said in the key's why and in provisioner_health, in the same group (P3). +- **U8** (develop, U1's trigger): the node-engine writes U1's refused key on the event that the placed module's newest + build ended failed, not at the next pass some other input starts; a refusal written late is a wait nobody can read + (P1, P3).