Sign in

Evidencebytes-31

Too relaxed value validator?

bytes.js#31, at commit c8be41b. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome
PATCH_REJECTED
Wall time
85.9s
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
#31
Pinned commit
c8be41b24b04e04992d5918356d5a4dd35fbf805

01The signal

The report, exactly as it was filed.

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

bytes.js#31 · as filedcommit c8be41b

Too relaxed value validator?

I just noticed this behavior:

``` js
> bytes('250Kg');
250
> bytes('250 e-mails');
250
```

Is this a bug? I would expect a `NaN` instead of `250B`, like in this example:

``` js
> bytes('something 250');
NaN
```
Issue
#31
Commit
c8be41b24b04e04992d5918356d5a4dd35fbf805
Why this commit
The first parent of the fix commit 2abd9365461105ae5ed1de2346243ebb5c163c1c, 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('250Kg') produces 250; the fix makes it produce null.
Expression
bytes('250Kg')
Reported output
250
Where that came from
Read mechanically from the report's fenced code, REPL form: `> bytes('250Kg'); 250`.

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('250Kg')` still produces 250 (read 250)
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`bytes('250Kg')` still produces 250 (read 250)
right-failurepassReproduced the reported failure: bytes('250Kg') produces 250; the fix makes it produce null.
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 c8be41b, 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 c8be41b24b04e04992d5918356d5a4dd35fbf805
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