You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that log.error(msg, cause = someThrowable) doesn't actually use the throwable to present a meaningful message: neither the throwable's message nor the stack trace appear in logs by default.
Example (you might as well construct an exception yourself, but I relied on a good old NPE here):
Edit: I have made a PR for a quick&dirty change that would fix this.
I personally think this is a critical bug.
It has made me reluctant to use weaver when it would otherwise be a great fit because I can't be sure that I will be able to see what exceptions caused my code to fail unless I rethrow them. And rethrowing every exception is not an option.
This issue was copied over from: disneystreaming/weaver-test#639
It was opened by: kubukoz
It appears that
log.error(msg, cause = someThrowable)
doesn't actually use the throwable to present a meaningful message: neither the throwable's message nor the stack trace appear in logs by default.Example (you might as well construct an exception yourself, but I relied on a good old NPE here):
Actual output on
sbt test
:I'd expect to see the exception message and stack trace somewhere in the logs.
Versions affected: tried 0.8.1 and a local snapshot of the latest main,
0.8.1+35-b03d8212-SNAPSHOT
.The text was updated successfully, but these errors were encountered: