remote build: internal error from 400 response
Metadata
Current evaluation
Remote builds expose an internal error when Launchpad returns HTTP 400 while pushing the repository; the triaged bug remains open and likely requires a Craft Application fix.
Suggested action: keep open
Reason: The maintainer-filed issue is labeled Triaged and Bug, identifies the exact uncaught lazr.restfulclient.errors.BadRequest, and links a failure log. Current Craft Application code catches BadRequest around recipe and build operations but has no equivalent handling in the Git repository token or push path, so the reported UX defect remains valid.
Evaluated by: mr-cal-bot
Impact:
38
Quick Win:
21
Complexity:
35
Confidence:
91
Actionability:
84
Issue body
### What needs to get done
Catch and raise a user-friendly error when Snapcraft fails to push a repo to Launchpad. This likely needs to be fixed upstream in Craft Application.
We already catch many `launchpadlib` errors but `lazr.restfulclient.errors.BadRequest` isn't being caught when pushing the repo.
### Why it needs to get done
To provide a better UX. Internal errors should never be exposed.
Source:
- @jnsgruk via [matrix](https://matrix.to/#/!fcfzhmtmKApekMQcxX:ubuntu.com/$i_-XIB1IDWrY4w7j16LkWR9-9JFwtVsPv4t65wpbsgg?via=ubuntu.com&via=matrix.org)
- [snapcraft-20250527-114721.927489.log](https://github.com/user-attachments/files/20458454/snapcraft-20250527-114721.927489.log)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
21
Complexity:
35
Confidence:
91
Actionability:
84
|
keep open | Remote builds expose an internal error when Launchpad returns HTTP 400 while pushing the repository; the triaged bug remains open and likely requires a Craft Application fix. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
19
Complexity:
20
Confidence:
85
Actionability:
80
|
close resolved | Legacy remote builder error handling for uncaught lazr.restfulclient.errors.BadRequest during Launchpad repo push. The legacy remote builder has been removed from snapcraft, eliminating this code path. | |
| qwen/qwen3.8-27b |
Impact:
50
Quick Win:
30
Staleness:
70
Complexity:
40
Confidence:
60
Support Request:
10
|
keep open | Snapcraft remote build exposes an internal error when Launchpad returns a 400 (BadRequest) during repo push; the lazr.restfulclient.errors.BadRequest exception is not caught. Triaged as a bug, fix likely needed upstream in Craft Application. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
30
Confidence:
90
Support Request:
10
|
keep open | Tracks catching and handling lazr.restfulclient.errors.BadRequest during Launchpad repo pushes to prevent internal errors. Currently triaged and awaiting implementation. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
75
Support Request:
0
|
keep open | Valid bug report requesting better error handling for Launchpad push failures. Triaged but inactive for over a year with no upstream fix or maintainer follow-up. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5960 remote build: internal error when build is cancelled on launchpad | snapcraft | open | remote-build crashes with internal error MissingSchema when a build is cancelled on Launchpad (build_log_url is the string "None"); acknowledged by mr-cal, tracked upstream in craft-application#996 and Jira SNAPCRAFT-1281, still unfixed. |