feat(tonic-types): add ability to extract rich error details from google.rpc.Status
#1430
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.
Motivation
The tonic-types crate allows for extracting rich error details from a
tonic::Status
through theStatusExt
trait. It does this by decoding the bytes returned bytonic::Status
into agoogle.rpc.Status
. However, it does not allow for extracting the error details directly from agoogle.rpc.Status
instance.This can present a problem if a message contains an internal
google.rpc.Status
value, which seems to be fairly common on some GCP bidi streams. Example message:Solution
From
impls for converting between types defined in "std_messages" and the generated protobuf types.StatusExt
functionality forpb::Status