Coerce integer-encoded CBOR values when reading float/double#1247
Merged
Conversation
adwsingh
reviewed
Jun 16, 2026
readDouble rejected any token that wasn't FLOAT, so a whole-valued double or float encoded as a CBOR integer (e.g. 1.0 written as the major-type-0 integer 1) threw a SerializationException.
mtdowling
force-pushed
the
fix-cbor-double-decoding
branch
from
44f5915 to
2765966
Compare
adwsingh
approved these changes
Jun 16, 2026
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.
readDouble rejected any token that wasn't FLOAT, so a whole-valued double or float encoded as a CBOR integer (e.g. 1.0 written as the major-type-0 integer 1) threw a SerializationException.
What behavior changes?
Describe the observable difference in behavior before and after this change.
Why is this change needed?
Explain the motivation: bug, feature request, refactor, performance, etc.
How was this validated?
List tests added, benchmarks run, or manual verification performed.
What should reviewers focus on?
Point reviewers to the files or sections that contain the interesting logic.
Additional Links
Related issues, design docs, or prior art.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.