Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The current version has a bug in the integer handling logic that produces incorrect results for big integer number. See the upstream error report and the fix: https://github.com/stedolan/jq/pull/1752
This was originally reported in https://bugzilla.redhat.com/show_bug.cgi?id=2008717 for RHEL 8 and https://bugzilla.redhat.com/show_bug.cgi?id=2008979 for Fedora, but it impacts RHEL 9 just as well.
Version-Release number of selected component (if applicable):
jq-1.6-9.el9
How reproducible:
always
Steps to Reproduce:
$ echo '{"a":9011153322235679}' | jq '.a'
Actual results:
9011153322235680
Expected results:
9011153322235679
Uh, that's not right. It should have made the MR on the upstream repo, not on my fork. I got that from centpkg:
$ git push dcavalca big-integer
Enumerating objects: 6, done.
Counting objects: 100% (6/6), done.
Delta compression using up to 16 threads
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 258.32 KiB | 5.87 MiB/s, done.
Total 4 (delta 1), reused 0 (delta 0), pack-reused 0
remote:
remote: To create a merge request for big-integer, visit:
remote: https://gitlab.com/dcavalca/jq/-/merge_requests/new?merge_request%5Bsource_branch%5D=big-integer
remote:
To gitlab.com:dcavalca/jq.git
* [new branch] big-integer -> big-integer
$
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (new packages: jq), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:2444