Evidencemathjs-2964

distance function error when calculate distance from point to line

mathjs#2964, at commit 6fa5890. 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
55.8s
Checks
3 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Issue
#2964
Pinned commit
6fa589057e4756ae3c76f7dfbf2295d535e1b1c1

01The signal

The report, exactly as it was filed.

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

mathjs#2964 · as filedcommit 6fa5890

distance function error when calculate distance from point to line

There are two points (5,0) and (10,0) in a line. The distance between from point (8,0) to the line should be 0, but got wrong result. 
Is this a bug or my syntax error?

```js
var {distance} = math

// math.distance([x1,y1], [x2,y2], [x3,y3])
// math.distance({pointX, pointY}, {lineOnePtX, lineOnePtY}, {lineTwoPtX, lineTwoPtY})

console.log(distance([8,0],[10,0],[5,0]));  // 3.5777087639996634
console.log(distance(
 {pointX: 8, pointY: 0},
 {lineOnePtX: 10, lineOnePtY: 0},
 {lineTwoPtX: 5, lineTwoPtY: 0})   );  //5.008792269599529
```
Issue
#2964
Commit
6fa589057e4756ae3c76f7dfbf2295d535e1b1c1
Why this commit
The first parent of the fix commit 1b06ec4b813ef63ff5e5ff6ae7c7362026c59fb4, 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
distance([8,0],[10,0],[5,0]) produces 3.5777087639996634; the fix makes it produce 0.
Expression
distance([8,0],[10,0],[5,0])
Reported output
3.5777087639996634
Where that came from
Read mechanically from the report's fenced code, SAME_LINE form: `console.log(distance([8,0],[10,0],[5,0])); // 3.5777087639996634`.

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.

Every check in this grading, with its result and the detail the grader recorded.
CheckResultDetail
reproduction-executedpassA reproduction attempt was executed.
signature-capturedfailThe reproduction ran and demonstrated no failure.
right-failurefailExpected `distance([8,0],[10,0],[5,0])` still producing 3.5777087639996634.
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 6fa5890, 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/josdejong/mathjs
git checkout 6fa589057e4756ae3c76f7dfbf2295d535e1b1c1
npm install

CREDDA_PROVIDER=heuristic \
  npx tsx apps/cli/src/main.ts fix <repo-path> @<issue-file> --no-color