From b4d6bf9bd0441e42b88f7db5a9305cd1b5631007 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 16:31:57 +0100 Subject: [PATCH] Design 47 H: H-A-150, which failed fetch forgets a resolution --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 4 ++++ 1 file changed, 4 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 018b6e21..266ca384 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 @@ -736,3 +736,7 @@ Where two preparers disagreed, the chosen one is named. out. It clears where the assignments are judged, not only where a machine is composed: the assigner clears it in its pass over the assignments (the one that writes wants) when the assignment is gone or the module is listed again, so the clear does not wait for the next step on that machine. P3. +- **H-A-150 (which failed fetch forgets a resolution, 16:38)** Met in the build of H-A-146: a resolution is forgotten + when the store answered the fetch and it failed (a 404, bytes not of the digest), never when the bus did not answer + (that fetch is tried again as today, the module not held for it). The take-in's fetch and the apply's fetch of a + bundle both forget, since either can meet a wrong digest. P7, P3.