Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cardinaltiy violation in stream interface implementation #8119

Open
eshitachandwani opened this issue Feb 25, 2025 · 0 comments · May be fixed by #8120
Open

Cardinaltiy violation in stream interface implementation #8119

eshitachandwani opened this issue Feb 25, 2025 · 0 comments · May be fixed by #8120

Comments

@eshitachandwani
Copy link
Member

There are 2 issues :

  1. 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.

  2. 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 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant