parser - Differentiate between wiki errors and other errors
Metadata
Current evaluation
Proposal to give snapcraft-parser distinct exit codes for wiki vs other errors was declined. Maintainer ~elopio closed it2016-12-16: no need for other values; reopen if a reason appears. Parser kept returning 1 for all errors.
Resolution: closed not a bug
Reason: No code change was made. The author confirmed snapcraft-parser 2.23 returns 1 on all errors and that the original motivation (avoiding wiki data overwrites) was already handled in the service deployment scripts, and ~elopio closed it stating there was 'no current reason to use other values' unless one arises, in which case the bug would be reopened.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Proposal to give snapcraft-parser distinct exit codes for wiki vs other errors was declined. Maintainer ~elopio closed it2016-12-16: no need for other values; reopen if a reason appears. Parser kept returning 1 for all errors. | |
| stealth/space-bunny-alpha | — | closed not a bug | Parser error differentiation was declined; snapcraft-parser 2.23 continued returning exit code 1 for all errors because maintainers saw no need for separate codes. | |
| stealth/space-bunny-alpha | — | closed resolved | Implemented distinct parser/wiki and network error handling in canonical/snapcraft#1045, commit 66ddbf12e, following the earlier non-zero wiki-error exit handling. | |
| qwen/qwen3.6-35b-a3b | — | — | The parser enhancement to differentiate wiki errors from other errors using distinct return codes was closed without implementation. The request remains abandoned due to lack of discussion or development activity. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The request to differentiate parser error types and return distinct exit codes was abandoned after over nine years with zero comments or activity. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The proposal to differentiate wiki errors from other parser errors and assign distinct return codes was abandoned due to lack of discussion or follow-up. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The proposal to assign distinct return codes for wiki versus other parser errors was abandoned due to lack of discussion or follow-up. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
canonical/snapcraft#658
(confidence 72%)
Earlier merged PR that established the single non-zero exit code for wiki errors that this issue proposed to split; the distinct-code request was closed rather than implemented.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1602394 [parser] Return error codes for YAML and parsing errors | snapcraft (launchpad) | closed | Parser now returns a nonzero status for YAML/wiki errors via merged snapcore/snapcraft#658 (commit bda3b100e); fallback reuse of prior origins was deferred. |