juliuszsompolski commented on PR #48037: URL: https://github.com/apache/spark/pull/48037#issuecomment-2483356362
> Instead of adding them to the suppressed field repeatedly, how about enrolling them in the stack traces of the current exception? The gist is that we want two stack traces: - the one from the original execution when the exception happened - the one from the current execution, that retrieved the exception. The first one is in suppressed exception. The second one is already stitched into the stack trace of the rethrown exception. The third one (with TRY_WITH_CALLER_STACKTRACE_TRY_STACKTRACE) was only needed internally to do the stitching, and I remove it in https://github.com/apache/spark/pull/48882 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
