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.
Introduction and Explanation
Long polling more time to recover
With current settings we wait up to
LONG_POLLING_SLEEP_ON_FAILURE_SECONDS * LONG_POLLING_RESPONSE_RETRY_N
seconds for server to respond correctly.With current defaults that is 3 * 3s = 9s in total, which is too small, let's increase this to 3 * 10s = 30s
Summary by CodeRabbit
Chore:
LONG_POLLING_SLEEP_ON_FAILURE_SECONDS
from 3 to 10 inencord/client.py
. This extends the time the system waits for a server response on failure, improving resilience against temporary network issues.