From 9c9342d8bf4153f1975a2fc5ba66a885f1fde1cb Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 23:12:51 +0100 Subject: [PATCH] Design 47 H: H-A-361 and H-A-362, a pipeline ending failed after a hand-off; the queue settings in the definition --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 3a0556b8..fbaf4d42 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -2253,3 +2253,16 @@ Where two preparers disagreed, the chosen one is named. - **H-A-359a (correction, 23:11)** The runtime's state act create already exists for bundles (create with a TTL, refused when the key exists); nothing is built in mesh-tools for H-A-359. mesh-sdk's bundle state gains TakeOnce over it and its TypeScript twin; the taken state's name and key have one definition both sides refer to. P9. +- **H-A-361 (a pipeline ends failed after a hand-off, 23:12)** Met twice tonight (the group's pipeline at 22:51, the + catalog fix's at 23:00): seconds after newer pipelines took movers away (H-A-223), the older pipeline ended failed + with every kept mover's steps counted as not passed, though none had been asked. The kind: the end judgement + counts a step never placed as a failure. Fix in the runner: a step not asked is open, never failed; after a + hand-off the pipeline places or keeps its remaining steps and ends only when every kept step has ended, and the + journal says the hand-off and what stays. Checked first against the undelivered fixes riding main.165 (the end + with nothing open, the versioned end): if they already cover it, nothing more; else a small fix from main. + Recovery of the moment: the group's build asked again by hand (22:12 UTC). fix-a-bug-met-twice, P-failure-loud. +- **H-A-362 (the work queue's settings in the seat definition, 23:12)** seatdef's message gains max-age, + duplicates-window, ack-wait and in-progress as duration strings and max-msgs, max-ack-pending and max-deliveries + as integers; mesh-sdk's bus composition derives the work-queue stream and its one shared worker from them; the + grants part moves onto that derivation and its own copy goes (a mesh-sdk subtask, then the delivery developer's + D1b). P9 (derived once), P3.