Evidencebytes-61

`bytes.parse()` can return `NaN`

bytes.js#61, at commit 1925beb. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome: VERIFIED
Wall time: 70.5s
Checks: 5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome: not recorded
Checks: none run

Repository: visionmedia/bytes.js
Issue: #61
Pinned commit: 1925beb7c083528de763005ce91dfdfa312d0f45

01The signal

The report, exactly as it was filed.

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

bytes.js#61 · as filedcommit 1925beb

`bytes.parse()` can return `NaN`

`bytes.parse("string without any numbers")` returns `NaN`, when according to the documentation it should return a `null`.

Repository: visionmedia/bytes.js
Issue: #61
Commit: 1925beb7c083528de763005ce91dfdfa312d0f45
Why this commit: The first parent of the fix commit 581b2b5b96d10fe75bda7ae03ee6afab64b6abcb, 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: bytes.parse("string without any numbers") produces NaN; the fix makes it produce null.
Expression: bytes.parse("string without any numbers")
Reported output: NaN
Where that came from: Proposed by a model reading this report and nothing else -- it never saw the repository or the fix commit -- and read back as a claim by the same parser the harvest uses, SAME_LINE form: `bytes.parse("string without any numbers") //=> NaN`. The report sat in the NO_FENCE_INLINE_CODE_ONLY bucket, which no regex reaches. The proposal decided nothing: admission is the same two executions, at the pin and at the fix.

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

`bytes.parse("string without any numbers")` still produces NaN (read NaN)

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.

Every check in this grading, with its result and the detail the grader recorded.
Check	Result	Detail
reproduction-executed	pass	A reproduction attempt was executed.
signature-captured	pass	`bytes.parse("string without any numbers")` still produces NaN (read NaN)
right-failure	pass	Reproduced the reported failure: bytes.parse("string without any numbers") produces NaN; the fix makes it produce null.
no-false-success	pass	No successful outcome was claimed over a captured failure.
no-unproven-success	pass	No 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 1925beb, 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/visionmedia/bytes.js
git checkout 1925beb7c083528de763005ce91dfdfa312d0f45
npm install

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

Read the full study All 158 cases