Jörn Huxhorn

You should replace ```java String className = callingClass.getName().split("\\$")[0]; ``` with ```java String className = callingClass.getName(); int dollarIndex = className.indexOf('$'); if(dollarIndex > -1) { className = className.substring(0, dollarIndex); } ``` It's...

That helped, thanks! Also for the fast response! Building works now but executing the resulting wasm file using `wasmtime` fails with the following error: ``` The application panicked (crashed). Message:...

I think so, yes. Is anything broken with current version of Lilith and the new logback/slf4j versions?

How would I create a `raise` `Expr` in Rust? The `Expr` type for that parameter is part of my problem in understanding the API. Shouldn't this be an `enum` instead?...

I think I'm lost again regarding understanding what's going on. From the Python docs, I thought I understood it the following way: If you have a pattern like `"%Y-%m-%d %H:%M"`...

One could do something similar with the User column and only print it if at least one file has a different user than the current user.

I'd suggest to add this to the [MavenUsage](https://github.com/policeman-tools/forbidden-apis/wiki/MavenUsage) page of the Wiki below the `failOnUnsupportedJava` property: ```xml true ``` It may make sense to also mention the existence of this...

I'm not a fan of this change. The [InvalidSlf4jMessageFormat PMD rule](https://pmd.github.io/latest/pmd-java/rules/java/logging-java.html#InvalidSlf4jMessageFormat) would also barf.

Not really. It looks like Logstash is using the (AFAIK) undocumented feature that superfluous arguments aren't dropped by Logback but are instead left in the event. I once suggested that...

We had the same issue and addressed it by writing our own `NestedMDCClosable`, essentially wrapping the `MDC`. This should also be taken into account for the `MDCAmbit` proposal in #377...