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
If we have a client streaming RPC , and the server doesn't send a message before returning status OK we expect an cardinality violation error and and INTERNAL status code , but currently we receive EOF if this happens.
If we have a client streaming RPC and the server calls a Recv() after a SendAndClose() we should get an status error code INTERNAL error code , but instead , we get status OK .
The text was updated successfully, but these errors were encountered:
There are 2 issues :
If we have a client streaming RPC , and the server doesn't send a message before returning status
OK
we expect an cardinality violation error and andINTERNAL
status code , but currently we receiveEOF
if this happens.If we have a client streaming RPC and the server calls a
Recv()
after aSendAndClose()
we should get an status error codeINTERNAL
error code , but instead , we get statusOK
.The text was updated successfully, but these errors were encountered: