notifications  

Messages by Thread

• Re: [PR] Bump com.google.guava:guava from 25.1-jre to 33.7.1-jre in /log4j-cassandra [logging-log4j2] via GitHub
• Re: [PR] Bump org.xerial.snappy:snappy-java from 1.1.10.8 to 1.1.10.9 in /log4j-cassandra [logging-log4j2] via GitHub
• [I] CronTriggeringPolicy with evaluateOnStartup="true" can overwrite logs [logging-log4j2] via GitHub
• [PR] Fix CronTriggeringPolicy with evaluateOnStartup=true overwriting logs (#4439) [logging-log4j2] via GitHub
• Re: [PR] Read header and footer if available [logging-flume] via GitHub
• [PR] Improve Configurator reference documentation [logging-log4cxx] via GitHub
• [PR] Fix/file extension bug [logging-flume] via GitHub
• [PR] Add support for JSON and YAML configurations [logging-flume] via GitHub
• [PR] Align Cassandra ASM dependency with JNR for Maven 4 [logging-log4j2] via GitHub
• Re: [I] Migrate to Maven 4 [logging-log4j2] via GitHub
• [PR] Test global Nashorn script filtering [logging-log4j-samples] via GitHub
  • Re: [PR] Test global Nashorn script filtering [logging-log4j-samples] via GitHub
• [PR] Prevent recursive JUL enablement checks [logging-log4j2] via GitHub
  • Re: [PR] Prevent recursive JUL enablement checks [logging-log4j2] via GitHub
  • Re: [PR] Prevent recursive JUL enablement checks [logging-log4j2] via GitHub
  • Re: [PR] Prevent recursive JUL enablement checks [logging-log4j2] via GitHub
• [PR] Migrate remaining log4j-api-test unit tests to JUnit 5 [logging-log4j2] via GitHub
  • Re: [PR] Migrate remaining log4j-api-test unit tests to JUnit 5 [logging-log4j2] via GitHub
• Re: [I] StackOverflow in `ScriptFilter` if scripting engine uses logging [logging-log4j2] via GitHub
• [PR] Make Log4cxx background threads identifiable on Linux [logging-log4cxx] via GitHub
  • Re: [PR] Make Log4cxx background threads identifiable on Linux [logging-log4cxx] via GitHub
• [PR] IAppender.Name does not uniquely identify an appender #340 (logging-log4net) via GitHub
  • Re: [PR] IAppender.Name does not uniquely identify an appender #340 (logging-log4net) via GitHub
• [I] IAppender.Name doc says the name "uniquely identifies the appender", but nothing enforces uniqueness (logging-log4net) via GitHub
  • Re: [I] IAppender.Name doc says the name "uniquely identifies the appender", but nothing enforces uniqueness (logging-log4net) via GitHub
• [PR] Fix size-only backup scan for prefix siblings (logging-log4net) via GitHub
  • Re: [PR] Fix size-only backup scan for prefix siblings (logging-log4net) via GitHub
• [I] RollingFileAppender counts unrelated prefix siblings as size backups (logging-log4net) via GitHub
• [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
  • Re: [PR] Fix/missing constructor [logging-log4j2] via GitHub
• [PR] Improve reference documentation [logging-log4cxx] via GitHub
  • Re: [PR] Improve reference documentation [logging-log4cxx] via GitHub
• [PR] Fix StatusLogger crash when property access is denied (#4429) [logging-log4j2] via GitHub
  • Re: [PR] Fix StatusLogger crash when property access is denied (#4429) [logging-log4j2] via GitHub
  • Re: [PR] Fix StatusLogger crash when property access is denied (#4429) [logging-log4j2] via GitHub
• [PR] fixed Pull Request template update [logging-log4j2] via GitHub
• Re: [PR] Bump the maven-minor-updates group across 1 directory with 4 updates [logging-log4j-samples] via GitHub
• Re: [PR] Bump gradle-wrapper from 9.8.0 to 9.8.1 in the gradle-minor-updates group across 1 directory [logging-log4j-samples] via GitHub
• [I] Migrate `log4j-api-test` tests to JUnit 5 [logging-log4j2] via GitHub
  • Re: [I] Migrate `log4j-api-test` tests to JUnit 5 [logging-log4j2] via GitHub
• [I] Fix `StatusLogger` crash when property access is denied [logging-log4j2] via GitHub
  • Re: [I] Fix `StatusLogger` crash when property access is denied [logging-log4j2] via GitHub
  • Re: [I] Fix `StatusLogger` crash when property access is denied [logging-log4j2] via GitHub
  • Re: [I] Fix `StatusLogger` crash when property access is denied [logging-log4j2] via GitHub
• [PR] Fix `StatusLogger` initialization when a security manager denies property access [logging-log4j2] via GitHub
• [PR] Migrate `log4j-api-test` tests to JUnit 5 [logging-log4j2] via GitHub
• [PR] Make Log4cxx background threads identifiable [logging-log4cxx] via GitHub
  • Re: [PR] Make Log4cxx background threads identifiable [logging-log4cxx] via GitHub
• [PR] Improve catch statement consistency [logging-log4cxx] via GitHub
  • Re: [PR] Improve catch statement consistency [logging-log4cxx] via GitHub
• [PR] Remove unused exceptions and apply rule of zero [logging-log4cxx] via GitHub
  • Re: [PR] Remove unused exceptions and apply rule of zero [logging-log4cxx] via GitHub
• [PR] Simplify the TimeBasedRollingPolicy interface [logging-log4cxx] via GitHub
  • Re: [PR] Simplify the TimeBasedRollingPolicy interface [logging-log4cxx] via GitHub
• [I] log4j2.system.properties / log4j2.component.properties are read from the whole classpath and applied silently — add visibility and document the trust boundary [logging-log4j2] via GitHub
  • Re: [I] log4j2.system.properties / log4j2.component.properties are read from the whole classpath and applied silently — add visibility and document the trust boundary [logging-log4j2] via GitHub
• [I] Configuration-time substitution of ${ctx:…} resolves ambient thread-context data (RCE via script attributes; values baked into patterns) [logging-log4j2] via GitHub
• [PR] Add fuzz target for syslog and structured-data layouts [logging-log4j2] via GitHub
• [PR] Respect putIfAbsent results and null arguments in AbstractConfiguration logger mutators [logging-log4j2] via GitHub
  • Re: [PR] Respect putIfAbsent results and null arguments in AbstractConfiguration logger mutators [logging-log4j2] via GitHub
  • Re: [PR] Respect putIfAbsent results and null arguments in AbstractConfiguration logger mutators [logging-log4j2] via GitHub
• [PR] Add escaping tests for `GelfLayout` and `JsonUtils` [logging-log4j2] via GitHub
• [PR] Add escaping test for `HtmlLayout` [logging-log4j2] via GitHub
• Re: [I] Missing/Faulty Logic in AbstractConfiguration for addLoggerAppender / addLoggerFilter / setLoggerAdditive [logging-log4j2] via GitHub
  • Re: [I] Missing/Faulty Logic in AbstractConfiguration for addLoggerAppender / addLoggerFilter / setLoggerAdditive [logging-log4j2] via GitHub
  • Re: [I] Missing/Faulty Logic in AbstractConfiguration for addLoggerAppender / addLoggerFilter / setLoggerAdditive [logging-log4j2] via GitHub
  • Re: [I] Missing/Faulty Logic in AbstractConfiguration for addLoggerAppender / addLoggerFilter / setLoggerAdditive [logging-log4j2] via GitHub
• [PR] Allow ODBCAppender testing with change code [logging-log4cxx] via GitHub
  • Re: [PR] Allow ODBCAppender testing without changing code [logging-log4cxx] via GitHub
• [PR] Fix merging of structured data elements with the same SD-ID in `Rfc5424Layout` [logging-log4j2] via GitHub
  • Re: [PR] Fix merging of structured data elements with the same SD-ID in `Rfc5424Layout` [logging-log4j2] via GitHub
  • Re: [PR] Fix merging of structured data elements with the same SD-ID in `Rfc5424Layout` [logging-log4j2] via GitHub
  • Re: [PR] Fix merging of structured data elements with the same SD-ID in `Rfc5424Layout` [logging-log4j2] via GitHub
• [PR] Simplify SMTPAppender interface [logging-log4cxx] via GitHub
  • Re: [PR] Simplify SMTPAppender interface [logging-log4cxx] via GitHub
• [PR] Respect logger-name hierarchy boundary in Configurator.setAllLevels [logging-log4j2] via GitHub
  • Re: [PR] Respect logger-name hierarchy boundary in Configurator.setAllLevels [logging-log4j2] via GitHub
  • Re: [PR] Respect logger-name hierarchy boundary in Configurator.setAllLevels [logging-log4j2] via GitHub
  • Re: [PR] Respect logger-name hierarchy boundary in Configurator.setAllLevels [logging-log4j2] via GitHub
  • Re: [PR] Respect logger-name hierarchy boundary in Configurator.setAllLevels [logging-log4j2] via GitHub
  • Re: [PR] Respect the logger-name hierarchy boundary in Configurator.setAllLevels and putIfAbsent results in AbstractConfiguration [logging-log4j2] via GitHub
  • Re: [PR] Respect the logger-name hierarchy boundary in Configurator.setAllLevels and putIfAbsent results in AbstractConfiguration [logging-log4j2] via GitHub
  • Re: [PR] Respect the logger-name hierarchy boundary in Configurator.setAllLevels and putIfAbsent results in AbstractConfiguration [logging-log4j2] via GitHub
  • Re: [PR] Respect the logger-name hierarchy boundary in Configurator.setAllLevels and putIfAbsent results in AbstractConfiguration [logging-log4j2] via GitHub
  • Re: [PR] Respect the logger-name hierarchy boundary in Configurator.setAllLevels and putIfAbsent results in AbstractConfiguration [logging-log4j2] via GitHub
  • Re: [PR] Respect the logger-name hierarchy boundary in Configurator.setAllLevels and putIfAbsent results in AbstractConfiguration [logging-log4j2] via GitHub
  • Re: [PR] Respect the logger-name hierarchy boundary in Configurator.setAllLevels and putIfAbsent results in AbstractConfiguration [logging-log4j2] via GitHub
  • Re: [PR] Respect the logger-name hierarchy boundary in Configurator.setAllLevels and putIfAbsent results in AbstractConfiguration [logging-log4j2] via GitHub
• [I] Configurator.setAllLevels also changes the level of sibling loggers that share a name prefix [logging-log4j2] via GitHub
• Re: [PR] Bump the maven-minor-2-x group across 1 directory with 18 updates [logging-log4j2] via GitHub
• Re: [PR] Bump the maven-minor-main group across 1 directory with 22 updates [logging-log4j2] via GitHub
• [PR] Reduce unnecessary file inclusion for Log4cxx users [logging-log4cxx] via GitHub
  • Re: [PR] Reduce unnecessary file inclusion for Log4cxx users [logging-log4cxx] via GitHub
• [PR] Ensure Log4cxx usage does not generate compiler warnings [logging-log4cxx] via GitHub
  • Re: [PR] Ensure Log4cxx usage does not generate compiler warnings [logging-log4cxx] via GitHub
  • Re: [PR] Ensure Log4cxx usage does not generate compiler warnings [logging-log4cxx] via GitHub
  • Re: [PR] Ensure Log4cxx usage does not generate compiler warnings [logging-log4cxx] via GitHub
  • Re: [PR] Ensure Log4cxx usage does not generate compiler warnings [logging-log4cxx] via GitHub
  • Re: [PR] Ensure Log4cxx usage does not generate compiler warnings [logging-log4cxx] via GitHub
• [PR] Restore PropertyChangeListener registration [logging-log4j2] via GitHub
  • Re: [PR] Restore PropertyChangeListener registration [logging-log4j2] via GitHub
• [I] Public headers trigger C4100 "unreferenced formal parameter" in client code built with /W4 on MSVC [logging-log4cxx] via GitHub
  • Re: [I] Public headers trigger C4100 "unreferenced formal parameter" in client code built with /W4 on MSVC [logging-log4cxx] via GitHub
  • Re: [I] Public headers trigger C4100 "unreferenced formal parameter" in client code built with /W4 on MSVC [logging-log4cxx] via GitHub
• [PR] Remove unnecessary and unimplemented interface methods [logging-log4cxx] via GitHub
  • Re: [PR] Remove unnecessary and unimplemented interface methods [logging-log4cxx] via GitHub
  • Re: [PR] Remove unnecessary and unimplemented interface methods [logging-log4cxx] via GitHub
  • Re: [PR] Remove unnecessary and unimplemented interface methods [logging-log4cxx] via GitHub
• [I] LoggerNameLevelRewritePolicy matches sibling packages that share a logger-name prefix [logging-log4j2] via GitHub
  • Re: [I] LoggerNameLevelRewritePolicy matches sibling packages that share a logger-name prefix [logging-log4j2] via GitHub
• [PR] Respect logger-name hierarchy boundary in LoggerNameLevelRewritePolicy [logging-log4j2] via GitHub
  • Re: [PR] Respect logger-name hierarchy boundary in LoggerNameLevelRewritePolicy [logging-log4j2] via GitHub
  • Re: [PR] Respect logger-name hierarchy boundary in LoggerNameLevelRewritePolicy [logging-log4j2] via GitHub
  • Re: [PR] Respect logger-name hierarchy boundary in LoggerNameLevelRewritePolicy [logging-log4j2] via GitHub
  • Re: [PR] Respect logger-name hierarchy boundary in LoggerNameLevelRewritePolicy [logging-log4j2] via GitHub
  • Re: [PR] Respect logger-name hierarchy boundary in LoggerNameLevelRewritePolicy [logging-log4j2] via GitHub
• [PR] Run RollingAppenderCountTest on 2.x again [logging-log4j2] via GitHub
  • Re: [PR] Run RollingAppenderCountTest on 2.x again [logging-log4j2] via GitHub
  • Re: [PR] Run RollingAppenderCountTest on 2.x again [logging-log4j2] via GitHub
• [PR] NoSQL reserved fields [logging-log4j2] via GitHub
  • Re: [PR] [Draft] NoSQL reserved fields [logging-log4j2] via GitHub
  • Re: [PR] [Draft] NoSQL reserved fields [logging-log4j2] via GitHub
  • Re: [PR] [Draft] NoSQL reserved fields [logging-log4j2] via GitHub
  • Re: [PR] [Draft] NoSQL reserved fields [logging-log4j2] via GitHub
  • Re: [PR] [Draft] NoSQL reserved fields [logging-log4j2] via GitHub
  • Re: [PR] [Draft] NoSQL reserved fields [logging-log4j2] via GitHub
  • Re: [PR] HandlingNoSQL reserved fields [logging-log4j2] via GitHub
• [PR] Simplify ThreadUtility class interface [logging-log4cxx] via GitHub
  • Re: [PR] Simplify ThreadUtility class interface [logging-log4cxx] via GitHub
• [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
  • Re: [PR] Support Jackson 3 [logging-log4j2] via GitHub
• Re: [I] Validate scripts in global `<Scripts>` container [logging-log4j2] via GitHub
  • Re: [I] Validate scripts in global `<Scripts>` container [logging-log4j2] via GitHub
  • Re: [I] Validate scripts in global `<Scripts>` container [logging-log4j2] via GitHub
  • Re: [I] Validate scripts in global `<Scripts>` container [logging-log4j2] via GitHub
• [PR] Use checkboxes in the pull request template [logging-log4j2] via GitHub
  • Re: [PR] Use checkboxes in the pull request template [logging-log4j2] via GitHub
  • Re: [PR] Use checkboxes in the pull request template [logging-log4j2] via GitHub
• [I] Pull Request template update [logging-log4j2] via GitHub
  • Re: [I] Pull Request template update [logging-log4j2] via GitHub
  • Re: [I] Pull Request template update [logging-log4j2] via GitHub
• [PR] Clarify web application shutdown listener configuration [logging-log4j2] via GitHub
  • Re: [PR] Clarify web application shutdown listener configuration [logging-log4j2] via GitHub
  • Re: [PR] Clarify web application shutdown listener configuration [logging-log4j2] via GitHub
  • Re: [PR] Clarify web application shutdown listener configuration [logging-log4j2] via GitHub
• [PR] Document behaviour changes in 2.0 [logging-log4cxx] via GitHub
  • Re: [PR] Document behaviour changes in 2.0 [logging-log4cxx] via GitHub
  • Re: [PR] Document behaviour changes in 2.0 [logging-log4cxx] via GitHub
• [PR] Make Msys2 use Windows native thread identifiers and names [logging-log4cxx] via GitHub
  • Re: [PR] Make Msys2 use Windows native thread identifiers and names [logging-log4cxx] via GitHub
• [PR] Make lazy log file creation unsurprising [logging-log4cxx] via GitHub
  • Re: [PR] Make lazy log file creation unsurprising [logging-log4cxx] via GitHub
• [PR] Fix intermittent failsures in CronExpressionTest [logging-log4j2] via GitHub
  • Re: [PR] Fix intermittent failures in CronExpressionTest [logging-log4j2] via GitHub
  • Re: [PR] Fix intermittent failures in CronExpressionTest [logging-log4j2] via GitHub
  • Re: [PR] Fix intermittent failures in CronExpressionTest [logging-log4j2] via GitHub
  • [PR] Fix intermittent failsures in CronExpressionTest [logging-log4j2] via GitHub
  • Re: [PR] Fix intermittent failures in CronExpressionTest [logging-log4j2] via GitHub
• [PR] Simplify MultiprocessRollingFileAppender [logging-log4cxx] via GitHub
  • Re: [PR] Simplify MultiprocessRollingFileAppender [logging-log4cxx] via GitHub
• [PR] Further simplify the FileAppender class interface [logging-log4cxx] via GitHub
  • Re: [PR] Further simplify the FileAppender class interface [logging-log4cxx] via GitHub
• [PR] Fix LocationAwareLogger bypassing configured MessageFactory [logging-log4j2] via GitHub
  • Re: [PR] Fix LocationAwareLogger bypassing configured MessageFactory [logging-log4j2] via GitHub
  • Re: [PR] Fix LocationAwareLogger bypassing configured MessageFactory [logging-log4j2] via GitHub
  • Re: [PR] Fix LocationAwareLogger bypassing configured MessageFactory [logging-log4j2] via GitHub
• [I] log4j-slf4j-impl: LocationAwareLogger.log() bypasses configured MessageFactory [logging-log4j2] via GitHub
• Re: [PR] FLUME-3348：TailDirSource will write an empty position when [logging-flume] via GitHub

• Earlier messages