-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
RetryErrors obscure actual errors - PubSub API #3905
Comments
@jonparrott Dropping your name on this since your fixes to |
I hit the same problem with the Cloud Spanner API. Specifically I was getting an INVALID_ARGUMENT trying to create an instance but no useful information about what was invalid. I ran the same command using gcloud and got a very helpful error message.
I'm guessing the problem is in the gRPC layer and so all APIs will be affected. Would it make sense to change the title of the issue? |
The new exception handling code will only raise a Basically, this won't be an issue once we get gapic to use the new error code. |
For near-future historians, this is how this programmer did meaningful error handling: from google.gax.errors import RetryError
from grpc import StatusCode
try:
leap_without_looking()
except RetryError as exc:
if exc.cause.code() is not StatusCode.ALREADY_EXISTS:
raise |
@jonparrott May I ask if this is fixed now? I'm only asking because I think it might have been fixed... |
Yes gax is dead for pubsub |
Similar to #3083, #3900
The text was updated successfully, but these errors were encountered: