-
Notifications
You must be signed in to change notification settings - Fork 324
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
Add rate limiting exceptions #695
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
@pragatimodi Since you are assigned to #666, would you be able to check this out? |
190b7c8
to
4ad0339
Compare
@jonathanedey I see you are mostly maintaining this repo now, is this something you could have a look at? |
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.
Hi @skion, This looks great. Thank you so much for your patience in getting this added!
This adds two exception types to enable users to detect rate limited calls which were previously swallowed and converted into a generic
InvalidArgumentError
, making it impossible to detect rate limiting situations and pass that information through to the end user.This is being discussed in #666.
I chose to inherit from the
ResourceExhaustedError
base exception, which seemed to make most sense.