Handle JSON floats with arbitrary precision#599
Open
jeffcharles wants to merge 1 commit into
Open
Conversation
jeffcharles
changed the title
saga-dasgupta
approved these changes
Jul 14, 2026
saga-dasgupta
left a comment
saga-dasgupta
left a comment
Contributor
There was a problem hiding this comment.
Changes make sense.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fixes some issues with the fuel consumption being reported as a different value compared to production.
arbitrary_precisionresults inserde_jsonpreserving the original numeric token representation. As a result however, the default msgpack formatting encodes it as a string instead of an integer or float so a custom serializer is needed to avoid that change.