error in number serialization

[dsxmachina]

Describe the bug
If you have serialized a 64-bit unsinged integer to json and you pipe the json through jq, the number will be changed into something else.

To Reproduce

echo '{"big-number":18446744073709551615}' | jq

Produces

{
  "big-number": 18446744073709552000
}

Expected behavior
18446744073709551615

Environment (please complete the following information):

• Linux, NixOS 22.11
• jq 1.6

[wader]

Hi, have a look at

• Numbers longer 17 digits wiped by zeroes #2396

[notevenaperson]

@wader

$ jq --version
jq-1.6-145-ga9f97e9
$ echo '{"userId": 11111111112222222222}' | jq '.userId'
11111111112222222222

I think this issue will continue to be reported until you make a new release. Most users do not have the latest version because their distro doesn't follow git head. Not even bleeding-edge Arch Linux has this fix. A way to get distros to update would be a version 1.7.

[wader]

Yeap hope we can do so also, see #2305 for current state of jq

[trothwell]

What does the JSON spec say about numbers?

The JSON Data Interchange Syntax ECMA-404
JSON instead offers only the representation of
numbers that humans use: a sequence of digits. All programming languages know how to make sense of digit
sequences even if they disagree on internal representations. That is enough to allow interchange.

I'd suggest that the internal representation be chosen by the user for backwards compatibility which was broken in jq-1.7 due to Decimal literal number #1752.

[nicowilliams]

This is fixed in jq 1.7.