Design 47 H2: the transport fault's two new classes, now accepted, in the glossary and the part
ADR 0668 and ADR 0664 accepted their insights of 2026-11-21, so the word and the two lines that rest on them say so.
This commit is contained in:
+3
-1
@@ -306,7 +306,9 @@ controller and the store; for module assignment, by the seat `mesh-module-assign
|
||||
- **transport fault** — a failure of a call or a step because the part it asks did not answer for a moment, not
|
||||
because of what it asked: a name lookup that timed out; a connection refused, reset or unreachable; a seat verb
|
||||
answered with no responders while a holder of that seat is named in the assignments (ADR 0664 §1); and, for a call,
|
||||
its own deadline passing (ADR 0668 §1). A build or check step that meets one is given again by the bus, at most
|
||||
its own deadline passing (ADR 0668 §1); a holder's `away` to a seat ask, its word that a part it depends on did
|
||||
not answer, naming that part (ADR 0668 §1, ADR 0664 §1, insights of 2026-11-21); and a 401 or 5xx answer of the forge to
|
||||
a step's fetch of its source (ADR 0664 §1, insight of 2026-11-21). A build or check step that meets one is given again by the bus, at most
|
||||
three runs (ADR 0664 §1, §2); a kept call is called again. A fault in what was asked (a compile error, an unknown
|
||||
revision, a seat no holder is named for) is not one, and ends the step or the call at once.
|
||||
*Not:* ~~transient error~~ (hq), ~~network blip~~ (hq)
|
||||
|
||||
@@ -69,15 +69,15 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
||||
the answer and logs one line; a call past its bound returns every try; a refusal returns at once; a holder given the
|
||||
same ask id twice acts once. Whole (runner): a composition ask whose holder is away for 40 s passes its step with no
|
||||
hand act.
|
||||
- §776 **A holder says `away` when a part it depends on is away.** (ADR 0664 §1 and ADR 0668 §1, each with its insight
|
||||
proposed 2026-11-21; H-A-300 (2), H-A-301, H-A-334 (3), H-A-339 (5); rows 177, 178) mesh-sdk's seat error answer
|
||||
- §776 **A holder says `away` when a part it depends on is away.** (ADR 0668 §1 and ADR 0664 §1 (insights of
|
||||
2026-11-21, accepted); H-A-300 (2), H-A-301, H-A-334 (3), H-A-339 (5); rows 177, 178) mesh-sdk's seat error answer
|
||||
gains the kind `away`, with `part` (what did not answer) and `words`. The forge module, holder of the seat `git`,
|
||||
answers `away` when the forge answers 401, 502 or 503 or a connection fault and the forge's own unauthenticated
|
||||
version read fails or names its store unavailable; it answers `refused`, "the forge refuses the mesh's admin
|
||||
account", only when that read succeeds and a freshly minted token (§808) is refused too, and it never words a refusal
|
||||
as an account to create. Every caller reads `away` as a transport fault (§775). This adds one class, a holder's own
|
||||
word that what it depends on is away, to the classes ADR 0664 §1 and ADR 0668 §1 list; the line rests on those two
|
||||
insights, accepted before H2's prepare starts. Built in H2 in mesh-sdk (the error kinds) and the forge module
|
||||
insights, accepted on 2026-11-21. Built in H2 in mesh-sdk (the error kinds) and the forge module
|
||||
(mesh-catalog). How it is checked: unit (forge module): a 401 with the version read failing answers `away`; a 401
|
||||
with the read passing and the fresh token refused answers `refused`. Whole (forge module): with the store stopped for
|
||||
30 s, a merge call in that window answers `away` and lands when called again.
|
||||
@@ -270,8 +270,8 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
||||
|
||||
### The build modules (seats `node-build-go`, `node-build-node`, `node-build-image`)
|
||||
|
||||
- §799 **A fetch or a publish that meets its holder away is a transport fault.** (ADR 0664 §1, §2; H-A-301, H-A-341
|
||||
(8), H-A-342 (1); row 178) A build or check step whose fetch of its source meets a connection fault or a 401 or 5xx
|
||||
- §799 **A fetch or a publish that meets its holder away is a transport fault.** (ADR 0668 §1 and ADR 0664 §1 (insights of 2026-11-21,
|
||||
accepted); ADR 0664 §2; H-A-301, H-A-341 (8), H-A-342 (1); row 178) A build or check step whose fetch of its source meets a connection fault or a 401 or 5xx
|
||||
answer of the forge, or whose publish to a registry seat meets no responders or a bundle that exited, ends its run
|
||||
`again`, never the step (ADR 0664 §1), with no seat call to learn why; the tool runner settles the ask with a
|
||||
delay of 15 s after the first run and 60 s after the second (`again-delays`, a setting of each build module, default
|
||||
|
||||
Reference in New Issue
Block a user