-
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
[8.15](backport #40446) [syslog] Fix handling of escaped characters in structured data #40464
Conversation
- Improved parser to handle escaped closing square brackets in structured data, along with square brackets in the normal, non-structured data portion of the message. - Fix incorrect offset being passed to removeBytes function, which would not remove escaped characters from structured data values. - The non-compliant-sd unit test cases now include escapes on the closing brackets within the structured data, something that should have always been there. - Add tests (cherry picked from commit 1c01d0e)
This pull request doesn't have a |
This pull request has not been merged yet. Could you please review and merge it @taylor-swanson? 🙏 |
This pull request is now in conflicts. Could you fix it? 🙏
|
This pull request has not been merged yet. Could you please review and merge it @taylor-swanson? 🙏 |
1 similar comment
This pull request has not been merged yet. Could you please review and merge it @taylor-swanson? 🙏 |
This pull request is now in conflicts. Could you fix it? 🙏
|
Proposed commit message
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
N/A
How to test this PR locally
Run unit tests in libbeat/reader/syslog
Related issues
This is an automatic backport of pull request #40446 done by [Mergify](https://mergify.com).