Handle exception in servers sendMessage better (v1.58 backport of #10513)#10520
Merged
larry-safran merged 2 commits intogrpc:v1.58.xfrom Aug 29, 2023
Merged
Conversation
…o stream and allow multiple closes (grpc#10513) * Use internalClose instead of close when sendMessage has a RuntimeException. * Change argument to internalClose to a Throwable instead of a Status. * Rename internalClose to handleInternalError
YifeiZhuang
approved these changes
Aug 25, 2023
Force rebuild
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When server side sendMessage throws a RuntimeException, call
handleInternalError()(previously internalClose) rather than close. This will log a warning.rename internalClose to handleInternalError and change argument from a Status to a Throwable.
Allows more debugging of #10500
Backport of #10513