Forward of the headers in the HTTPExceptions #227
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this update, the HTTP headers are available in the HTTPException and its subclasses. It exposes the response context. We have this need at Autodesk because we hit GitHub's secondary rate limit. We want to use the header details to configure an optimized retry policy when we hit this limit.
We hit some 429 from GitHub due to secondary rate limit. The way to handle that, following the GitHub guidance, is to check the headers headers, which the library blocks. This PR works on this.
related to
RateLimit.from_http()isNone#207