Skip to content
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

GRPC client interceptor: check if response has exception before trying to access result #948

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AmicoJoules
Copy link

Small fix on the callback set by the grpc client interceptor. Trying to access the result raises the Future exception which can be problematic for asynchronous grpc calls.

This PR addresses issue #790

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@AmicoJoules
Copy link
Author

@googlebot I fixed it.

@AmicoJoules AmicoJoules force-pushed the client-interceptor-fix branch from 8cf0128 to 883e14c Compare August 26, 2020 19:56
@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@AmicoJoules AmicoJoules changed the title Check if response has exception before trying to access result GRPC client interceptor: check if response has exception before trying to access result Aug 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants