Cherry-pick #8464 to 6.x: Remove line carriages on asset generation #8465
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.
Cherry-pick of PR #8464 to 6.x branch. Original message:
On Windows, asset files can contain line carriages, what leads to
different encoded assets. Remove this carriages between encoding the
string.
This can be what is generating different asset files on #8394, thanks
to @narph for pointing to the possibility of carriages causing this
problem.