Evidencemicromatch-11
problem with "logical OR" or problem in my mind, lol?
micromatch#11, at commit 8078ceb. A closed issue from a repository Credda did not choose.
LIVE2026-09-20
RIGHT_FAILUREexecuted against the upstream checkout.
- Outcome
- ERRORED
- Wall time
- 116.1s
- Checks
- 5 passed of 5 applicable
RECORDED
NOT_GRADEDgraded from the transcript committed with this case.
- Outcome
- not recorded
- Checks
- none run
- Repository
- micromatch/micromatch
- Issue
- #11
- Pinned commit
- 8078ceb31c7f99214d4fd4aeba3710817e9e6bc0
01The signal
The report, exactly as it was filed.
Nothing paraphrased or cleaned up. The mess is the thing under test.
problem with "logical OR" or problem in my mind, lol?
I use makeRe to generate regex based on glob pattern to test against some filepath.
examples
``` js
var expected = false;
var options = {};
var pattern = 'maiden/{**/*.,*.}';
var re = mm.makeRe(pattern, options);
console.log(re.test('maiden/code'));
//=> true
```
isMatch()
``` js
var expected = false;
var options = {};
var pattern = 'maiden/{**/*.,*.}';
var match = mm.isMatch('maiden/code', pattern, options);
console.log(match);
//=> true
```
micromatch()
``` js
var expected = [];
var options = {};
var pattern = 'maiden/{**/*.,*.}';
var match = mm('maiden/code', pattern, options);
console.log(match);
//=> ['maiden/code']
```
I think its logical to return `true` only if there no dots in the pattern, ie `'maiden/{**/*,*}'`- Repository
- micromatch/micromatch
- Issue
- #11
- Commit
- 8078ceb31c7f99214d4fd4aeba3710817e9e6bc0
- Why this commit
- The first parent of the fix commit 1188da22066d7e5fbdbac62bfb3ef233200d05f4, 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.
- Symptom
- (mm.makeRe(('maiden/{**/*.,*.}'), ({}))).test('maiden/code') produces true; the fix makes it produce false.
- Expression
- (mm.makeRe(('maiden/{**/*.,*.}'), ({}))).test('maiden/code')
- Reported output
- true
- Where that came from
- Read mechanically from the report's fenced code, NEXT_LINE form: `console.log(re.test('maiden/code')); //=> true`.
03What happened
The live run reproduced the reported failure.
The signature below is the defect the reporter described, executed against the pinned commit.
`re.test('maiden/code')` still produces true (read true)The LIVE grading as emitted. A check that did not apply is never shown as a pass.
| Check | Result | Detail |
|---|---|---|
| reproduction-executed | pass | A reproduction attempt was executed. |
| signature-captured | pass | `re.test('maiden/code')` still produces true (read true) |
| right-failure | pass | Reproduced the reported failure: (mm.makeRe(('maiden/{**/*.,*.}'), ({}))).test('maiden/code') produces true; the fix makes it produce false. |
| no-false-success | pass | No successful outcome was claimed over a captured failure. |
| no-unproven-success | pass | No 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 8078ceb, run the report through the CLI the way the study did.
git clone https://github.com/micromatch/micromatch git checkout 8078ceb31c7f99214d4fd4aeba3710817e9e6bc0 npm install CREDDA_PROVIDER=heuristic \ npx tsx apps/cli/src/main.ts fix <repo-path> @<issue-file> --no-color