Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Long polling more time to recover #447

Merged
merged 1 commit into from
Oct 16, 2023

Conversation

adam-encord
Copy link
Contributor

@adam-encord adam-encord commented Oct 9, 2023

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:

  • Increased the value of LONG_POLLING_SLEEP_ON_FAILURE_SECONDS from 3 to 10 in encord/client.py. This extends the time the system waits for a server response on failure, improving resilience against temporary network issues.

🎉🎈

In the realm where code and servers play,

A change was made, a delay to stay.

From three to ten, the seconds grew,

For stronger bonds, between me and you. 💻💞

So celebrate this chore, small but mighty,

Making our connection more flighty! 🚀🌟

@github-actions
Copy link

github-actions bot commented Oct 9, 2023

Image description CodeRabbit

Walkthrough

The overall change in this pull request involves adjusting the system's response time to server failures. Specifically, it increases the wait time before retrying a failed server request from 3 seconds to 10 seconds, effectively extending the total wait time from 9 seconds to 30 seconds.

Changes

File Summary
encord/client.py The value of LONG_POLLING_SLEEP_ON_FAILURE_SECONDS has been increased from 3 to 10. This extends the time the system waits for a server response on failure, increasing the total wait time from 9 seconds to 30 seconds.

Notes

Chat with Image description CodeRabbit Bot (@coderabbitai)

  • Reply on review comments left by this bot to ask follow-up questions. A review comment is a comment on a diff or a file.
  • Invite the bot into a review comment chain by tagging @coderabbitai in a reply.

Code suggestions

  • The bot may make code suggestions, but please review them carefully before committing since the line number ranges may be misaligned.
  • You can edit the comment made by the bot and manually tweak the suggestion if it is slightly off.

Ignoring further reviews

  • Type @coderabbitai: ignore anywhere in the PR description to ignore further reviews from the bot.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image description CodeRabbit

Commits Files that changed from the base of the PR and between e8ce861 and 6807a00 commits.
Files selected (1)
  • encord/client.py (1)
Review comments generated (1)
  • Review: 0
  • LGTM: 1

@github-actions
Copy link

github-actions bot commented Oct 9, 2023

Unit test report

124 tests   113 ✔️  6s ⏱️
    1 suites    11 💤
    1 files        0

Results for commit 6807a00.

@sergei-encord sergei-encord merged commit d9bc1fd into master Oct 16, 2023
4 checks passed
@sergei-encord sergei-encord deleted the aj/long-polling-more-time-to-recover branch October 16, 2023 14:36
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.

2 participants