kelunik opened a new pull request, #3872: URL: https://github.com/apache/logging-log4j2/pull/3872
Caching of filesystem timestamps (at least in ext4 on Linux) results in non-accurate creation timestamps. Thus, let's round it to the second. Rounding is also applied for the lastModified time, but I'm not sure whether it's needed there. Fixes #3068. ### ✅ Required checks - [x] **License**: I confirm that my changes are submitted under the [Apache License, Version 2.0](https://apache.org/licenses/LICENSE-2.0). - [x] **Commit signatures**: All commits are signed and verifiable. (See [GitHub Docs on Commit Signature Verification](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification)). - [x] **Code formatting**: The code is formatted according to the project’s style guide. - [ ] **Build & Test**: I verified that the project builds and all unit tests pass. ### 🧪 Tests (select one) - [ ] I have added or updated tests to cover my changes. - [x] No additional tests are needed for this change. ### 📝 Changelog (select one) - [ ] I added a changelog entry in `src/changelog/.2.x.x`. (See [Changelog Entry File Guide](https://logging.apache.org/log4j/tools/log4j-changelog.html#changelog-entry-file)). - [ ] This is a trivial change and does not require a changelog entry. -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
