[PR] Allow a HTMLLayout title to contain characters special to HTML [logging-log4cxx]

2025-07-20 Thread via GitHub
swebb2066 opened a new pull request, #513: URL: https://github.com/apache/logging-log4cxx/pull/513 (no comment) -- 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 unsubscri

[PR] Escape control characters in JSONLayout data [logging-log4cxx]

2025-07-20 Thread via GitHub
swebb2066 opened a new pull request, #512: URL: https://github.com/apache/logging-log4cxx/pull/512 This PR ensures that the control characters (U+ through U+001F) that are escaped in JSON output -- This is an automated message from the Apache Git Service. To respond to the message, p

Re: [PR] Add ThreadContextStack injection capability [logging-log4j2]

2025-07-20 Thread via GitHub
yybmion commented on PR #3810: URL: https://github.com/apache/logging-log4j2/pull/3810#issuecomment-3094726259 Hi @vy, Thank you for the question! You previously provided positive feedback on this issue, stating: > "I think your assessment is correct: ThreadContext alway

Re: [I] Regression in default logging configuration since 2.25.0 [logging-log4j2]

2025-07-20 Thread via GitHub
vy commented on issue #3835: URL: https://github.com/apache/logging-log4j2/issues/3835#issuecomment-3094699113 I tortured @ppkarwasz in a video call to make him confess that `org.apache.logging.log4j.core.config.DefaultLayout#toSerializable(LogEvent)` needed a newline suffix. @rschmitt, wo

Re: [PR] Create `NamedDatePattern` to make date & time patterns supported by Pattern Layout programmatically accessible [logging-log4j2]

2025-07-20 Thread via GitHub
vy merged PR #3789: URL: https://github.com/apache/logging-log4j2/pull/3789 -- 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...@lo

Re: [PR] Add changelog for `StatusLogger` changes in `2.23.0` [logging-log4j2]

2025-07-20 Thread via GitHub
vy merged PR #3838: URL: https://github.com/apache/logging-log4j2/pull/3838 -- 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...@lo

Re: [PR] fix: Prevent `LogBuilder` memory leak in Log4j API to Logback bridge [logging-log4j2]

2025-07-20 Thread via GitHub
vy merged PR #3824: URL: https://github.com/apache/logging-log4j2/pull/3824 -- 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...@lo

Re: [I] Using log4j-to-slf4j in a web application incorrectly sets a value in a ThreadLocal in org.apache.logging.slf4j.SLF4JLogger [logging-log4j2]

2025-07-20 Thread via GitHub
vy closed issue #3819: Using log4j-to-slf4j in a web application incorrectly sets a value in a ThreadLocal in org.apache.logging.slf4j.SLF4JLogger URL: https://github.com/apache/logging-log4j2/issues/3819 -- This is an automated message from the Apache Git Service. To respond to the message,

Re: [PR] Make `StatusLogger` self-contained and testable [logging-log4j2]

2025-07-20 Thread via GitHub
vy commented on PR #2249: URL: https://github.com/apache/logging-log4j2/pull/2249#issuecomment-3094677599 @ppkarwasz, you're right. I've submitted #3838 to address this. Would you mind reviewing, please? -- This is an automated message from the Apache Git Service. To respond to the messag

[PR] Add changelog for `StatusLogger` changes in `2.23.0` [logging-log4j2]

2025-07-20 Thread via GitHub
vy opened a new pull request, #3838: URL: https://github.com/apache/logging-log4j2/pull/3838 (no comment) -- 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-

Re: [PR] Merge release `2.25.1` back into `2.x` [logging-log4j2]

2025-07-20 Thread via GitHub
vy merged PR #3820: URL: https://github.com/apache/logging-log4j2/pull/3820 -- 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...@lo

Re: [PR] Add ThreadContextStack injection capability [logging-log4j2]

2025-07-20 Thread via GitHub
vy commented on PR #3810: URL: https://github.com/apache/logging-log4j2/pull/3810#issuecomment-3094666998 @yybmion, do you have a use case? Do you need this functionality for a certain system of yours that is deployed to production? Would you mind giving us some more context, please? --

Re: [I] Project page is 404 [logging-log4j-jmx-gui]

2025-07-20 Thread via GitHub
vy closed issue #38: Project page is 404 URL: https://github.com/apache/logging-log4j-jmx-gui/issues/38 -- 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:

Re: [I] Project page is 404 [logging-log4j-jmx-gui]

2025-07-20 Thread via GitHub
vy commented on issue #38: URL: https://github.com/apache/logging-log4j-jmx-gui/issues/38#issuecomment-3094661559 @matozoid, fixed. The website should be up. Let us know if you still experience problems. -- This is an automated message from the Apache Git Service. To respond to the messa

Re: [PR] Bump apache/logging-parent/.github/workflows/deploy-snapshot-reusable.yaml@rel/11.3.0 from 11.3.0 to 12.1.0 [logging-log4j-jmx-gui]

2025-07-20 Thread via GitHub
vy commented on PR #36: URL: https://github.com/apache/logging-log4j-jmx-gui/pull/36#issuecomment-3094661020 Fixed manually. -- 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.

