Repository navigation
Conversation
CaiJimmy
force-pushed
the
jimmy/better-xml-error
branch
from
October 4, 2026 22:25
1be5bb2 to
2f8467d
Compare
QT3 Test Results - Parser:
|
| Test Suite | Passing | Failing | Errors | Skipped | Missing features | Total |
|---|---|---|---|---|---|---|
app |
2037 | 27 | 88 | 5 | 5 | 2157 |
array |
208 | 0 | 1 | 0 | 0 | 209 |
fn |
10308 | 270 | 170 | 387 | 315 | 11135 |
map |
220 | 0 | 0 | 0 | 0 | 220 |
math |
149 | 0 | 0 | 0 | 0 | 149 |
misc |
764 | 34 | 21 | 52 | 18 | 871 |
op |
4339 | 4 | 23 | 0 | 0 | 4366 |
prod |
11469 | 343 | 187 | 208 | 7 | 12207 |
ser |
332 | 11 | 0 | 0 | 0 | 343 |
xs |
155 | 0 | 0 | 9 | 0 | 164 |
| Total | 29981 | 689 | 490 | 661 | 345 | 31821 |
Full analysis report: see analysis-jsoniq in artifacts.
QT3 Test Results - Parser:
|
| Test Suite | Passing | Failing | Errors | Skipped | Missing features | Total |
|---|---|---|---|---|---|---|
app |
2044 | 26 | 82 | 5 | 5 | 2157 |
array |
209 | 0 | 0 | 0 | 0 | 209 |
fn |
10330 | 249 | 169 | 387 | 315 | 11135 |
map |
220 | 0 | 0 | 0 | 0 | 220 |
math |
149 | 0 | 0 | 0 | 0 | 149 |
misc |
768 | 30 | 21 | 52 | 18 | 871 |
op |
4339 | 4 | 23 | 0 | 0 | 4366 |
prod |
11550 | 295 | 154 | 208 | 7 | 12207 |
ser |
343 | 0 | 0 | 0 | 0 | 343 |
xs |
155 | 0 | 0 | 9 | 0 | 164 |
| Total | 30107 | 604 | 449 | 661 | 345 | 31821 |
Full analysis report: see analysis-xquery in artifacts.
CaiJimmy
force-pushed
the
jimmy/fix-element-type
branch
from
October 6, 2026 21:21
1edd792 to
dfb2ff8
Compare
CaiJimmy
force-pushed
the
jimmy/better-xml-error
branch
from
October 6, 2026 21:22
2f8467d to
ad50c0c
Compare
CaiJimmy
force-pushed
the
jimmy/fix-element-type
branch
from
October 6, 2026 23:39
dfb2ff8 to
28c5994
Compare
CaiJimmy
force-pushed
the
jimmy/better-xml-error
branch
from
October 6, 2026 23:39
ad50c0c to
00addb9
Compare
Callers pass a description of the input, and every parse error reads "Unable to parse <input> at line L, column C: <reason>". Fragment errors in the synthetic closing tag are reported at the end of the input instead of at a recomputed position. Keep one test per diagnostic behavior.
CaiJimmy
force-pushed
the
jimmy/better-xml-error
branch
from
October 8, 2026 20:29
b886320 to
c00d8a2
Compare
CaiJimmy
marked this pull request as ready for review
October 8, 2026 20:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
XML inputs are now parsed through one helper,
XmlParsingUtils, so every entry point reports parse errors the same way:Previously each of
fn:doc,fn:doc-available,fn:parse-xml,fn:parse-xml-fragment,jn:xml-filesand serialization parameter documents created its own parser, and onlyfn:docreported the position and reason.Behavior changes
jn:xml-filesraises FODC0002 naming the file and position, instead of a genericRuntimeExceptionwhose message contained the whole file. It also keeps the file's line breaks, so reported lines are correct.fn:parse-xmlandfn:parse-xml-fragmentinclude the parser's reason and the position in the input (FODC0006, unchanged). Fragment positions are relative to the argument, not the internal wrapper element.fn:doc-availableand the parse functions no longer print parser errors to stderr.Error metadata still points to the call in the query; the position inside the XML is part of the message. Apart from
jn:xml-files, error codes are unchanged.