Add null (\u0000) as a valid line terminator#28998
Conversation
|
This pull request does not have a backport label. Could you fix it @belimawr? 🙏
NOTE: |
\u0000 as a valid line terminator\u0000) as a valid line terminator
c55e6c4 to
bb452e1
Compare
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
bb452e1 to
6726f70
Compare
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
ade174f to
5eb5cb8
Compare
|
This pull request is now in conflicts. Could you fix it? 🙏 |
Add null (`\u0000`) as a valid line terminator called `null_terminator`. Closes: elastic#27061
5eb5cb8 to
046d765
Compare
…ws-on-file-changes * upstream/master: Fix discovery of Nomad allocations (elastic#28700) Add null (`\u0000`) as a valid line terminator (elastic#28998) Remove `logging.files.suffix` option and always use datetime suffixes (elastic#28927) x-pack/filebeat/module: add note for default var.input (elastic#28324) Fix AccessList & AccessMask processing in security data_stream (elastic#29016) [Metricbeat] Fix wrong mapping on "info" subkey (elastic#28782) ci: daily/weekly jobs (elastic#29050) [mergify] report open backported PRs once a week (elastic#28964)
What does this PR do?
Add null (
\u0000) as a valid line terminator callednull_terminator.Why is it important?
Closes: #27061
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areasCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues