Per this <https://stackoverflow.com/a/48750825/969755> SO post and some messages in this group, there looks to be agreement on and progress towards enabling richer gRPC error reporting via google.rpc.Status <https://cloud.google.com/apis/design/errors#error_model> as a replacement for io.grpc.Status <https://github.com/grpc/grpc/blob/master/src/proto/grpc/status/status.proto> .
But nowhere on the gRPC website <https://grpc.io/> including the error handling <https://grpc.io/docs/guides/error/> page is this mentioned, which seems a major omission -- it takes a fair bit of googling to discover this. For the sake of other developers looking to adopt gRPC and needing to support richer error reporting, will somebody update that page to talk about this? Similarly, the use of the grpc-status-details-bin header/metadata key should be added to the gRPC over HTTP2 <https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md> spec. (flagged as "experimental" or something if needed). We're using akka-grpc and until I asked about supporting google.rpc.Status <https://cloud.google.com/apis/design/errors#error_model> yesterday it wasn't even on their radar. It's really hard to tell where this stands in terms of official library support too. It'd be really helpful to list/track official library support status for this on the error handling <https://grpc.io/docs/guides/error/> page or somewhere else on the gRPC website <https://grpc.io/>. Speaking of library support status, is this currently available, or being worked on, for the following languages? Java JS (grpc-web) Objective C thanks, Chris -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/6c1642af-23ce-48ab-9bf0-260897a6ca3d%40googlegroups.com.
