-
Notifications
You must be signed in to change notification settings - Fork 148
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
Get status_code from invocation details #158
Comments
@ericboucher I need more information here. What backoff decorator are you using? What is the function you are decorating? A minimal code example would help. |
Hi @bgreen-litl, this is our code at the moment to bypass this. And here is a link to the code https://github.com/MeltanoLabs/tap-github/blob/main/tap_github/client.py#L264
Ideally, we could get the response.status_code directly in |
You're only showing me the handler, not the declaration of backoff decorator, but it looks like you must be using the You've always been able to get the Exception instance in the backoff handlers, see the "Getting exception info" section in the README. The short version is use backoff is not tightly coupled to You also might want to look at the |
Makes sense, thanks a lot for these details @bgreen-litl :) |
When writing a
backoff_handler
, it would be very useful for us to have access to some information about the failed response.Currently, the availables details are as follows.
Would it be possible to add the Response.status_code? Or even maybe the full Response?
PS - Thanks for this awesome tool!
The text was updated successfully, but these errors were encountered: