Skip to content

Commit 47b0165

Browse files
matt2eclaudeStar Lord
authored
perf(relay): confirm membership hints with exact channel reads (#486)
Signed-off-by: Matt Toohey <[email protected]> Signed-off-by: Star Lord <b89298dbe87c6b3fd8a425b535d9d161f23c88d555a47925ae0b04dfe02b201e@buzz.block.builderlab.xyz> Co-authored-by: Claude Code <[email protected]> Co-authored-by: Star Lord <b89298dbe87c6b3fd8a425b535d9d161f23c88d555a47925ae0b04dfe02b201e@buzz.block.builderlab.xyz>
1 parent bbd470c commit 47b0165

5 files changed

Lines changed: 935 additions & 16 deletions

File tree

‎docs/relay-queries.md‎

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -681,7 +681,19 @@ including failures when no channel is selected. The store owns that obligation,
681681
the optional metadata read, and its learned retry time; live Retry and diagnostic
682682
Refresh channels share the same cooldown. Metadata failure never revokes successful
683683
membership authority. Hints during an active read coalesce into one follow-up;
684-
a refused read retains the obligation without draining queued work. Live Retry
684+
a member-added hint naming a channel the viewer does not yet hold confirms only
685+
that channel when the list is already ready, while removals, unnamed hints, held
686+
channels and CLOSED still schedule the full refresh. Named hints arriving
687+
together share one exact read, a channel already being confirmed is not read
688+
again, and a full refresh that starts afterwards retires pending confirmations
689+
in favour of its own result. A full refresh that fails while a confirmation is
690+
pending keeps its error for Retry rather than triggering another refresh, but a
691+
superseding refresh that a concurrent revocation interrupts before it settles
692+
reruns, because the grants it inherited still need a complete roster. A cache
693+
clear or disconnect drops queued and pending confirmations outright, before a
694+
queued hint can read into the new session state; the next establishment's
695+
refresh or Retry owns recovery there.
696+
A refused read retains the obligation without draining queued work. Live Retry
685697
retries failed/deferred work, not every successful refresh or healthy subscription.
686698
A new channel-route failure with Buzz's `restricted: channel access revoked`
687699
reason schedules this same coalesced refresh. CLOSED is a hint, not archive or

0 commit comments

Comments
 (0)