Fix for Jenkins Malformed encoding #823
Merged
Conversation
This file contains hidden or 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
bhanurp
approved these changes
Jun 25, 2025
| @@ -111,6 +111,15 @@ private static Properties searchAdditionalPropertiesFile(Properties existingProp | |||
| } else { | |||
| try (InputStream inputStream = Files.newInputStream(propertiesFile.toPath())) { | |||
| props.load(inputStream); | |||
| } catch (IllegalArgumentException e) { | |||
| // Handle malformed Unicode escape sequences | |||
There was a problem hiding this comment.
All comments looks redundant, consider removing.
80ed335 to
640b4d6
Compare
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.
The issue was that when loading properties files with malformed Unicode escape sequences (like
\uxxxx), the original code would fail withIllegalArgumentException: Malformed \uxxxx encoding.The fix implements a fallback strategy:
IllegalArgumentException, try loading with explicit UTF-8 encoding