[PR] Restrict pattern layout min/max field width specifiers to 3 digits [logging-log4cxx]

2025-02-03 Thread via GitHub
swebb2066 opened a new pull request, #475: URL: https://github.com/apache/logging-log4cxx/pull/475 This PR proposes adding documentation and checks to avoid integer-overflow bugs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to Gi

Re: [PR] Restrict pattern layout min/max field width specifiers to 3 digits [logging-log4cxx]

2025-02-03 Thread via GitHub
swebb2066 commented on PR #475: URL: https://github.com/apache/logging-log4cxx/pull/475#issuecomment-2632692293 Fixes [OSS-Fuzz 393666942](https://issues.oss-fuzz.com/issues/393666942) and [OSS-Fuzz 393411535](https://issues.oss-fuzz.com/issues/393411535) -- This is an automated message

Re: [PR] Restrict pattern layout min/max field width specifiers to 3 digits [logging-log4cxx]

2025-02-03 Thread via GitHub
swebb2066 merged PR #475: URL: https://github.com/apache/logging-log4cxx/pull/475 -- 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

Re: [I] Suspect deadlock in InternalLoggerRegistry (intermittent) (logging-log4j2)

2025-02-03 Thread via GitHub
vy commented on issue #3399: URL: https://github.com/apache/logging-log4j2/issues/3399#issuecomment-2630648586 > Feel free to merge [#3418](https://github.com/apache/logging-log4j2/pull/3418), since I will be back only next Tuesday. @ppkarwasz, thanks so much. 😍 Though we're not in

Re: [PR] Bump org.wiremock:wiremock from 3.10.0 to 3.11.0 (logging-log4j2)

2025-02-03 Thread via GitHub
github-actions[bot] merged PR #3432: URL: https://github.com/apache/logging-log4j2/pull/3432 -- 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: notificatio

[I] Make `logger.error(ex);`, `logger.info(ex);`, etc. print stack trace by default (logging-log4j2)

2025-02-03 Thread via GitHub
Niko-O opened a new issue, #3433: URL: https://github.com/apache/logging-log4j2/issues/3433 It is too easy to write code like this: ``` try { doThing(); } catch (ThingFailedException ex) { logger.error("Doing this thing failed."); logger.error("Context I

Re: [I] Unable to set property [file] on object [log4net.Appender.FileAppender] (logging-log4net)

2025-02-03 Thread via GitHub
FreeAndNil commented on issue #220: URL: https://github.com/apache/logging-log4net/issues/220#issuecomment-2631586511 Possible duplicate of #163 -- 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

[I] XmlLayoutSchemaLog4J: Changed XML start element for exceptions since v3.0.0 (logging-log4net)

2025-02-03 Thread via GitHub
sita-martin opened a new issue, #225: URL: https://github.com/apache/logging-log4net/issues/225 Until v2.0.17 exceptions were written with the start element __ in an XML. Since version 3.0.0 this has changed to __. i.e. v2.0.17 `System.TimeoutException: throw timeout` v3.0.3