Design 47 H: H-A-146, a resolution whose fetch failed is forgotten
This commit is contained in:
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user