ppkarwasz commented on code in PR #3501:
URL: https://github.com/apache/logging-log4j2/pull/3501#discussion_r2110315178
##
log4j-core/src/main/java/org/apache/logging/log4j/core/config/builder/api/MonitorResourceComponentBuilder.java:
##
@@ -0,0 +1,22 @@
+/*
+ * Licensed to the
MichaelMorrisEst commented on code in PR #3501:
URL: https://github.com/apache/logging-log4j2/pull/3501#discussion_r2114474331
##
log4j-core/src/main/java/org/apache/logging/log4j/core/config/builder/api/MonitorResourceComponentBuilder.java:
##
@@ -0,0 +1,22 @@
+/*
+ * Licensed
ppkarwasz commented on code in PR #3681:
URL: https://github.com/apache/logging-log4j2/pull/3681#discussion_r2113701902
##
log4j-core-test/src/test/java/org/apache/logging/log4j/core/util/internal/InternalLoggerRegistryTest.java:
##
@@ -0,0 +1,189 @@
+/*
+ * Licensed to the Apac
ppkarwasz opened a new pull request, #191:
URL: https://github.com/apache/logging-log4j-tools/pull/191
This change enables the same branch protection that was implemented in
`logging-log4j2`.
See apache/logging-log4j2#3582 and apache/logging-log4j2#3662
--
This is an automa
maedula commented on issue #250:
URL:
https://github.com/apache/logging-log4net/issues/250#issuecomment-2918581607
While thinking about it and to be a lil more precise for the condition where
incorrect overwriting log files happens if the logging process is being killed
and restarted. I'm
Class-New commented on issue #3697:
URL:
https://github.com/apache/logging-log4j2/issues/3697#issuecomment-2918395259
SizeBasedTriggeringPolicy的size大小限制为5k
5.9K common.85.l0g
6.2K common.86.l0g
3.2K common.87.log
--
This is an automated message from the Apache Git Service.
To
gdziadkiewicz commented on issue #250:
URL:
https://github.com/apache/logging-log4net/issues/250#issuecomment-2918617885
> While thinking about it and to be a lil more precise for the condition
where incorrect overwriting log files happens if the logging process is being
killed and restart
ppkarwasz opened a new pull request, #190:
URL: https://github.com/apache/logging-log4j-tools/pull/190
Previously, `SchemaGenerator` did not handle configuration attributes with
boxed types (e.g., `Integer`, `Boolean`), leading to their omission from the
generated XSD schema.
This up
jhl221123 commented on code in PR #3681:
URL: https://github.com/apache/logging-log4j2/pull/3681#discussion_r2113606606
##
log4j-core-test/src/test/java/org/apache/logging/log4j/core/util/internal/InternalLoggerRegistryTest.java:
##
@@ -0,0 +1,189 @@
+/*
+ * Licensed to the Apac
