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
According to the gRPC docs for compression, when a server sends a response using an unrecognized/unsupported encoding the client MUST report the error with an internal error code. (See bullet 5 in the test cases section of that doc.)
Similarly, when a server sends a message where the envelope has the “compressed” bit set, but there is no encoding for the stream (or the encoding is “identity”), the recipient MUST fail with an internal error code.
The client in this package returns an unknown error in both of these situations instead of internal.
The text was updated successfully, but these errors were encountered:
According to the gRPC docs for compression, when a server sends a response using an unrecognized/unsupported encoding the client MUST report the error with an
internal
error code. (See bullet 5 in the test cases section of that doc.)Similarly, when a server sends a message where the envelope has the “compressed” bit set, but there is no encoding for the stream (or the encoding is “identity”), the recipient MUST fail with an
internal
error code.The client in this package returns an
unknown
error in both of these situations instead ofinternal
.The text was updated successfully, but these errors were encountered: