Sign in

Evidencems-103

There is only partial support for negative time

ms#103, at commit 845c302. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

NO_FAILURE_OBSERVED

executed against the upstream checkout.

Outcome
NO_RUNNABLE_CHECK
Wall time
40.2s
Checks
3 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
vercel/ms
Issue
#103
Pinned commit
845c302f155d955141d623a0276bbff3529ed626

01The signal

The report, exactly as it was filed.

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

ms#103 · as filedcommit 845c302

There is only partial support for negative time

Support for negative time was recently added but it doesn't work for all cases.

## Expected Behavior

`ms(-1 * 60 * 1000, { long: true })` => `-1 minute`
`ms(-1 * 60 * 60 * 10000, { long: true })` => `-10 hours`
`ms(-234234234, { long: true })` => `-3 days`

## Actual Behavior

`ms(-1 * 60 * 1000, { long: true })` => `-60000 ms`
`ms(-1 * 60 * 60 * 10000, { long: true })` => `-36000000 ms`
`ms(-234234234, { long: true })` => ` -234234234 ms`
Repository
vercel/ms
Issue
#103
Commit
845c302f155d955141d623a0276bbff3529ed626
Why this commit
The first parent of the fix commit b8acd77e258cd7b77e80a9655d05759f4134fd92, which GitHub binds to this issue via CLOSED_EVENT_PR. 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
ms(-1 * 60 * 1000, { long: true }) produces '-60000 ms'; the fix makes it produce '-1 minute'.
Expression
ms(-1 * 60 * 1000, { long: true })
Reported output
"-60000 ms"
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: `ms(-1 * 60 * 1000, { long: true }) //=> "-60000 ms"`. 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

No failure was captured.

Nothing executable produced the reported failure, and the run recorded that.

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-capturedfailThe reproduction ran and demonstrated no failure.
right-failurefailExpected `ms(-1 * 60 * 1000, { long: true })` still producing "-60000 ms".
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 845c302, 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/vercel/ms
git checkout 845c302f155d955141d623a0276bbff3529ed626
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