github-actions[bot] commented on PR #3650:
URL: https://github.com/apache/logging-log4j2/pull/3650#issuecomment-2856048962
Job
Requested goals
Build Tool Version
Build Outcome
Build Scan®
build-
ppkarwasz merged PR #3645:
URL: https://github.com/apache/logging-log4j2/pull/3645
--
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-unsubsc
ppkarwasz commented on PR #3645:
URL: https://github.com/apache/logging-log4j2/pull/3645#issuecomment-2855906947
@magicwerk,
Thanks, I'll merge it as soon as the required tests pass.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log o
magicwerk commented on code in PR #3645:
URL: https://github.com/apache/logging-log4j2/pull/3645#discussion_r2076213380
##
log4j-perf-test/src/main/java/org/apache/logging/log4j/message/ParameterFormatterBenchmark.java:
##
@@ -81,4 +95,38 @@ private static int latencyParams(fina
jhl221123 opened a new pull request, #3650:
URL: https://github.com/apache/logging-log4j2/pull/3650
This pull request addresses issue #3206, which could lead to a
`NullPointerException` when using the shorthand notation for the root logger
(e.g., rootLogger = INFO) in `log4j2.properties` wi
ppkarwasz commented on PR #175:
URL:
https://github.com/apache/logging-log4j-tools/pull/175#issuecomment-2854452265
Apparently there is still one required change: the workflows in
`.github/workflows` must be migrated from `@rel/11.3.0` to `@rel/12.1.0`.
--
This is an automated message fr
alan0428a commented on PR #175:
URL:
https://github.com/apache/logging-log4j-tools/pull/175#issuecomment-2854211268
@ppkarwasz fixed. Thanks.
--
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
