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

polygon max retry bug fix #482

Merged
merged 1 commit into from
Jul 4, 2024
Merged

polygon max retry bug fix #482

merged 1 commit into from
Jul 4, 2024

Conversation

grzesir
Copy link
Contributor

@grzesir grzesir commented Jul 4, 2024

No description provided.

Copy link
Contributor

korbit-ai bot commented Jul 4, 2024

My review is in progress 📖 - I will have feedback for you in a few minutes!

@grzesir grzesir merged commit 2a8cdd1 into dev Jul 4, 2024
1 check passed
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.

I have reviewed your code and found 2 potential issues. To discuss my individual comments that I have added, tag me in replies using @korbit-ai.


Please react with a 👍 to my comments that you find helpful and a 👎 to those you find unhelpful - this will help me learn and improve as we collaborate.

@@ -548,10 +552,11 @@ def _get(self, *args, **kwargs):
try:
return super()._get(*args, **kwargs)

except MaxRetryError:
except MaxRetryError as e:
Copy link
Contributor

Choose a reason for hiding this comment

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

category Naming

In the exception handling block for MaxRetryError, the variable name 'e' is not descriptive. Consider renaming it to 'max_retry_error' to provide more context about what it represents.

@@ -5,7 +5,7 @@

setuptools.setup(
name="lumibot",
version="3.5.10",
version="3.5.11",
Copy link
Contributor

Choose a reason for hiding this comment

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

category Documentation

I noticed that you've updated the version of the software package in the setup.py file, but this change is not reflected in the README.md file. It's important to keep the README.md file up-to-date with the latest version of the software package. Could you please update the README.md file to reflect this change?

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.

None yet

1 participant