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

Bug: API implementations can leak uncaught exceptions #165

Closed
abeltrano opened this issue Feb 23, 2024 · 0 comments · Fixed by #168 or #166
Closed

Bug: API implementations can leak uncaught exceptions #165

abeltrano opened this issue Feb 23, 2024 · 0 comments · Fixed by #168 or #166
Labels
bug Something isn't working

Comments

@abeltrano
Copy link
Contributor

Describe the bug
The API implementations currently do not take care to prevent leaking exceptions outside the API boundary.

Steps To Reproduce
N/A

Expected behavior

  • No exceptions should ever leak the API boundary, and every gRPC function implementation must always return a value such that the remote client always receives a response.

Actual behavior

  • Uncaught exceptions can crash the server and cause the client to time out waiting for a response.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant