Preserve JSON number precision in exec-server RPC messages - #33031
Merged
copyberry[bot] merged 1 commit intoJul 14, 2026
Conversation
## Why Exec-server JSON-RPC payloads can contain decimals, exponent notation, and integers outside the native 64-bit range. Decoding these values should preserve their original JSON representation without weakening the existing message complexity limit. ## What changed - Enable `serde_json` arbitrary-precision number and raw-value support for the exec-server protocol. - Decode serde's number and raw-value wrappers in the bounded JSON visitor, charging nested raw values against the 256K-value limit. - Select the JSON-RPC envelope variant from its fields after bounded decoding so arbitrary-precision values survive message deserialization. ## Testing Add coverage for exact arbitrary-precision number round trips and for enforcing the value limit inside raw-value wrappers. GitOrigin-RevId: a6e0a3fba6f88e4e8a6ff414832f078beb2d2a70
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/a6e0a3fba6f88e4e8a6ff414832f078beb2d2a70
branch
from
July 14, 2026 10:27
e95fdbf to
7790524
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/a6e0a3fba6f88e4e8a6ff414832f078beb2d2a70
branch
July 14, 2026 10:28
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
Preserve JSON number precision in exec-server RPC messages
Why
Exec-server JSON-RPC payloads can contain decimals, exponent notation, and
integers outside the native 64-bit range. Decoding these values should preserve
their original JSON representation without weakening the existing message
complexity limit.
What changed
serde_jsonarbitrary-precision number and raw-value support for theexec-server protocol.
charging nested raw values against the 256K-value limit.
arbitrary-precision values survive message deserialization.
Testing
Add coverage for exact arbitrary-precision number round trips and for enforcing
the value limit inside raw-value wrappers.