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
Now I was expecting to find the Something message attached in the metadata or similar field on the RpcError. But it's always empty. What I get is something like this RpcError{code: "ABORTED", name: "RpcError", message: "aborted", metadata: {}}
There might be other layers affecting the outcome of this like some Envoy setting or whatnot. Does anyone successfully use this feature or could try in their setup if it works?
The text was updated successfully, but these errors were encountered:
Oh, I see that metadata is empty. If you are using gRPC-web, make sure the headers are CORS allowlisted. If the header still does not show up, this might be a bug in this library, and I'd be interested in a confirmation.
Hi there! Great job with the library!
I am playing around and wanted to test a bit more complex gRPC errors.
Now I was expecting to find the
Something
message attached in the metadata or similar field on the RpcError. But it's always empty. What I get is something like thisRpcError{code: "ABORTED", name: "RpcError", message: "aborted", metadata: {}}
There might be other layers affecting the outcome of this like some Envoy setting or whatnot. Does anyone successfully use this feature or could try in their setup if it works?
The text was updated successfully, but these errors were encountered: