-
Notifications
You must be signed in to change notification settings - Fork 181
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
client: pass the provided ctx to backoff.RetryNotify #146
base: master
Are you sure you want to change the base?
Conversation
If we hit a connection error in any of the ..WithContext functions, we end up blocked in the backoff.RetryNotify loop. This loop can use a context, but it needs to be bound to the BackOff provided when RetryNotify is called. Added a test case `TestSubscribeWithContextAbortRetrier` to demonstrate the problem and verify the fix. Fixes r3labs#131.
@purehyperbole mind having a look at this one? |
@merlinran mind having a look? |
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.
This looks like a neat solution which solves the problem it intended to solve. I'm not part of the org so still need the members to decide if merge or not.
Ah, gotcha, well, thanks for the review just the same! |
bump @purehyperbole 😄 |
@purehyperbole would appreciate your review to get this one merged if it looks ok. |
@purehyperbole could you please have a look at merging this? |
@purehyperbole Is this package still maintained? @reidjc As the only other publicly visible member of the r3labs organization, can you comment on the status of this repo? |
If we hit a connection error in any of the ..WithContext functions, we end up blocked in the backoff.RetryNotify loop. This loop can use a context, but it needs to be bound to the BackOff provided when RetryNotify is called.
Added a test case
TestSubscribeWithContextAbortRetrier
to demonstrate the problem and verify the fix.Fixes #131.