Re: [PR] Fix Scala 3 macros for Message [logging-log4j-scala]

2024-02-01 Thread via GitHub
vy commented on PR #40: URL: https://github.com/apache/logging-log4j-scala/pull/40#issuecomment-1920856415 @ppkarwasz, shared Dotty compiler release schedules point to the end of January and sometime in February, nothing concrete. We released `13.0.0` with the aforementioned

Re: [PR] Fix Scala 3 macros for Message [logging-log4j-scala]

2024-02-01 Thread via GitHub
ppkarwasz commented on PR #40: URL: https://github.com/apache/logging-log4j-scala/pull/40#issuecomment-1920740867 @kojunho7, Dotty compiler 3.3.2 (cf. [this thread](https://contributors.scala-lang.org/t/scala-3-3-2-release-date/6422)) and 3.4.0 (cf. [this

Re: [I] %tid always print the same ID if async logging is used (logging-log4j2)

2024-02-01 Thread via GitHub
ppkarwasz commented on issue #2258: URL: https://github.com/apache/logging-log4j2/issues/2258#issuecomment-1920768637 @baldpate, Thank you for the report, we'll look into it. Could you also try with a **full** async configuration? This requires you to add: ```

Re: [I] %tid always print the same ID if async logging is used (logging-log4j2)

2024-02-01 Thread via GitHub
ppkarwasz commented on issue #2258: URL: https://github.com/apache/logging-log4j2/issues/2258#issuecomment-1921256723 No, it is async. When we talk about async loggers, we are actually talking about two **different** implementations: -

Re: [I] %tid always print the same ID if async logging is used (logging-log4j2)

2024-02-01 Thread via GitHub
baldpate commented on issue #2258: URL: https://github.com/apache/logging-log4j2/issues/2258#issuecomment-1921002400 Hi @ppkarwasz, With AsyncLoggerContextSelector the thread ID seems normal. But I cannot find the `Starting AsyncLogger disruptor` log with ``` ``` With

Re: [I] Remove `ThreadLocals.enable` property in `main` (logging-log4j2)

2024-02-01 Thread via GitHub
vy closed issue #2105: Remove `ThreadLocals.enable` property in `main` URL: https://github.com/apache/logging-log4j2/issues/2105 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.

[jira] [Updated] (LOG4J2-3680) Some log events are no longer serialized correctly

2024-02-01 Thread Peter De Maeyer (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter De Maeyer updated LOG4J2-3680: Description: We noticed a regression between 2.21.1 and 2.22.0 in the serilialization of

[jira] [Assigned] (LOG4J2-3680) Some log events are no longer serialized correctly

2024-02-01 Thread Volkan Yazici (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici reassigned LOG4J2-3680: - Assignee: Volkan Yazici > Some log events are no longer serialized correctly >

[jira] [Assigned] (LOG4J2-3680) Some log events are no longer serialized correctly

2024-02-01 Thread Volkan Yazici (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici reassigned LOG4J2-3680: - Assignee: Piotr Karwasz (was: Volkan Yazici) > Some log events are no longer

[jira] [Updated] (LOG4J2-3680) Some log events are no longer serialized correctly

2024-02-01 Thread Peter De Maeyer (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter De Maeyer updated LOG4J2-3680: Description: When we updated from 2.20.0 to 2.22.1 (I had to pick 2.22.0 in the *Affects

[jira] [Updated] (LOG4J2-3680) Some log events are no longer serialized correctly

2024-02-01 Thread Peter De Maeyer (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter De Maeyer updated LOG4J2-3680: Summary: Some log events are no longer serialized correctly (was: Some log events are no

[jira] [Created] (LOG4J2-3680) Some log events are no longer serialized correctly.

2024-02-01 Thread Peter De Maeyer (Jira)
Peter De Maeyer created LOG4J2-3680: --- Summary: Some log events are no longer serialized correctly. Key: LOG4J2-3680 URL: https://issues.apache.org/jira/browse/LOG4J2-3680 Project: Log4j 2

Re: [PR] Use GCC recommended symbol visibility in the next ABI version [logging-log4cxx]

2024-02-01 Thread via GitHub
swebb2066 merged PR #340: URL: https://github.com/apache/logging-log4cxx/pull/340 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Bump org.apache.maven.plugins:maven-jlink-plugin from 3.1.0 to 3.2.0 [logging-log4j-samples]

2024-02-01 Thread via GitHub
dependabot[bot] opened a new pull request, #112: URL: https://github.com/apache/logging-log4j-samples/pull/112 Bumps [org.apache.maven.plugins:maven-jlink-plugin](https://github.com/apache/maven-jlink-plugin) from 3.1.0 to 3.2.0. Release notes Sourced from

Re: [PR] Optimize relocation processing when loading liblog4cxx.so [logging-log4cxx]

2024-02-01 Thread via GitHub
swebb2066 merged PR #341: URL: https://github.com/apache/logging-log4cxx/pull/341 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [I] Logs generated using SLF4J's addKeyValue method do not log correctly. (logging-log4j2)

2024-02-01 Thread via GitHub
ppkarwasz commented on issue #1813: URL: https://github.com/apache/logging-log4j2/issues/1813#issuecomment-1923070109 @rgoers, What about the solution proposed in [this SO question](https://stackoverflow.com/a/77917282/11748454)? -- This is an automated message from the Apache