Sign in

Evidencepretty-ms-7

A verbose option?

pretty-ms#7, at commit 6026235. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome
VERIFIED
Wall time
96.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
sindresorhus/pretty-ms
Issue
#7
Pinned commit
602623519c2233e32df0cf258ed2311c3e1e548f

01The signal

The report, exactly as it was filed.

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

pretty-ms#7 · as filedcommit 6026235

A verbose option?

@sindresorhus 
In places where a verbose display is required, I would like something like : -

``` js
prettyMs(1337, {verbose: true});
// => 1.3 seconds
// => instead of `1.3s`

prettyMs(1337000000, {verbose: true});
//=> '15 days 11 hours 23 minutes 20 seconds'
```

I would be happy to submit a patch, if you are interested in this too?
Issue
#7
Commit
602623519c2233e32df0cf258ed2311c3e1e548f
Why this commit
The first parent of the fix commit 7d8e034c346e4b426e4df3771832d7126189f84f, 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
prettyMs(1337000000, {verbose: true}) does not produce '15 days 11 hours 23 minutes 20 seconds'; the fix makes it do so.
Expression
prettyMs(1337000000, {verbose: true})
Where that came from
Read mechanically from the report's fenced code, NEXT_LINE form: `prettyMs(1337000000, {verbose: true}); //=> '15 days 11 hours 23 minutes 20 seconds'`.

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
`prettyMs(1337000000, {verbose: true})` still produces '15 days 11 hours 23 minutes 20 seconds' (read 15d 11h 23m 20s)
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`prettyMs(1337000000, {verbose: true})` still produces '15 days 11 hours 23 minutes 20 seconds' (read 15d 11h 23m 20s)
right-failurepassReproduced the reported failure: prettyMs(1337000000, {verbose: true}) does not produce '15 days 11 hours 23 minutes 20 seconds'; the fix makes it do so.
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 6026235, 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/sindresorhus/pretty-ms
git checkout 602623519c2233e32df0cf258ed2311c3e1e548f
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