H-A-146: forget a resolution whose fetch failed, so versions is asked again
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
This commit is contained in:
@@ -212,6 +212,7 @@ func TestTheNodeComposesItsWantsFromTheBus(t *testing.T) {
|
||||
t.Run("it reads the catalog half by the fingerprints its wants name", composeFromEntries)
|
||||
t.Run("a running module without an entry stands as the newest build", runningModuleWithoutEntryStandsAsTheNewestBuild)
|
||||
t.Run("a want naming its version is resolved through the registry seats", aWantNamingItsVersionIsResolvedThroughTheRegistrySeats)
|
||||
t.Run("a resolution whose fetch failed is forgotten", aResolutionWhoseFetchFailedIsForgotten)
|
||||
b := newFakeBus()
|
||||
fp := meshcatalogclient.SourcePrefix2 + strings.Repeat("a", 64)
|
||||
digest := meshcatalogclient.ManifestDigest([]byte(lemurs))
|
||||
|
||||
Reference in New Issue
Block a user