gRPC: error.type for gRPC cannot have different semantics in server and client

[mbissa]

Area(s)

No response

What's the problem?

The way gRPC is designed currently, all non OK statuses are considered errors. There is no way to determine if something which is non-OK is actually an OK for server.

Describe the solution you'd like

Just keep the everything non-OK as an error.

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}