Sign in

Evidencefilesize-77

It does not work properly for some extreme cases

filesize.js#77, at commit e1e6185. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome
PARTIALLY_VERIFIED
Wall time
274.4s
Checks
5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
avoidwork/filesize.js
Issue
#77
Pinned commit
e1e618513627e03b2609b94d0c5989ee4a6f24fb

01The signal

The report, exactly as it was filed.

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

filesize.js#77 · as filedcommit e1e6185

It does not work properly for some extreme cases

version: `filesize@3.2.0`

```
> filesize(1/8, { bits: true })
'1024 '
> filesize(1024*1024*1024*1024*1024*1024*1024*1024*1024, { bits: true })
'8 '
> filesize(1, { bits: true })
'8 b'
> filesize(1024*1024*1024*1024*1024*1024*1024*1024, { bits: true })
'8 Yb'
> 
```
Issue
#77
Commit
e1e618513627e03b2609b94d0c5989ee4a6f24fb
Why this commit
The first parent of the fix commit cc2ad7ae9684b91aa27b6067babeaf9642c658fe, 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
filesize(1/8, { bits: true }) produces '1024 '; the fix makes it produce '1 b'.
Expression
filesize(1/8, { bits: true })
Reported output
'1024 '
Where that came from
Read mechanically from the report's fenced code, REPL form: `> filesize(1/8, { bits: true }) '1024 '`.

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
`filesize(1/8, { bits: true })` still produces '1024 ' (read 1024 )
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`filesize(1/8, { bits: true })` still produces '1024 ' (read 1024 )
right-failurepassReproduced the reported failure: filesize(1/8, { bits: true }) produces '1024 '; the fix makes it produce '1 b'.
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 e1e6185, 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/avoidwork/filesize.js
git checkout e1e618513627e03b2609b94d0c5989ee4a6f24fb
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