node-engine seat: compose-candidate is a verb marked chunks; its ask carries a call token and its answer names the chunks (A-237b)
Builds: design 47 G (G-22 lead answers 2) A-237b; A-237, A-249
This commit is contained in:
Vendored
+5
-1
@@ -981,6 +981,8 @@ export interface ComposeAnswer {
|
||||
|
||||
/** is what compose-candidate takes. */
|
||||
export interface ComposeCandidateInput {
|
||||
/** 128 random bits the caller chooses: the subject token of the chunks and acknowledgements the composition input is sent in, whatever its size (design 47 G A-237b); an ask with input and no call is answered inline, as before the checker goes (G-6 section 321) */
|
||||
"call"?: string;
|
||||
/** the key of the candidate to compose: a check's candidate in the indexer, <group>.<heads hash>; a branch pipeline's catalog graph revision, <branch>.<revision> (the node-engine reads its entries through mesh-catalog.revision); or a run on request's, run-<id>; built and read by the seat's client (nodeengineclient) */
|
||||
"candidate": string;
|
||||
/** also answer the composition input the candidate was composed from, for the sandbox path */
|
||||
@@ -991,7 +993,9 @@ export interface ComposeCandidateInput {
|
||||
export interface ComposeCandidateAnswer {
|
||||
/** the candidate's key */
|
||||
"candidate": string;
|
||||
/** when asked: the composition input it composed from */
|
||||
/** when asked with input and a call token: how many chunks of at most 512 KiB carry the composition input, sent on the chunk subject of the call, each acknowledged by the caller (design 47 G A-237b) */
|
||||
"chunks"?: number;
|
||||
/** when asked without a call token: the composition input it composed from, inline, up to what one answer carries (the checker's form, kept until G removes the checker, G-6 section 321) */
|
||||
"input"?: Record<string, unknown>;
|
||||
/** every module placed on the node, sorted by name */
|
||||
"modules": Module[];
|
||||
|
||||
Reference in New Issue
Block a user