Skip to content
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

Cherry-pick #8464 to 6.x: Remove line carriages on asset generation #8465

Merged
merged 1 commit into from
Oct 1, 2018

Conversation

jsoriano
Copy link
Member

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.

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)
@@ -33,6 +33,7 @@ The list below covers the major changes between 6.3.0 and master only.
==== Bugfixes

- Fix permissions of generated Filebeat filesets. {pull}7140[7140]
- Fix issue on asset generation that could lead to different results in Windows. {pull}8464[8464]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is CHANGELOG-developer.asciidoc the correct doc to target?

I notice other PRs like https://github.com/elastic/beats/pull/8147/files target CHANGELOG.asciidoc

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is a change only for development, it doesn't affect any functionality.

@jsoriano jsoriano merged commit f0b5fe8 into elastic:6.x Oct 1, 2018
@jsoriano jsoriano deleted the backport_8464_6.x branch October 1, 2018 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants