Repository navigation
TIKA-5010: tika-grpc reads parse-context timeout-limits and closes in… - #3448
Merged
Merged
Conversation
…terrupted calls with UNAVAILABLE
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…terrupted calls with UNAVAILABLE
This pulls out fixes to v1 made on the v2 PR: #2961
I intentionally dropped the stacktrace trimming. That should be a separate PR that adds a new option for ExceptionReporting/parse-context.exception-reporting. To my mind, the message is often more sensitive than the stack trace. We should discuss on a separate issue if that's still needed.