Filter work summary to remove non-xml safe characters (PP-1969) #2198
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.
Description
Add some filtering to our
set_summary
function to filter out xml unsafe characters and add a DB migration to remove these characters from our existing database.Motivation and Context
Seeing
Exception in web app: All strings must be XML compatible: Unicode or ASCII, no NULL bytes or control characters
in our logs.Looking at the data in our database, these are only coming in via the Enki integration, but it seemed like a good idea to make sure they can't make it in though any integration.
How Has This Been Tested?
Checklist