Design 47 G: the lead's answer A-462a (no entry in the followed catalog; the assigner asks the indexer nothing) #645
@@ -1400,3 +1400,9 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
`mesh-host.composed` events the assigner follows in its pass as it follows the haves, never by reading the
|
||||
node-engine's bucket; the module's own have is not the source, since none names a fingerprint before its want does.
|
||||
(From the develop of A-459: `composed(node, module, fp)` read only `<node>.node`.)
|
||||
- **A-462a** (A-462; principles 7, 9 and 3) "A build that has no entry" is a fingerprint the catalog half the assigner
|
||||
follows holds no entry for on any watched branch. The assigner asks the indexer nothing for it: taking a build in is
|
||||
the indexer's own work on its pending state, and its tool `indexer_take_in_pending` takes the indexer's own keys,
|
||||
not a module or a fingerprint. The want says, in its words, that it waits for the entry of that fingerprint, so the
|
||||
wait is loud and read with `assigner_why`; that sentence of A-462 about the indexer's tool is withdrawn. (From the
|
||||
develop of A-462.)
|
||||
|
||||
Reference in New Issue
Block a user