-
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
Fix build for all OS after #8424 #8717
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will approve this to get the build green again, but I am not sure to do we really need to create a platform-specific file for stripping new line?
Just to clarify my previous comment, adding platform specific code should be for something that would yield simplicity benefits, hidding system calls / hidding libraries. My worries here is to add complexity and maintenance. |
SGTM, let me do the change, as this is only in master (not backported to 6.x yet) |
Added to #8718 |
* Fix build for all OS after elastic#8424 * Apply PR comments
… CRI log processing (#8718) * Reduce casting between []byte and string in CRI log processing (#8424) * Reduce casting between []byte and string in CRI log processing * Refactor CRI and json-file detection * Improve handling of new lines in linux/windows CRI logs. * Move new line removal to OS specific functions. * Add option to force CRI log parsing, otherwise autodetect log type. * Fixed unit tests and new line removal * Fixed new line removal * Added unit tests to check Forced CRI flag (cherry picked from commit 3f7d6a6) * Add CHANGELOG and docs for CRI force flag (#8699) (cherry picked from commit 06ec3b9) * Fix conflicting paths * Fix build for all OS after #8424 (#8717) * Fix build for all OS after #8424 * Apply PR comments
Use the right build flags for docker JSON platform specific code