Repository navigation
Fix JSON encoding of large integers - #196
Open
vera-rubin wants to merge 1 commit into
Open
vera-rubin wants to merge 1 commit into
vera-rubin wants to merge 1 commit into
Conversation
|
This branch has not been deployed
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
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.
CELJSONEncoderemits9007199254740993as a JSON number, but CEL's JSON mapping requires the decimal string"9007199254740993"for integers outside ±(2⁵³−1). Onmain(22158f8), run:python -m celpy -n '9007199254740993'We convert large CEL integers to strings during the encoder's existing recursive walk, keeping values inside the range as numbers.
We tested signed and unsigned boundaries at the top level and in nested lists and maps, and ran the unit suite and doctests.
— ChipLab