-
Notifications
You must be signed in to change notification settings - Fork 32
fix: Fix Invalid iproute2
JSON output in arm64
#1820
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
Conversation
00cea61
to
05b4ca3
Compare
@mateoflorido Thanks a lot for the workaround and LGTM. I think this can catch what we've seen so far. Even if it doesn't catch every edge case, a valid json value cannot start with a number and continue with a string, so it should be quite benign for any valid response and shouldn't do any harm. I'll leave the final approval to @addyess and @berkayoz |
1a55d26
to
01c344f
Compare
01c344f
to
ad6254d
Compare
// combines the VXLAN VNI value with the fan-map extension, resulting in | ||
// invalid JSON, but a valid YAML. |
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.
😍
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.
Yep, this is lovely and simple
Fix Invalid `iproute2` JSON output in arm64 (cherry picked from commit adbd67e)
Successfully created backport PR for |
Fix Invalid `iproute2` JSON output in arm64 (cherry picked from commit adbd67e)
Successfully created backport PR for |
Fix Invalid `iproute2` JSON output in arm64 (cherry picked from commit adbd67e)
Successfully created backport PR for |
Fix Invalid `iproute2` JSON output in arm64 (cherry picked from commit adbd67e) Co-authored-by: Mateo Florido <[email protected]>
Description
Fix an invalid
iproute2
JSON output in arm64Solution
Given that all JSON is a valid YAML we can use its parser to avoid errors caused by invalid JSON.
Issue
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2121908
Backport
Should this PR be backported? If so, to which release?
Checklist
type: title