Volkan Yazıcı

~@tmmlsBE, Log4j doesn't support native image compilation out-of-the-box currently, see [LOG4J2-2649](https://issues.apache.org/jira/browse/LOG4J2-2649). You need to manually provide the necessary reachability metadata, which pretty much depends on your Log4j configuration. I guess...

Instead adding compression support to ``, we better create a wrapper layout that compresses the output of another layout. This issue has already been discussed in [LOG4J2-3023](https://issues.apache.org/jira/browse/LOG4J2-3023). @der-eismann, would you...

@ppkarwasz, could you explain how we can use ``? Do you suggest a maintainer creating a personal account and occasionally checking the report?

@PassiveIncomeMachine, could you share the following information too, please? 1. A complete stack trace (pointing to some line numbers in the `org.apache.logging.log4j` package, etc.) 2. `Layout.json` file For the record,...

@PassiveIncomeMachine, 1. I am still missing a stack trace. **Please send a complete stack trace.** 2. [The `TPLayout.json` you shared](https://github.com/apache/logging-log4j2/files/15372262/TPLayout.json) contains a custom resolver: `humanMessage`. Can this be our smoking...

I would be in favor of creating a new `log4j-config-xml` module. A very big part of our users use `log4j2.yaml` and `log4j2.properties`. When they migrate to Log4j 3, they will...

I wrote JTLs `Uris` class you mentioned before JTL became a part of the Log4j. Hence, I can totally relate to the absence of this resource loading mechanism and I...

If I interpret [code](https://github.com/scalaz/scalaz-zio/blob/master/core/shared/src/main/scala/scalaz/zio/Fiber.scala) right, scalaz-zio's `Fiber`s are yet another wrapper for async callback composition ala Rx. I could not see any continuation support, which is the case for all...

Would you mind sharing the JDK and OS details as well, please?

@nqzero, I believe 527b570 and 929a898 address the Quasar Fiber and Java Thread cases, respectively. Would you mind verifying, please?