Design 47 H2: H-A-412, a run's output and an oversized answer are two things
This commit is contained in:
@@ -345,3 +345,13 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
|
||||
node's crypto refuses; so two small pure libraries, each pinned in mesh-sdk's package.json: tweetnacl 1.0.3 and blakejs
|
||||
1.2.1; no hand-written hash (no crypto written by hand, tested or not). The TypeScript seals live in src/seal (export
|
||||
"./seal"), mirroring go/seal. P9.
|
||||
- **H-A-412 (a run's output and an oversized answer are two things; the big answer travels chunked, 01:00)** §791,
|
||||
BM4. (1) The object `<node>.<ask id>` in `outputs` is the run's test output, written by the build module when the level
|
||||
ends with a header beside the text holding the failing tests and their words taken from the level's results, so
|
||||
`output` answers the last 64 KB, the size and `failing` without reading the text again; `no-longer-kept` past the
|
||||
objects' max-age. (2) An answer too large for one message (a check's whole answer the builder reads with Step.Whole, a
|
||||
run's or compose's answer the assigner reads with StepEnded.ReadOutput) is not an output: it travels as the chunked
|
||||
answer of the verb that gives it, in the SDK's chunked-call form (process.CallChunks, as compose-candidate already
|
||||
does), never as an object kept for a later read; keepOver's `output.<ask>` object goes with the chunks verb, and the
|
||||
two readers move to the chunked form (the builder's and the assigner's developers, one row each). One way for a big
|
||||
answer, P3; §791's "read where it is kept" is the run output's rule. P3, ADR 0525 §6.
|
||||
|
||||
Reference in New Issue
Block a user