[SPARK-50400][BUILD] Upgrade log4j2 to 2.24.2 #48945
Closed
+6
−6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Okay, I have re-trigger the failed CI, let's wait for it. |
dongjoon-hyun
approved these changes
Nov 24, 2024
|
Merged to master. Thank you, @panbingkun . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
The pr aims to upgrade log4j2 from
2.24.1to2.24.2.Why are the changes needed?
The full release notes:
https://github.com/apache/logging-log4j2/releases/tag/rel%2F2.24.2
This release fixes a critical bug in Log4j API initialization code, which can cause LogManager.getLogger() to return null under certain conditions. See Broken logger initialization in 2.24.1 logging-log4j2#3143 for details.
Fix key removal issues in Thread Context (Build fails with RAT errors for files in log4j-osgi-test/felix-cache/bundle0/ logging-log4j2#3048)
Use hard references to Loggers in LoggerRegistry. (Broken logger initialization in 2.24.1 logging-log4j2#3143)
Fix ArrayIndexOutOfBoundsException in JSON Template Layout truncated exception resolver (Fix off-by-one in
StackTraceStringResolverlogging-log4j2#3216)Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.
Was this patch authored or co-authored using generative AI tooling?
No.