Re: [PR] Bump apache/logging-parent/.github/workflows/deploy-snapshot-reusable.yaml@rel/11.3.0 from 11.3.0 to 12.1.0 [logging-log4j-jmx-gui]

2025-07-20 Thread via GitHub
vy closed pull request #36: Bump apache/logging-parent/.github/workflows/deploy-snapshot-reusable.yaml@rel/11.3.0 from 11.3.0 to 12.1.0 URL: https://github.com/apache/logging-log4j-jmx-gui/pull/36 -- This is an automated message from the Apache Git Service. To respond to the message, please

Re: [PR] Bump org.apache.logging:logging-parent from 11.3.0 to 12.1.1 [logging-log4j-jmx-gui]

2025-07-20 Thread via GitHub
vy commented on PR #39: URL: https://github.com/apache/logging-log4j-jmx-gui/pull/39#issuecomment-3094660924 Fixed manually. -- 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.

Re: [PR] Bump org.apache.logging:logging-parent from 11.3.0 to 12.1.1 [logging-log4j-jmx-gui]

2025-07-20 Thread via GitHub
vy closed pull request #39: Bump org.apache.logging:logging-parent from 11.3.0 to 12.1.1 URL: https://github.com/apache/logging-log4j-jmx-gui/pull/39 -- 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

Re: [PR] Bump apache/logging-parent/.github/workflows/build-reusable.yaml@rel/12.1.0 from 12.1.0 to 12.1.1 [logging-log4j-jmx-gui]

2025-07-20 Thread via GitHub
vy closed pull request #43: Bump apache/logging-parent/.github/workflows/build-reusable.yaml@rel/12.1.0 from 12.1.0 to 12.1.1 URL: https://github.com/apache/logging-log4j-jmx-gui/pull/43 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [PR] Bump apache/logging-parent/.github/workflows/build-reusable.yaml@rel/12.1.0 from 12.1.0 to 12.1.1 [logging-log4j-jmx-gui]

2025-07-20 Thread via GitHub
vy commented on PR #43: URL: https://github.com/apache/logging-log4j-jmx-gui/pull/43#issuecomment-3094660863 Fixed manually. -- 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.

Re: [I] Deprecate withers in `2.x` [logging-log4j2]

2025-07-20 Thread via GitHub
ppkarwasz closed issue #3750: Deprecate withers in `2.x` URL: https://github.com/apache/logging-log4j2/issues/3750 -- 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 unsubscrib

Re: [I] Bugwards incompatibility in Log4j2 properties config parsing since 2.25.0 [logging-log4j2]

2025-07-20 Thread via GitHub
ppkarwasz commented on issue #3836: URL: https://github.com/apache/logging-log4j2/issues/3836#issuecomment-3094645747 Hi @rschmitt, Thank you for reporting this. The behavior you're seeing stems from the fact that the **Java Properties configuration format** operates different

Re: [I] Regression in default logging configuration since 2.25.0 [logging-log4j2]

2025-07-20 Thread via GitHub
ppkarwasz commented on issue #3835: URL: https://github.com/apache/logging-log4j2/issues/3835#issuecomment-3094503720 Hi @rschmitt, Nice catch! :100: Can you make a PR to fix the problem? -- This is an automated message from the Apache Git Service. To respond to the message, ple

Re: [I] Badly formatted status msg in AbstractDriverManagerConnectionSource [logging-log4j2]

2025-07-20 Thread via GitHub
ppkarwasz closed issue #3828: Badly formatted status msg in AbstractDriverManagerConnectionSource URL: https://github.com/apache/logging-log4j2/issues/3828 -- 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

Re: [PR] Correct log message format in `AbstractDriverManagerConnectionSource` [logging-log4j2]

2025-07-20 Thread via GitHub
ppkarwasz merged PR #3831: URL: https://github.com/apache/logging-log4j2/pull/3831 -- 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

Re: [PR] Maven: Repro for issue 3834 [logging-log4j-samples]

2025-07-20 Thread via GitHub
ppkarwasz commented on PR #352: URL: https://github.com/apache/logging-log4j-samples/pull/352#issuecomment-3094000120 Hi @rob975, Thanks for the example. I'll look into it to see if we manage to make the build fail. -- This is an automated message from the Apache Git Service. To r

Re: [I] Failed to build parent project for org.apache.logging.log4j:log4j-api:jar:2.25.1 [logging-log4j2]

2025-07-20 Thread via GitHub
ppkarwasz closed issue #3834: Failed to build parent project for org.apache.logging.log4j:log4j-api:jar:2.25.1 URL: https://github.com/apache/logging-log4j2/issues/3834 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

Re: [I] Failed to build parent project for org.apache.logging.log4j:log4j-api:jar:2.25.1 [logging-log4j2]

2025-07-20 Thread via GitHub
ppkarwasz commented on issue #3834: URL: https://github.com/apache/logging-log4j2/issues/3834#issuecomment-3093990475 Hi @rob975, Thanks for the PR apache/logging-log4j-samples#352. From that example it looks like the problem causes `ERROR` and `WARN` messages, but does not fail the