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

Disallow failing in most API requests #590

Merged
merged 3 commits into from
Oct 22, 2024
Merged

Disallow failing in most API requests #590

merged 3 commits into from
Oct 22, 2024

Conversation

Al4ise
Copy link
Collaborator

@Al4ise Al4ise commented Oct 21, 2024

Introduces infinite retries for some network requests.

Description by Korbit AI

What change is being made?

Modify API request methods to disallow failures by default, adding retry logic for failed requests in interactive_brokers_rest_data.py.

Why are these changes being made?

These changes ensure that API requests are more robust by retrying upon failure, which reduces the likelihood of transient errors affecting the application's functionality. This approach improves reliability and user experience by handling temporary issues like rate limiting or network errors more gracefully.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

Copy link
Contributor

@korbit-ai korbit-ai bot left a comment

Choose a reason for hiding this comment

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

Review Summary by Korbit AI

Code Execution Comments

  • Implement a maximum retry limit or backoff strategy and add logging to prevent infinite loops and aid debugging.
Files scanned
File Path Reviewed
lumibot/data_sources/interactive_brokers_rest_data.py

Explore our documentation to understand the languages and file types we support and the files we ignore.

Need a new review? Comment /korbit-review on this PR and I'll review your latest changes.

Korbit Guide: Usage and Customization

Interacting with Korbit

  • You can manually ask Korbit to review your PR using the /korbit-review command in a comment at the root of your PR.
  • You can ask Korbit to generate a new PR description using the /korbit-generate-pr-description command in any comment on your PR.
  • Too many Korbit comments? I can resolve all my comment threads if you use the /korbit-resolve command in any comment on your PR.
  • Chat with Korbit on issues we post by tagging @korbit-ai in your reply.
  • Help train Korbit to improve your reviews by giving a 👍 or 👎 on the comments Korbit posts.

Customizing Korbit

  • Check out our docs on how you can make Korbit work best for you and your team.
  • Customize Korbit for your organization through the Korbit Console.

Current Korbit Configuration

General Settings
Setting Value
Review Schedule Automatic excluding drafts
Max Issue Count 10
Automatic PR Descriptions
Issue Categories
Category Enabled
Naming
Database Operations
Documentation
Logging
Error Handling
Systems and Environment
Objects and Data Structures
Tests
Readability and Maintainability
Asynchronous Processing
Design Patterns
Third-Party Libraries
Performance
Security
Functionality

Feedback and Support

error_message = f"error: Task '{description}' Failed. Status code: {response.status_code}, Response: {response.text}"
to_return=None
first_run=True
while (not allow_fail) or first_run:
Copy link
Contributor

Choose a reason for hiding this comment

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

category Functionality

Implement a maximum retry limit for API requests.

The implementation of infinite retries for API requests could potentially lead to unintended behavior. Consider adding a maximum retry limit or implementing a backoff strategy to prevent infinite loops. Also, add logging to track the number of retry attempts for each request. This will help in monitoring and debugging the system's behavior.

Chat with Korbit by mentioning @korbit-ai, and give a 👍 or 👎 to help Korbit improve your reviews.

@grzesir grzesir merged commit c802f9c into dev Oct 22, 2024
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants