Answer A-461d: a placed module not heard running is laid from its placement or trunk build
This commit is contained in:
@@ -1845,3 +1845,9 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
`validate-tries` tries in a row ends could-not-validate with its words, so a request that keeps moving is loud.
|
||||
Could-not-validate keeps §713's other causes (the step could not run, the program exited other than 0, the answer
|
||||
not both cases), asked again by a later merge or `indexer_validate_again`.
|
||||
- **A-461d** (A-461b; principles 7 and 2) A module placed on another node and not heard running there counts as one
|
||||
whose running build has no entry: the composer lays it from the build its placement names, or, when the placement
|
||||
names none, from its trunk build through the seat `mesh-catalog`'s verb `module`, exactly as A-461b says. Being heard
|
||||
running is never a condition for laying another node's module; the assignment is the mesh's truth of what is placed
|
||||
there. (From the develop of the store fetchers' fix: shanks heard no `running` of `distribution` on novox, so it laid
|
||||
the store's holder name-only and found no store address.)
|
||||
|
||||
Reference in New Issue
Block a user