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

pack: fix missing scientific notation in JSON parser [Backport 3.2] #9853

Merged
merged 1 commit into from
Jan 21, 2025

Conversation

aivarasbaranauskas
Copy link
Contributor

Make JSON parser work with uppercase E when numbers are in scientific notation format. Also support scientific notation with positive exponent, not only negative.

Fixes #7113, improves on #2746.


Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

  • [N/A] Example configuration file for the change
  • [N/A] Debug log output from testing the change
  • [N/A] Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

  • [N/A] Run local packaging test showing all targets (including any new ones) build.
  • [N/A] Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

  • [N/A] Documentation required for this feature

Backporting

  • Backport to latest stable release.

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

@cosmo0920 cosmo0920 changed the title Fix missing scientific notation in JSON parser Fix missing scientific notation in JSON parser [Backport 3.2] Jan 20, 2025
@aivarasbaranauskas aivarasbaranauskas changed the title Fix missing scientific notation in JSON parser [Backport 3.2] pack: fix missing scientific notation in JSON parser [Backport 3.2] Jan 20, 2025
@edsiper edsiper merged commit e83535b into fluent:3.2 Jan 21, 2025
19 of 21 checks passed
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