Graal optimizations may break uberjar running about timbre HOT 6 OPEN

@TuggyNE Hi there, thanks for the report!

Requesting a bit more info please-

• What SLF4J adapter are you using? Could you please link me to it?
• Have you tried clearing all your build artifacts?
• Besides updating Timbre and Tufte, did you update anything else? E.g. JVM, Graal options, etc.

Thanks!

from timbre.

What SLF4J adapter are you using? Could you please link me to it?

https://github.com/fzakaria/slf4j-timbre

Have you tried clearing all your build artifacts?

Yes, but it doesn't help. (I did confirm it's not architecture or OS-dependent, though.)

Besides updating Timbre and Tufte, did you update anything else? E.g. JVM, Graal options, etc.

Nope, totally routine build. (I don't actually use GraalVM NI for anything on this project, it's just a plain uberjar.)

Thanks!

You're welcome, and thanks for the quick reply!

from timbre.

Can you share the version of Timbre that were you upgrading from? (May be helpful to pinpoint when an issue was introduced).

From your stacktrace, it looks to me like the problem might be with the appender, thought it's not immediately obvious to me what change/s might have caused trouble.

It looks like it could be a subtle unexpected side effect of recent changes to optimize GraalVM builds.

That change only affects unit tests, so I don't believe should affect your build.

I'd recommend opening an issue with slf4j-timbre. That project's maintainer can maybe more easily identify the problem from the stacktrace. If it turns out there was some kind of regression on Timbre's side, or if there's something I can do from Timbre's side to workaround the problem - I'll of course get right on it.

In the meantime am hoping they might be able to provide some guidance.

from timbre.

Relatedly, have also just opened fzakaria/slf4j-timbre#71

from timbre.

Thanks for bringing this up @TuggyNE!

Am I to understand that slf4j-timbre previously worked correctly under GraalVM? (I remember someone trying this out a while ago, but I don't recall the outcome.)

I'll aim to incorporate GraalVM into slf4j-timbre's integration tests so we can figure out any problems and avoid regressions.

from timbre.