Answer A-456a and A-457a: a released build counts as reserved; the publish retries on the builder's own re-ask state
This commit is contained in:
@@ -1406,3 +1406,15 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
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.)
|
||||
- **A-456a** (A-456; principles 3 and 7) A released build counts as reserved: the build step passes a reserving build
|
||||
whose fingerprint has a reservation or a released version. The builder knows the second from its own record of the
|
||||
`version-released` it wrote for that fingerprint; where that record keeps no fingerprint today, the builder keeps
|
||||
it there (its own state), never asking the catalog. (From the develop of A-456: the reservation is deleted at
|
||||
release, so a rerun of a released build's step failed "no version reserved".)
|
||||
- **A-457a** (A-457; principles 7, 1 and 11) "The builder's own work queue" is no new stream and no new process: the
|
||||
publish item is a re-ask in the builder's own re-ask state, the mechanism `builder_reserve_done` and publish-again
|
||||
already queue on, consumed by the builder's one process. The value carries its tries and its next try; a failed or
|
||||
unanswered publish is written again with tries plus one and a pause of `publish-pause` doubled per try up to
|
||||
`publish-pause-max`, and after `publish-tries` tries it ends loudly (log, condition) and stays readable in the
|
||||
builder's tools; all three are settings with defaults (30 s, 30 min, 8). (From the develop of A-457: a work-queue
|
||||
stream would need a `bus` restating the builder's whole account, or a second process.)
|
||||
|
||||
Reference in New Issue
Block a user