Evidencefast-xml-parser-317
Processing instruction validation error
fast-xml-parser#317, at commit eb8b6c5. A closed issue from a repository Credda did not choose.
LIVE2026-09-20
NOT_EXECUTEDexecuted against the upstream checkout.
- Outcome
- NO_RUNNABLE_CHECK
- Wall time
- 70.4s
- Checks
- 2 passed of 4 applicable
RECORDED
NOT_GRADEDgraded from the transcript committed with this case.
- Outcome
- not recorded
- Checks
- none run
- Repository
- NaturalIntelligence/fast-xml-parser
- Issue
- #317
- Pinned commit
- eb8b6c5ef7e0834fb9b410e60ff15c9257701a62
01The signal
The report, exactly as it was filed.
Nothing paraphrased or cleaned up. The mess is the thing under test.
Processing instruction validation error
* [x] Are you running the latest version?
* [x] Have you included sample input, output, error, and expected output?
* [x] Have you checked if you are using correct configuration?
* [x] Did you try online [tool](https://naturalintelligence.github.io/fast-xml-parser/)?
### Description
Im trying to validate an XML that uses a PI tag at a non-top level, but the validation fails. This [tool](https://onlinexmltools.com/validate-xml) correctly validates the XML, but the `fast-xml-parser` online tool doesn't. Is there a way to ignore those tags? Or this is the expected result?
### Input
```
<?xml version="1.0" encoding="utf-8"?>
<Content><?tibco-char 19?> content</Content>
```
### Code
```js
validate('<?xml version="1.0" encoding="utf-8"?><Content><?tibco-char 19?> content</Content>`);
```
### Output
```
{
err: { code: 'InvalidChar', msg: "char 'c' is not expected.", line: 2 }
}
```
### expected data
```
true
```
**Would you like to work on this issue?**
<!-- choose one by changing [ ] to [x] -->
- [ ] Yes
- [x] No
[Bookmark](https://github.com/NaturalIntelligence/fast-xml-parser/stargazers) this repository for further updates.- Repository
- NaturalIntelligence/fast-xml-parser
- Issue
- #317
- Commit
- eb8b6c5ef7e0834fb9b410e60ff15c9257701a62
- Why this commit
- The first parent of the fix commit ec25c54932863964a844769563fcca0b6ddc9d46, 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
- validate('<?xml version="1.0" encoding="utf-8"?><Content><?tibco-char 19?> content</Content>') does not produce true; the fix makes it do so.
- Expression
- validate('<?xml version="1.0" encoding="utf-8"?><Content><?tibco-char 19?> content</Content>')
- Where that came from
- Proposed by a model reading this report and nothing else -- it never saw the repository or the fix commit -- and read back as a claim by the same parser the harvest uses, SAME_LINE form: `validate('<?xml version="1.0" encoding="utf-8"?><Content><?tibco-char 19?> content</Content>') //=> true`. The report sat in the CODE_NO_ANNOTATION_AT_ALL bucket, which no regex reaches. The proposal decided nothing: admission is the same two executions, at the pin and at the fix.
03What happened
No failure was captured.
Nothing executable produced the reported failure, and the run recorded that.
The LIVE grading as emitted. A check that did not apply is never shown as a pass.
| Check | Result | Detail |
|---|---|---|
| reproduction-executed | fail | Nothing was established: Credda's own sandbox blocked 1 command(s), so no reproduction ran unimpeded. This is not a result about the repository. |
| signature-captured | n/a | The reproduction ran and demonstrated no failure. |
| right-failure | fail | Expected `validate('<?xml version="1.0" encoding="utf-8"?><Content><?tibco-char 19?> content</Content>')` not producing true. |
| 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 eb8b6c5, run the report through the CLI the way the study did.
git clone https://github.com/NaturalIntelligence/fast-xml-parser git checkout eb8b6c5ef7e0834fb9b410e60ff15c9257701a62 npm install CREDDA_PROVIDER=heuristic \ npx tsx apps/cli/src/main.ts fix <repo-path> @<issue-file> --no-color