-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
proto: no slice oenc for *reflect.rtype = []*reflect.rtype #551
Comments
Is this log output, or is it included in the actual output of the server? |
It goes to the server's stderr here. |
Hi! Oh yeah, was wondering about this the other day too... Nice one with Also the protobuf tag would need to contain But actually, if
And then by the way it would indeed be nice to unify with the stream errors. :) |
As advised by @itizir in the discussion of grpc-ecosystem#551. However, I've gone with the minimal change to make the error go away, I haven't introduced a proper, generated protobuf definition. Also, I've noticed our error body message there looks suspiciously like Status[1], except for the field name "Error" vs "Message". Fixes grpc-ecosystem#551. [1]: https://github.com/google/go-genproto/blob/2b5a72b8730b0b/googleapis/rpc/status/status.pb.go#L83-L93 Signed-off-by: Stephan Renatus <srenatus@chef.io>
As advised by @itizir in the discussion of #551. However, I've gone with the minimal change to make the error go away, I haven't introduced a proper, generated protobuf definition. Also, I've noticed our error body message there looks suspiciously like Status[1], except for the field name "Error" vs "Message". Fixes #551. [1]: https://github.com/google/go-genproto/blob/2b5a72b8730b0b/googleapis/rpc/status/status.pb.go#L83-L93 Signed-off-by: Stephan Renatus <srenatus@chef.io>
As advised by @itizir in the discussion of grpc-ecosystem#551. However, I've gone with the minimal change to make the error go away, I haven't introduced a proper, generated protobuf definition. Also, I've noticed our error body message there looks suspiciously like Status[1], except for the field name "Error" vs "Message". Fixes grpc-ecosystem#551. [1]: https://github.com/google/go-genproto/blob/2b5a72b8730b0b/googleapis/rpc/status/status.pb.go#L83-L93 Signed-off-by: Stephan Renatus <srenatus@chef.io>
Hey there
With the introduction of error details in JSON responses, #515, we've also gotten us an extra line of output for every JSON error encoding process:
...irregardless of whether this error contains error details or not. Looking back at the PR's CI run, it has been in there right from the start.
The line comes from
proto.(*Properies).setEncAndDec
, called viajsonpb.jsonProperties
.However, since the tests pass, it seems like whatever is happening there wouldn't have to happen?
Have you got any idea how to get rid of that?
(While looking into this, I've also started wondering why grpc-gateway's error details don't have
@type
fields, but that's a different matter. But would you think they should have them?)The text was updated successfully, but these errors were encountered: