[PR] Bump version to 1.5.0 [logging-log4cxx]

2025-04-18 Thread via GitHub
swebb2066 opened a new pull request, #496: URL: https://github.com/apache/logging-log4cxx/pull/496 (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

Re: [PR] Add SO_REUSEADDR to APRServerSocket [logging-log4cxx]

2025-04-18 Thread via GitHub
swebb2066 merged PR #495: URL: https://github.com/apache/logging-log4cxx/pull/495 -- 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: [PR] Bump apache/logging-parent/.github/workflows/deploy-release-reusable.yaml@rel/12.0.0 from 12.0.0 to 12.1.0 [logging-log4j2]

2025-04-18 Thread via GitHub
ppkarwasz commented on PR #3629: URL: https://github.com/apache/logging-log4j2/pull/3629#issuecomment-2813858204 @dependabot recreate -- 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

Re: [I] Unwanted logging by StatusLogger [logging-log4j2]

2025-04-18 Thread via GitHub
ppkarwasz commented on issue #3100: URL: https://github.com/apache/logging-log4j2/issues/3100#issuecomment-2813355721 > I don't know if I have a good argument for keeping them at DEBUG, or if it's just a resistance to change, but I know that 2.24.3 is too noisy at INFO, and 2.24.0 was just

Re: [PR] Bump co.elastic.logging:log4j2-ecs-layout from 1.6.0 to 1.7.0 [logging-log4j2]

2025-04-18 Thread via GitHub
ppkarwasz merged PR #3608: URL: https://github.com/apache/logging-log4j2/pull/3608 -- 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] Bump actions/stale from 9.0.0 to 9.1.0 [logging-log4j2]

2025-04-18 Thread via GitHub
ppkarwasz merged PR #3625: URL: https://github.com/apache/logging-log4j2/pull/3625 -- 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: [I] logchar is defined as char in Windows environments [logging-log4cxx]

2025-04-18 Thread via GitHub
rm5248 commented on issue #494: URL: https://github.com/apache/logging-log4cxx/issues/494#issuecomment-2814323969 > It looks like this changed here: [4507748](https://github.com/apache/logging-log4cxx/commit/45077480eb6af9bb222c554cad7e2c02d1951fc6) > > You should be able to work aro

Re: [PR] Bump org.apache.logging.log4j:log4j-bom from 2.25.0-SNAPSHOT to 3.0.0-beta3 in /log4j-samples-graalvm in the all group across 1 directory [logging-log4j-samples]

2025-04-18 Thread via GitHub
ppkarwasz commented on PR #321: URL: https://github.com/apache/logging-log4j-samples/pull/321#issuecomment-2812547206 Do not upgrade to Log4j 3.x -- 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/merge-dependabot-reusable.yaml@rel/12.0.0 from 12.0.0 to 12.1.0 [logging-log4j2]

2025-04-18 Thread via GitHub
ppkarwasz commented on PR #3627: URL: https://github.com/apache/logging-log4j2/pull/3627#issuecomment-2813858691 @dependabot recreate -- 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

Re: [I] Log file timestamp not updated on some file systems. Support periodic sync to flush metadata to FS [logging-log4j2]

2025-04-18 Thread via GitHub
roytmana commented on issue #3593: URL: https://github.com/apache/logging-log4j2/issues/3593#issuecomment-2815309401 In our case timestamp is not updated **at all** and after 60 days when archival process (external to the app) looks for old logs it hits on live open log files and delete th

Re: [PR] Add SO_REUSEADDR to APRServerSocket [logging-log4cxx]

2025-04-18 Thread via GitHub
swebb2066 commented on PR #495: URL: https://github.com/apache/logging-log4cxx/pull/495#issuecomment-2815290095 Please also change the .cpp files so building with `LOG4CXX_ABI_VER=16` works ``` diff --git a/src/main/cpp/aprserversocket.cpp b/src/main/cpp/aprserversocket.cpp index 53

Re: [PR] Bump org.mockito:mockito-bom from 5.16.1 to 5.17.0 [logging-log4j2]

2025-04-18 Thread via GitHub
ppkarwasz merged PR #3591: URL: https://github.com/apache/logging-log4j2/pull/3591 -- 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: [I] logchar is defined as char in Windows environments [logging-log4cxx]

2025-04-18 Thread via GitHub
WorldRobertProject commented on issue #494: URL: https://github.com/apache/logging-log4cxx/issues/494#issuecomment-2814892047 Here's how we use an overlay port: 1. Copy ``vcpkg\ports\log4cxx`` to another place 2. Add an option `-DLOG4CXX_CHAR=wchar_t` to ``vcpkg_cmake_configure`` i

Re: [I] logchar is defined as char in Windows environments [logging-log4cxx]

2025-04-18 Thread via GitHub
WorldRobertProject commented on issue #494: URL: https://github.com/apache/logging-log4cxx/issues/494#issuecomment-2814856038 @rm5248 For now, this issue has been resolved by the overlay port. Thank you so much. I realized that there is still an issue caused by character encoding.

Re: [PR] Add SO_REUSEADDR to APRServerSocket [logging-log4cxx]

2025-04-18 Thread via GitHub
swebb2066 commented on PR #495: URL: https://github.com/apache/logging-log4cxx/pull/495#issuecomment-2814831567 To assist with the migration to the next ABI version, could you please also test the LOG4CXX_ABI_VERSION. For example: ``` diff --git a/src/main/include/log4cxx/helpers/serve

Re: [I] logchar is defined as char in Windows environments [logging-log4cxx]

2025-04-18 Thread via GitHub
swebb2066 commented on issue #494: URL: https://github.com/apache/logging-log4cxx/issues/494#issuecomment-2814724266 > but Unicode-specific characters cannot be logged @WorldRobertProject please provide a code snippet that shows how you would like to log Unicode-specific characters.