Repository navigation
client: retry the initial inbox state before starting REST polling - #193
Merged
Merged
Conversation
highesttt
approved these changes
Nov 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After a restart that couldn't reuse the cached session, two logins got
HTTP 503: 130: Over capacityfrominbox_initial_state.json. Since then everyuser_updates.jsonpoll has failed the same way (all 6 attempts, then backoff, ~20 give-ups/hour per login for 9+ hours). The polled URL has nocursorparameter. Before the restart, both logins had been polling without errors from a cached session's cursor.Cause:
syncUntrustedChannelsis the only place that seedsPollingCursor. WhenGetInitialInboxStatefails it just logs and returns, andconnectstarts polling anyway with an empty cursor. Nothing ever fetches the initial state again, so message requests and legacy group DMs stop arriving until the next reconnect.Change:
syncUntrustedChannelsreturns the fetch error, and the polling goroutine retries it with backoff (1 min, doubling up to 30 min) before callingStartPolling. Auth errors still go straight to polling, which already handles them.Tag
@indentto continue the conversation here.