Sign in

Evidenceurijs-224

.relativeTo() requires trailing slash on .. path segments

URI.js#224, at commit 4ad3f29. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome
REPRODUCED_NOT_DIAGNOSED
Wall time
62.8s
Checks
5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
medialize/URI.js
Issue
#224
Pinned commit
4ad3f2927c5dddce64593bc08cee1678d852c4f5

01The signal

The report, exactly as it was filed.

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

URI.js#224 · as filedcommit 4ad3f29

.relativeTo() requires trailing slash on .. path segments

I'm not sure if this adheres to the URI spec or not, but this behaviour was surprising to me:

```
> URI("http://example.com/foo/..").relativeTo("http://example.com/foo/").toString()
""
> URI("http://example.com/foo/../").relativeTo("http://example.com/foo/").toString()
"../"
```

What are your thoughts here?
Issue
#224
Commit
4ad3f2927c5dddce64593bc08cee1678d852c4f5
Why this commit
The first parent of the fix commit 5331344f6b2bf23b995af203d4a4866e97bd87b5, 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
URI("http://example.com/foo/..").relativeTo("http://example.com/foo/").toString() produces ''; the fix makes it produce '../'.
Expression
URI("http://example.com/foo/..").relativeTo("http://example.com/foo/").toString()
Reported output
""
Where that came from
Read mechanically from the report's fenced code, REPL form: `> URI("http://example.com/foo/..").relativeTo("http://example.com/foo/").toString() ""`.

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
`URI("http://example.com/foo/..").relativeTo("http://example.com/foo/").toString()` still produces "" (read )
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`URI("http://example.com/foo/..").relativeTo("http://example.com/foo/").toString()` still produces "" (read )
right-failurepassReproduced the reported failure: URI("http://example.com/foo/..").relativeTo("http://example.com/foo/").toString() produces ''; the fix makes it produce '../'.
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 4ad3f29, 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/medialize/URI.js
git checkout 4ad3f2927c5dddce64593bc08cee1678d852c4f5
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