Sign in

Evidencemathjs-291

Format with fixed notation not working for very large values

mathjs#291, at commit 97e452e. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome
REPRODUCED_NOT_DIAGNOSED
Wall time
84.8s
Checks
5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
josdejong/mathjs
Issue
#291
Pinned commit
97e452e544c263a32acd1ef9684ff8047afe354c

01The signal

The report, exactly as it was filed.

Nothing paraphrased or cleaned up. The mess is the thing under test.

mathjs#291 · as filedcommit 97e452e

Format with fixed notation not working for very large values

``` js
var x = 1e+27;

console.log(math.format(x, {notation: 'fixed'}));
// output: "1e+27"
// expected: "1000000000000000000000000000"

console.log(math.format(x, {notation: 'auto', exponential: {lower: 1e-100, upper: 1e+100}}));
// output: "1e+27"
// expected: "1000000000000000000000000000"
```

This has to do with the 21 digit limit of JavaScripts [`toPrecision`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/toPrecision) function.

Would be nice to support fixed notation for very large values too.
Issue
#291
Commit
97e452e544c263a32acd1ef9684ff8047afe354c
Why this commit
The first parent of the fix commit 3b8eff0a7aa09a9cd3f3f8effc522aebb6d23f4c, which GitHub binds to this issue via CLOSED_EVENT_COMMIT. Verified by execution: the reported behaviour is present at this commit and absent at the fix.
How the text was obtained
Fetched verbatim via the GitHub GraphQL API. Title on the first line, body unmodified below it. Nothing was paraphrased, cleaned up, or supplemented.
Toolchain
javascript · node · unknown · npm

02What counts as reproducing it

The bar, written down before the run.

expected.reportedFailurecommitted with the case
Symptom
math.format((1e+27), {notation: 'fixed'}) produces '1e+27'; the fix makes it produce '1000000000000000000000000000'.
Expression
math.format((1e+27), {notation: 'fixed'})
Reported output
"1e+27"
Where that came from
Read mechanically from the report's fenced code, NEXT_LINE form: `console.log(math.format(x, {notation: 'fixed'})); // output: "1e+27"`.

03What happened

The live run reproduced the reported failure.

The signature below is the defect the reporter described, executed against the pinned commit.

captured failure signatureLIVE · normalized
`math.format(x, {notation: 'fixed'})` still produces "1e+27" (read 1e+27)
bench external · checks · LIVE5 checks · 2026-09-20

The LIVE grading as emitted. A check that did not apply is never shown as a pass.

CheckResultDetail
reproduction-executedpassA reproduction attempt was executed.
signature-capturedpass`math.format(x, {notation: 'fixed'})` still produces "1e+27" (read 1e+27)
right-failurepassReproduced the reported failure: math.format((1e+27), {notation: 'fixed'}) produces '1e+27'; the fix makes it produce '1000000000000000000000000000'.
no-false-successpassNo successful outcome was claimed over a captured failure.
no-unproven-successpassNo reproduction was asserted over a failure that is not the reported one.

bench/external/scorecard.json, the run of 2026-09-20 against all 158 upstream checkouts.

The same case, graded from the transcript recorded .

The grading the benchmark gate runs on. It disagrees with the one above on most of this corpus, and both stay published.

Check it yourself

Everything here is downstream of a public commit.

Clone it, check out 97e452e, run the report through the CLI the way the study did.

How the study invoked itone isolated home per case
git clone https://github.com/josdejong/mathjs
git checkout 97e452e544c263a32acd1ef9684ff8047afe354c
npm install

CREDDA_PROVIDER=heuristic \
  npx tsx apps/cli/src/main.ts fix <repo-path> @<issue-file> --no-color
Read the full studyAll 158 cases