You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to extract the "details" portion of a gRPC error using Python as the client language. The core protobuf definition that I am basing the behavior on is documented here. Example client code block:
I was expected the details to be the extended content rather than the error message. Am I overlooking something obvious? Is this not supported in the Python client library?
The server-side code is written in go and looks something like this:
s:=status.New(codes.AlreadyExists, "dataset already exists for combination of subject and provenance")
ifs, err=s.WithDetails(res.VersionSets[0]); err!=nil {
logrus.Panicf("cannot add details to google.rpc.Status: %+v", err)
}
returnnil, s.Err()
The text was updated successfully, but these errors were encountered:
Hey! So I am actually working on adding details part of errors, it is work in progress. However you are in luck, since I have added python code samples - #15
I am trying to extract the "details" portion of a gRPC error using Python as the client language. The core protobuf definition that I am basing the behavior on is documented here. Example client code block:
I was expected the details to be the extended content rather than the error message. Am I overlooking something obvious? Is this not supported in the Python client library?
The server-side code is written in go and looks something like this:
The text was updated successfully, but these errors were encountered: