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

Fix for Alpaca order tracking #660

Merged
merged 2 commits into from
Dec 11, 2024
Merged

Fix for Alpaca order tracking #660

merged 2 commits into from
Dec 11, 2024

Conversation

Al4ise
Copy link
Collaborator

@Al4ise Al4ise commented Dec 9, 2024

Description by Korbit AI

What change is being made?

Add unprocessed orders to a tracking list upon order submission in the Alpaca broker integration.

Why are these changes being made?

Previously, orders that were submitted to Alpaca but not processed were not being tracked, potentially leading to discrepancies or missed updates. By appending such orders to the _unprocessed_orders list, we ensure more accurate tracking and handling of orders.

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

  • Remove orders from _unprocessed_orders after processing to avoid memory leaks and tracking inaccuracies.
Files scanned
File Path Reviewed
lumibot/brokers/alpaca.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
Readability and Maintainability
Asynchronous Processing
Design Patterns
Third-Party Libraries
Performance
Security
Functionality

Feedback and Support

@@ -447,6 +447,7 @@ def _submit_order(self, order):
order.set_identifier(response.id)
order.status = response.status
order.update_raw(response)
self._unprocessed_orders.append(order)
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 severity potentially major

Orders not removed from unprocessed orders list

Tell me more

What is the issue?
Orders are added to _unprocessed_orders but never removed, potentially causing memory leaks and tracking inaccuracies.

Why this matters
Orders will accumulate indefinitely in the _unprocessed_orders list, consuming memory and possibly leading to incorrect order tracking since orders that are completed or cancelled remain in the unprocessed list.

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

@grzesir grzesir merged commit f95160b into dev Dec 11, 2024
1 check passed
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