Design 47 H: H-A-197, every pull loop claims through the SDK
This commit is contained in:
@@ -1050,3 +1050,8 @@ Where two preparers disagreed, the chosen one is named.
|
||||
refuses, loud at bind time, a second pull loop on a durable the same process already pulls (the error names the
|
||||
durable and both binders), so the kind cannot run in silence again; the cause itself is delivered by the tool
|
||||
runner's own release (H-A-132/133). P1 (failure must be loud), P7.
|
||||
- **H-A-197 (every pull loop claims through the SDK, 22:05)** Met in the build of H-A-196: the tool runner binds its
|
||||
durables through the bus client directly, so the SDK's guard would not have seen the two loops that caused the
|
||||
fault. Every module's pull loop, the tool runner's included, claims its durable through the SDK's one guard before it
|
||||
pulls (P7: shared behaviour lives in the SDK), and a re-serve stops its old loop before it binds the new one so the
|
||||
guard refuses only a true second loop. P1, P7.
|
||||
|
||||
Reference in New Issue
Block a user