github-actions[bot] merged PR #187:
URL: https://github.com/apache/logging-log4j-tools/pull/187
--
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: notifica
rschmitt commented on PR #3675:
URL: https://github.com/apache/logging-log4j2/pull/3675#issuecomment-2898961509
What should I do about these baseline failures?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL ab
LeadAssimilator opened a new issue, #247:
URL: https://github.com/apache/logging-log4net/issues/247
Using %date/%utcdate with ABSOLUTE and ISO8601 causes one of the dates to
not change:
```xml
```
yields:
```
06:48:26,722 2025-05-22 06:48:26,722
06:48:
swebb2066 merged PR #500:
URL: https://github.com/apache/logging-log4cxx/pull/500
--
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] commented on PR #3681:
URL: https://github.com/apache/logging-log4j2/pull/3681#issuecomment-2899006129
Job
Requested goals
Build Tool Version
Build Outcome
Build Scan®
build-
ctubbsii commented on issue #3100:
URL:
https://github.com/apache/logging-log4j2/issues/3100#issuecomment-2899363555
> * Rollover events currently don't emit anything above `DEBUG`, even though
they’re important for understanding log rotation behavior.
By rollover, do you mean reconf
garydgregory commented on issue #3100:
URL:
https://github.com/apache/logging-log4j2/issues/3100#issuecomment-2899433591
Here's another general logging pickle that somewhat applies to status
logging. There are events that you may care about depending on _how_ and _when_
you view them.
jhl221123 opened a new pull request, #3681:
URL: https://github.com/apache/logging-log4j2/pull/3681
This pull request addresses issue #3430 by implementing a mechanism to
expunge stale entries in `InternalLoggerRegistry`.
It builds upon PR #3474 and incorporates feedback from @vy and
