Uncaught yaml.ParserError
Metadata
Current evaluation
YAML parser tracebacks were fixed by merged snapcore/snapcraft PR #2263 (commit 057f66649), which catches broader YAML exceptions and reports invalid YAML.
Resolution: closed resolved
Reason: PR #2263 was merged as commit 057f66649 and explicitly fixed LP #1792049 by broadening YAML exception handling in ProjectInfo.
Evaluated by: mr-cal-bot
No scores available.
Issue body
YAML ParserErrors are leaking through and causing tracebacks when they should simply be presented to the users as invalid YAML to be fixed.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | YAML parser tracebacks were fixed by merged snapcore/snapcraft PR #2263 (commit 057f66649), which catches broader YAML exceptions and reports invalid YAML. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #2263 (057f66649) broadened YAML exception handling so parser errors are reported as invalid YAML instead of leaking tracebacks. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by commit 057f66649 through PR #2263, adding handling for YAML parsing exceptions to prevent tracebacks. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a documented resolution or fix. The uncaught yaml.ParserError causing tracebacks was not addressed. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The uncaught yaml.ParserError causing tracebacks was not patched or addressed. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution details or comments. The uncaught yaml.ParserError causing tracebacks was not addressed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The uncaught yaml.ParserError causing tracebacks instead of user-friendly messages remains unfixed. The issue appears abandoned due to age and zero activity. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#2263
(confidence 100%)
Merged PR 2263 introduced the resolving YAML exception-handling change.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1686557 Duplicated error message during yaml validation | snapcraft (launchpad) | closed | Fixed duplicated YAML validation errors in snapcore/snapcraft#1347 (commit 9e8e336de) by removing an early exit and consolidating CLI error handling. | |
| #1599098 [parser] Don't explode if snapcraft.yaml is missing | snapcraft (launchpad) | closed | Fixed by merged PR #985 (commit 632022ccd), which replaced the missing snapcraft.yaml traceback with a clearer parser error. | |
| #1605541 snapcraft-parser doesn't work | snapcraft (launchpad) | closed | Fixed in snapcore/snapcraft#681 by making snapcraft-parser handle CRLF-separated YAML documents. | |
| #4342 refactor(parts): separate yaml parsing from base errors | snapcraft | merged | Merged PR #4342 as commit 33356311d, separating YAML parsing from base errors so snapcraft.yaml can be loaded for base checks; no functional changes. | |
| #1787373 snapcraft does not use the C yaml parser | snapcraft (launchpad) | closed | Snapcraft adopted PyYAML's C parser in merged PR #2218 (commit 2e6ed7fd1), replacing yaml.safe_load() with CSafeLoader. | |
| #1608032 snapcraft crashes with useless message on bad YAML | snapcraft (launchpad) | closed | Bad-YAML handling had already been fixed before Sergiusens closed Launchpad #1608032 in August 2020; no resolving PR or commit was linked. |