From 2e1a6688ec2e4a4a82edeb8b4ba139c0784ddb83 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 14:10:44 +0100 Subject: [PATCH] Design 47 H2: H-A-473, the publish dispatch pulls live first --- 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md index ffcfc742..9c1a9d8c 100644 --- a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md @@ -915,3 +915,8 @@ The lead's one-line answers to the questions H2's develop and review raise (impl has read since the last registration-changed it heard; while the view is unread or stale, every member is refused as before ("the watched branches are not read yet"), never merged with the note. The holder keeps the time of its last read and of the last change heard; a read that fails is retried and said. P-failure-loud. +- **H-A-473 (the publish dispatch pulls live first, then again, 14:45)** ยง793, B4. The dispatch does not race the server's + pending count against a callback: it pulls the live consumer itself (a fetch of up to its slots, no wait) and only + when that fetch returns nothing pulls the again consumer; a live item is received the moment the fetch returns it, so + "delivered but not received" cannot exist and the whole test holds at one processor. The test bound of a build step + in the builder's whole test is tied to MESH_TEST_LEVEL_BOUND, as the other whole tests do. P-failure-loud, P3.