swebb2066 merged PR #432:
URL: https://github.com/apache/logging-log4cxx/pull/432
--
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: notifications-unsubscr
github-actions[bot] merged PR #227:
URL: https://github.com/apache/logging-log4j-samples/pull/227
--
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: notifi
ppkarwasz commented on PR #3235:
URL: https://github.com/apache/logging-log4j2/pull/3235#issuecomment-2496335794
> Does this mean a 2.24.3 is around the corner?
@garydgregory, I would wait a couple of weeks to see if other bugs are
reported, but, yes, I think we should release a `2.24
garydgregory commented on PR #3235:
URL: https://github.com/apache/logging-log4j2/pull/3235#issuecomment-2496322604
Hi all,
Does this mean a 2.24.3 is around the corner?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitH
ppkarwasz commented on issue #3234:
URL:
https://github.com/apache/logging-log4j2/issues/3234#issuecomment-2495949641
@AlexProgrammerDE,
Nice catch! :100:
#3235 should fix it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on t
ppkarwasz opened a new pull request, #3235:
URL: https://github.com/apache/logging-log4j2/pull/3235
The `InternalLoggerRegistry` implementation introduced in version `2.24.2`
did not return a copy of the registry, when
`InternalLoggerRegistry.getLoggers()` was called. This could lead to a
