Escape invalid characters when creating XML document from log file #3638
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
1. Always use UTF-8 encoding for test console output unless running on WINE 2. Replace invalid characters with '?' when creating XML element with text content from log file.
Replace invalid surrogate pairs as well.
Rely on Nightly.ReplaceInvalidXmlChars to let us know about bad encoding in the log file.
nickshulman
changed the title
nickshulman
deleted the
Skyline/work/20251010_BetterFixForNightlyFailure
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Replace invalid characters with backslash u and a hex code when creating XML element with text content from log file.