Design 47 H2: H-A-419 to H-A-421; the H-A-415 addendum's words
This commit is contained in:
@@ -419,3 +419,29 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
|
||||
- **H-A-412 (third addendum, 01:11)** The step run takes `output` out of each test answer: the run text goes only to the
|
||||
outputs object of a step ask, and a check ask's answer keeps no text (one place for the run text, P3), so a check
|
||||
answer stays within the steps state's value.
|
||||
- **H-A-415 (addendum, 01:16)** (3) is withdrawn: the forge module's manifest is accepted in both cases once the validator's
|
||||
request resolves the seat definitions' includes (mesh-sdk seatdef.Resolve); the raw seat.json files gave the
|
||||
package-registry seats no verbs, which refused gitea and the build modules' publish invokes alike. H2's
|
||||
package-registry definitions hold publish, publish-part, versions and remove; D4a changed only oci-artifact-registry's
|
||||
list. Every validator run of this milestone resolves includes first (the request builder /var/tmp/h2c4c/mkreq.py does).
|
||||
(2) stands as far as the node-engine invokes `versions` on oci-artifact-registry: that seat's version read is `list
|
||||
{module}`; the node-engine's developer checks the container-image-registry seat's definition before changing that call.
|
||||
- **H-A-419 (the node record states the declaration Version its engine reads, 01:18)** H-A-416 (2). The node record
|
||||
(the have key `<node>.node`) gains `declaration-reads` (int, written from declaration.Version), its form raised by one,
|
||||
a K row the node-engine's developer makes as for `run`; the composer reads it there and writes the lower Version,
|
||||
leaving out what it lacks. One name per thing (the word the manifest states), P3; the `contract` number stays what it is.
|
||||
- **H-A-420 (I4's re-pin revision, the event's revision form, where reservations are kept, 01:18)** §805. (1) A pipeline's
|
||||
reservations happen at one catalog revision, so the indexer keeps one re-pin revision per event revision: the first
|
||||
version-reserved of a revision makes it, later ones of the same revision add their pins to it; the check counts one
|
||||
revision for twenty packages. (2) version-reserved's `revision` is the indexer's revision name `<branch>.<n>`; the
|
||||
builder's B11 writes that form. (3) The indexer keeps which reservations a revision holds in its state `heard` under
|
||||
`reserved.<revision>.<module>` (8 MiB, key-ttl the pipeline's bound), read at a pipeline-ended not passed for the
|
||||
re-pin to the newest released (H-A-418). P3.
|
||||
- **H-A-421 (the conformance kit's cases for H2's forms, 01:18)** BM4 (2). (i) StepEnds refuses an AskSteps with no
|
||||
Outputs; (ii) one new case SeatVerbs(t, seat, tools, steps) every build module calls with its seat tools: it runs
|
||||
current, output and answer for a fake ask and judges them against the part's form 2 (current: node, takes, since,
|
||||
capacity, asks with asker; output: input ask alone, answer ask, output, size, failing, or a refusal for an ask never
|
||||
run here; answer: ask and call, chunks), and runs a pipeline step through steps with a Test body answer holding
|
||||
`output`, a NOT RUN skip and an archive, judging the end's not-run, the archive reaching the test call and the run's
|
||||
output kept as `<node>.<ask>`; (iii) install judged in SeatVerbs only when steps.Install is set. One kit case for the
|
||||
forms, P3; a rule states how it is checked.
|
||||
|
||||
Reference in New Issue
Block a user