Sign in

Evidenceramda-1714

R.flip always curries two arguments only

ramda#1714, at commit f494250. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

NO_FAILURE_OBSERVED

executed against the upstream checkout.

Outcome
INCONCLUSIVE
Wall time
70.0s
Checks
3 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
ramda/ramda
Issue
#1714
Pinned commit
f494250c0aed9ecc096cc5b5b7823661edc14de2

01The signal

The report, exactly as it was filed.

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

ramda#1714 · as filedcommit f494250

R.flip always curries two arguments only

``` js
R.flip((a, b, c) => { return `${a} ${b} ${c}`})(1, 2);
// => "2 1 undefined" (should be function)
```

http://goo.gl/dkpLXU
Repository
ramda/ramda
Issue
#1714
Commit
f494250c0aed9ecc096cc5b5b7823661edc14de2
Why this commit
The first parent of the fix commit 5b87e5ee4aa9b18ffc3dd514b6fae571afe760c0, 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
R.flip((a, b, c) => { return `${a} ${b} ${c}`})(1, 2) produces '2 1 undefined'; the fix makes it produce [Function (anonymous)].
Expression
R.flip((a, b, c) => { return `${a} ${b} ${c}`})(1, 2)
Reported output
"2 1 undefined"
Where that came from
Read mechanically from the report's fenced code, NEXT_LINE form: `R.flip((a, b, c) => { return `${a} ${b} ${c}`})(1, 2); // => "2 1 undefined" (should be function)`.

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 `R.flip((a, b, c) => { return `${a} ${b} ${c}`})(1, 2)` still producing "2 1 undefined".
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 f494250, 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/ramda/ramda
git checkout f494250c0aed9ecc096cc5b5b7823661edc14de2
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