Sign in

Evidencejs-yaml-117

Negative zero loses the sign after dump.

js-yaml#117, at commit e6bac15. 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
111.2s
Checks
5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
nodeca/js-yaml
Issue
#117
Pinned commit
e6bac155e7670e04343f6a5cd97cb441349deb73

01The signal

The report, exactly as it was filed.

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

js-yaml#117 · as filedcommit e6bac15

Negative zero loses the sign after dump.

``` javascript
yaml.dump(-0.0) // => '0\n'
```
Repository
nodeca/js-yaml
Issue
#117
Commit
e6bac155e7670e04343f6a5cd97cb441349deb73
Why this commit
The first parent of the fix commit 6030fa6c389aaf14545222f7fa27e86359ca3a3b, which GitHub binds to this issue via REFERENCED_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
yaml.dump(-0.0) produces '0\n'; the fix makes it produce '-0.0\n'.
Expression
yaml.dump(-0.0)
Reported output
'0\n'
Where that came from
Read mechanically from the report's fenced code, SAME_LINE form: `yaml.dump(-0.0) // => '0\n'`.

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
`yaml.dump(-0.0)` still produces '0\n' (read 0
)
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`yaml.dump(-0.0)` still produces '0\n' (read 0 )
right-failurepassReproduced the reported failure: yaml.dump(-0.0) produces '0\n'; the fix makes it produce '-0.0\n'.
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 e6bac15, 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/nodeca/js-yaml
git checkout e6bac155e7670e04343f6a5cd97cb441349deb73
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