-
Notifications
You must be signed in to change notification settings - Fork 133
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
Exception information is lost #372
Comments
At least, print SomeException to stdout when |
Could you share a minimal repro (or even better, a PR with a test case)?
…On Fri, 9 Feb 2024 at 16:17, Yuriy Syrovetskiy ***@***.***> wrote:
At least, print SomeException to stdout when verbose is on.
—
Reply to this email directly, view it on GitHub
<#372 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNBDKCN6BVC6BE6OVIBQH3YSY4WZAVCNFSM6AAAAABDBUA6ZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWGEYTCNBZGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@cblp I agree we could be logging and not dropping information in handlers (PRs welcome!) I don't agree with the assessment re. unhandledExceptionHandler because there are effects outside ActionT as well. |
@cblp good point about |
closed by #374 |
When any unknown exception happens, someExceptionHandler catches it and drops all information.
So I don't know how to put it in log to investigate. If it's possible please tell how.
Also, unhandledExceptionHandler has no sense because
scottyExceptionHandler
already caught allScottyException
s.The text was updated successfully, but these errors were encountered: