The apply's fetch tells the composer of bytes that are not of the declared
digest (fetch_first.go), but no test held it: with that call disabled every
test of internal/apply passed. TestAStoreThatStaysAwayCostsOneBoundedWait now
has a store that serves other bytes to two modules from one source, and the
composer is told exactly once, with the declared digest.
Builds: design 47 H H-A-150
A fetch nothing answered for (a bus or store that did not answer, a gateway
saying the store is away) proves nothing about the digest, so it is tried
again as before and the module is not held for it; only an answer of the
store's (a 404, bytes not of the digest) forgets the resolution. The apply's
fetch of a bundle meets the same wrong digest as the take-in's, so it tells
the composer too (apply.WithFetchFailed, set in the node agent's apply).
Builds: design 47 H H-A-150, H-A-146, G A-430a
The engine kept a want's version resolved to a digest for its process's life
even when the artifact store's fetch of that digest failed (404, or bytes not
of the digest), so a fix of the store's answer never reached the node without
a restart. A failed fetch now forgets every resolution naming that digest, says
"resolution of <module> <version> forgotten: <why>" in the journal and holds
the module; the seats' verb versions is asked again at the module's next want,
at the next compose by hand, and after resolveAgain (the bound a failed lookup
already has). A resolution whose fetch succeeded is kept.
Builds: design 47 H H-A-146, G A-430a