same error for app command not existent and not executable
Metadata
Current evaluation
Fixed by PR #2539 in commit e0cb7cb94, adding distinct InvalidAppCommand errors for non-existent and non-executable commands.
Resolution: closed resolved
Reason: Merged PR #2539 added separate InvalidAppCommand errors for missing and non-executable commands, replacing the ambiguous message with actionable diagnostics.
Evaluated by: mr-cal-bot
No scores available.
Issue body
When running snapcraft on a project with an unexisting command defined in an app, or when the command is not executable, the same error message is returned.
This is a problem because then there is no nice way to explain how to fix the problem. Instead of showing the same error, there should be one error for unexisting and a different one for not executable. That way the instructions on how to fix it will be clear and precise.
To reproduce, run snapcraft on a project with something like:
apps:
test:
command: idontexist
$ snapcraft
The specified command 'idontexist' defined in the app 'test' does not exist or is not executable
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by PR #2539 in commit e0cb7cb94, adding distinct InvalidAppCommand errors for non-existent and non-executable commands. | |
| stealth/space-bunny-alpha | — | closed resolved | Resolved by merged PR #2539 (commit e0cb7cb94), adding distinct InvalidAppCommand errors for missing and non-executable app commands. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a fix after prolonged inactivity; the combined error for missing and non-executable app commands remained unresolved. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The request to differentiate error messages for missing versus non-executable snapcraft app commands was abandoned due to prolonged inactivity. No fix or merge was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Distinct error messages for missing versus non-executable snapcraft app commands were not implemented. The request was closed without resolution or comments, indicating it was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. Implemented distinct error messages for non-existent versus non-executable snapcraft app commands, resolving the validation ambiguity and improving user guidance. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned. Distinct error messages for non-existent versus non-executable snapcraft app commands were never implemented. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#2539
(confidence 100%)
PR #2539 was linked in the closing comment and is recorded in commit e0cb7cb94.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2539 errors: Add InvalidAppCommand errors for non-existent and not-found | snapcraft | merged | Merged PR #2539 via commit e0cb7cb94, adding InvalidAppCommand errors for missing and non-executable app commands. | |
| #3321 meta: add error check for "command not found" | snapcraft | merged | Merged in snapcraft#3321 via commit 44930f709: missing app commands now raise InvalidAppCommandNotFound; PrimedCommandNotFoundError was removed and unit tests added. |