[GR-52790] Print stack trace of UserException causes. #9140
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.
In case a UserException has a cause attached, print its stack trace right after all messages to provide users with more diagnostic info.
An example where this is useful is a failing Feature. Currently, the output would look like this:
This PR makes the stack trace of the exception thrown in the feature available to the user:
(note, the internal exception is only visible because I ran this with
-H:+ReportExceptionStackTraces).In addition, the PR also makes sure errors and stack traces are printed consistently to stdout.