Design 47 G: the lead's answer A-454 (an upstream image is no part of the want) #640
@@ -1327,3 +1327,9 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
removed, or at another fingerprint. A have in the middle of a move (`backing-up`, `applying`, `checking`) is not "no
|
||||
longer held", so the backup ask stands while the node backs up again after an "again" answer, and a second failure
|
||||
is asked under the next number, as §16 says.
|
||||
- **A-454** (§421's parts check, A-432; principles 7 and 3) A want's parts are the artifacts the mesh built for the
|
||||
module. The node-engine's check that what a composition fetches matches the want's parts counts only what is fetched
|
||||
from the mesh's artifact store (a bundle, an archive, a program, or a container image the mesh built, named through the
|
||||
artifact store or the registry seat); a container image the manifest pins from outside (an upstream image by its digest)
|
||||
is no part and is never "fetched and not in the want's parts". (Live, novox 2026-11-17 00:46: distribution 0.1.11 held
|
||||
"parts-differ: fetched and not in the want's parts" for the upstream `registry` image its manifest pins.)
|
||||
|
||||
Reference in New Issue
Block a user