-
-
Notifications
You must be signed in to change notification settings - Fork 174
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
Extend RedisSettings to include redis Retry Helper settings #387
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #387 +/- ##
==========================================
+ Coverage 96.27% 96.38% +0.10%
==========================================
Files 11 11
Lines 1074 1078 +4
Branches 209 209
==========================================
+ Hits 1034 1039 +5
Misses 19 19
+ Partials 21 20 -1
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
The tests has been fixed in #382, so don’t worry about those failing pipelines on some Python versions for now. As you can see from the codecov bot above, this repo strive to have 100% codecov. Would love if you added tests for these settings. |
@JonasKs, added some tests which improved coverage. Still one partial, but might be from testing failures? |
I'll try to review again this weekend / early next week 🙇♂️ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! 😊
Thanks for taking a look, just pushed a change for the Exception type. We've been using the above changes in our systems and everything has been working as expected so far. A heads up I'll be offline from the first few weeks of February, so if anything comes up that's the reason for any radio silence on my end. Thanks again! |
Thanks for the PR and for testing in your environment! I'd also recommend double checking that maintainers can edit your PR, in case Samuel finds time to review/release while you're gone. 😊 |
Hi there, is it possible to merge this fix to main branch? |
Hello- thanks for the fix! Any thoughts on merging this? Would be great to have for my use cases! 🙇 |
Workaround while waiting for PR merge. Initialize ArqRedis with a connection pool including your retry helper.
redis_pool parameter can be found in docs here: Example custom backoff class, we are using for more granular access and logging but you can use any redis retry helper
docs on redis retry helpers: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks so much for this, sorry for the long delay.
@JonasKs @Kludex we might be able to use redis's retry logic to remove our retry stuff - https://github.com/samuelcolvin/arq/blob/94cd8782b4f0764a17962186a349d32125cb98e3/arq/connections.py#L258-L286 |
|
proposed fix for #386