Skip to content

Read an open channel's history again when a read of it failed - #75

Merged
Ocnrb merged 2 commits into
mainfrom
fix/history-after-bridge-reload
Sep 27, 2026
Merged

Ocnrb merged 2 commits into
mainfrom
fix/history-after-bridge-reload

Conversation

@Ocnrb

@Ocnrb Ocnrb commented Sep 27, 2026

Copy link
Copy Markdown
Member
  • A failed initial read of the open channel is no longer final: the group is read again (-3 first) with a short backoff, cut short when the bridge or the node comes back
  • A page the node broke off, or a read the bridge lost to a reload, counts as failed; a 4xx refusal or a stream without storage counts as answered
  • Paging waits while the open's reads are owed, so an empty screen no longer asks the storage node every second
  • While reads are retried the screen keeps loading; when they give up it says so instead of "No messages yet"

Ocnrb and others added 2 commits September 27, 2026 16:38
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…en they gave up

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@Ocnrb
Ocnrb merged commit 67b60b1 into main Sep 27, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant