diff --git a/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md b/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md index 747c3219..02665b69 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md +++ b/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md @@ -592,3 +592,8 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | The builder writes a git tag `go/v` for every Go package, while the Go toolchain's direct fallback for a nested module looks for `/v`, so the tags serve nothing; secondary, as the registry seat holds every real version; the builder. Owed: the tag takes the package's directory, or no tag is written at all. | H2 | | A build that fails this way is asked again every 30 to 40 s, and the builder reserves a new version number each time (`mesh-build-go` 0.1.65 to 0.1.70 in five minutes): the builder never gives up a failing build of an unchanged fingerprint; the builder. Owed: a failed build of a fingerprint is not asked again until its inputs change, and no version is reserved for a build that failed before. | H2 | | With H-A-196 and H-A-197 built (the SDK's one guard against a second pull loop on a durable; the tool runner claims through it), two durable pull loops in the delivery repository still call the bus client directly: the watchman's dead-letter loop and the grants holder's main loop; each binds one durable once today, so there is no fault, but the kind is open there; the watchman and the grants part. Owed: both route through the SDK's consume function, in a change after this group's SDK is published (a module builds against the latest published SDK); the review that finds a direct durable pull is the check. | H2, or the next change of the delivery repository | +| The seat mesh-grants's verb `grants-for` (row 69): the grants holder keeps the catalog revisions it read, at most `grants-for-revisions-per-branch` per branch and only for the branches it follows, and learns the branch's newest revision from the catalog-revision event; the grants part. Settled by H-A-193 and H-A-195; merged as pull request #294, whose pipeline failed on other faults, so it is delivered with the next passing pipeline. | settled in H1 once delivered | +| The publishes the builder heard lived only in its memory and were lost at a restart, so a build waiting for a package published before it waited the whole bound; the builder. Settled by H-A-194 (before it waits, the builder asks the package registry seat's `versions` verb once), in pull request #291. | settled in H1 once delivered | +| A package artifact's steps lacked its same-repository requirements (H-A-198), and writing the derived "../" paths into the entry (H-A-199) would have changed the form of the seat mesh-catalog's `modules` value, which every module decodes, so every reader would have had to run the new client before the writer: the mesh cannot derive that ordering edge yet; the Go build module (`mesh-build-go`) and the indexer (`mesh-delivery-indexer`). Settled for H1 by H-A-202 (the Go build module derives the same-repository tree transitively; the indexer takes those directories into the fingerprint for every form without writing them into the entry). Owed: a change of a kept value's form is an ordering edge the delivery plan derives (a contract version on the value, or the readers' release before the writer's). | H2 | +| The indexer pins every other-repository requirement across the module graph, never one of its own repository (H-A-201, pull request #296), and the Go build module refuses a build with no pin (H-A-192, the catalog's change); together they end the "unknown revision" kind (row 72); the indexer and the Go build module. | settled in H1 once delivered | +| The seat mesh-catalog's hand-written digest helpers lived under the contract's generated root, so the generator's check failed every unit step; the contracts module. Settled by H-A-200 (they live in the seat's hand-written client), in pull request #295. Owed: the generator's check runs in the contracts module's own unit step on the mesh (it does today), and the hand-written clients' import of the delivery SDK (ADR 0625 ยง3) is still on trunk. | H2 |