From 26f5505e39e33eb80dc862b2603aa48c65bf652e Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 16:20:29 +0100 Subject: [PATCH] Design 47 H: H-A-146, a resolution whose fetch failed is forgotten --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 7 +++++++ 1 file changed, 7 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 aa46d39a..547d8dc2 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 @@ -705,3 +705,10 @@ Where two preparers disagreed, the chosen one is named. filter in place, keeping its messages, and says so in its journal (held and composed filter); it never makes the stream again for that, so nothing kept is lost; the same for `pipeline-started` and `wait-held`. A consumer's filters it already adds in place. P3, P7. +- **H-A-146 (a resolution whose fetch failed, 16:21)** Met at the first want written from a pipeline: the node-engine + resolved the want's version to a digest through the artifact store's `versions`, the fetch of that digest failed + (the store answered the manifest's digest where the blob's was due), and the engine kept the resolution for its + process's life, so the store's fix alone would never reach that node without a restart. A resolution whose fetch + failed is forgotten: the engine asks `versions` again at the next want, the next `compose` by hand, and after a + bound while the module is held, and says so in its journal; a resolution whose fetch succeeded is kept as today. + At this clean state a restart of the desktop's node-engine stands in once. P3.