Skip to content

pack: Handle UINT64_MAX value correctly in json packing [Backport 4.0]#10610

Merged
cosmo0920 merged 2 commits into4.0from
cosmo0920-handle-uint64-max-value-correctly-in-json-pack-4.0
Jul 22, 2025
Merged

pack: Handle UINT64_MAX value correctly in json packing [Backport 4.0]#10610
cosmo0920 merged 2 commits into4.0from
cosmo0920-handle-uint64-max-value-correctly-in-json-pack-4.0

Conversation

@cosmo0920
Copy link
Contributor

This is backporting PR of #10607.


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:

  • Example configuration file for the change
  • Debug log output from testing the change
  • 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.

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

Documentation

  • 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.

Signed-off-by: Hiroshi Hatake <hiroshi@chronosphere.io>
…acking

Signed-off-by: Hiroshi Hatake <hiroshi@chronosphere.io>
@cosmo0920 cosmo0920 added this to the Fluent Bit v4.0.5 milestone Jul 18, 2025
@cosmo0920 cosmo0920 merged commit c91f1c7 into 4.0 Jul 22, 2025
21 checks passed
@cosmo0920 cosmo0920 deleted the cosmo0920-handle-uint64-max-value-correctly-in-json-pack-4.0 branch July 22, 2025 02:57
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.

1 participant