-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove line carriages on asset generation #8464
Merged
Merged
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
On Windows, asset files can contain line carriages, what leads to different encoded assets. Remove this carriages between encoding the string.
ruflin
reviewed
Sep 27, 2018
ruflin
approved these changes
Sep 27, 2018
jsoriano
added
needs_backport
PR is waiting to be backported to other branches.
v6.5.0
v6.4.3
labels
Sep 27, 2018
jsoriano
added a commit
to jsoriano/beats
that referenced
this pull request
Sep 27, 2018
On Windows, asset files can contain line carriages, what leads to different encoded assets. Remove these carriages between encoding the string. (cherry picked from commit aafff49)
jsoriano
added
v6.5.0
and removed
needs_backport
PR is waiting to be backported to other branches.
labels
Sep 27, 2018
jsoriano
added a commit
to jsoriano/beats
that referenced
this pull request
Sep 27, 2018
On Windows, asset files can contain line carriages, what leads to different encoded assets. Remove these carriages between encoding the string. (cherry picked from commit aafff49)
jsoriano
added a commit
that referenced
this pull request
Oct 1, 2018
jsoriano
added a commit
that referenced
this pull request
Oct 1, 2018
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
On Windows, asset files can contain line carriages, what leads to different encoded assets. Remove these carriages between encoding the string. (cherry picked from commit 97927b9)
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.
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.