Closed cmdjulian closed 5 months ago
There were numerous bugs in 0.3.0 that I should have filed but instead just fixed. Let me check to see and will shortly get back to you.
Confirmed. I know it worked at one point but apparently I recently broke it when I regenerated code and the unit test did not test the throwable (how embarrassing). The loggers are code generated.
I'm in the works of having a much more extensive testing suite.
Pumping out a release now. I guess the static level loggers were not being tested for the throwable non marker calls.
@cmdjulian 0.4.0 should be in Maven central (or at least it will be propagated shortly).
Thanks a ton for reporting this. By 0.5.0 we should be approaching less experimental and the API will stabilize as well.
Thanks for rainbowgum
! 👍🏻
Not quite sure why, but only the first log statement gets actually logged, the other two invocations don't print anything. Am I doing something wrong here?
It seems like this is for all logger methods which do include a
Throwable
in their signature. The logger faced I'm using on top ofRainbowgum
is kotlin-logging which relies onslf4j
. For other loggers likelogback
everything works as it should.I created a small reproducer: logger.zip