Uh oh!
There was an error while loading. Please reload this page.
feat: add support for 'error_info' - #307
Conversation
tseaver
left a comment
There was a problem hiding this comment.
All returns from _parse_grpc_error_details must return a 2-tuple.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Tres Seaver <tseaver@palladion.com>
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. ℹ️ Googlers: Go here for more info. |
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. ℹ️ Googlers: Go here for more info. |
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. ℹ️ Googlers: Go here for more info. |
tseaver
commented
Nov 9, 2021
@googlebot I consent. |
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. ℹ️ Googlers: Go here for more info. |
tseaver
commented
Nov 9, 2021
@atulep The CLA bot has (once again) lost its tiny mind. You'll need to remove the |
atulep
commented
Nov 10, 2021
Hey @tseaver, it seems to complain because email used in the commit "@palladion.com" is different than the one you used to sign CLA with. The docs suggest "If the email address does not match an email found, please ask the contributor to either add their new email address to their CLA or rebase their commits with their correct email address." Can you please do that? |
Uh oh!
There was an error while loading. Please reload this page.
summer-ji-eng
left a comment
There was a problem hiding this comment.
Left one comment, other than that, looks good to me. :)
tseaver
commented
Nov 10, 2021
The error message is incorrect -- all my commits in the |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
atulep
commented
Nov 10, 2021
I checked the internal dashboards, and it shows you signed CLA with a "@gmail.com" address. This is the official instruction I was told to follow:
I know you're an active contributor, so this is really weird to see an CLA issue. Can you share a similar issue from the past where a Googler manually removed the CLA label? Thank you. |
tseaver
commented
Nov 10, 2021
@tswast, @busunkim96 Can one of you please tag in on the manual CLA flip? |
vam-google
commented
Nov 10, 2021
@googlebot I fixed it. |
atulep
commented
Nov 15, 2021
@summer-ji-eng@tseaver - finally addressed your feedback. Thanks for your comments! |
Requested changes made in 331d6e3
tseaver
commented
Nov 16, 2021
@atulep the CLA flag has to be cleared again after pushing any commit, even a merge. |
atulep
commented
Nov 17, 2021
@tseaver I manually flipped the flag but it still blocks me from merging. |
software-dov
left a comment
There was a problem hiding this comment.
Looks good, just some nitpicking.
| if not self._error_info: | ||
| return None | ||
| return self._error_info.reason |
There was a problem hiding this comment.
Nit: we can simplify this to
returnself._error_info.reasonifself._error_infoelseNone| if not self._error_info: | ||
| return None | ||
| return self._error_info.domain |
There was a problem hiding this comment.
Same here: we can use conditional expressions
| if not self._error_info: | ||
| return None | ||
| return self._error_info.metadata |
| error_info = list( | ||
| filter( | ||
| lambda detail: detail.get("@type", "") | ||
| == "type.googleapis.com/google.rpc.ErrorInfo", | ||
| details, | ||
| ) | ||
| ) |
There was a problem hiding this comment.
Nit: it's more idiomatic to use list comprehensions than list and filter.
error_info_type="type.googleapis.com/google.rpc.ErrorInfo"error_info= [dfordindetailsifd.get("@type", "") ==error_info_type]atulep
commented
Nov 29, 2021
Closing this in favor of #315. |
Adds
error_infofield toGoogleAPICallError, as requested in #286.