Strange technical error message when querying store
Metadata
Current evaluation
Fixed by snapcore/snapcraft#2094, merged as 0d8602cc5, improving handling and presentation of Store API network errors and retries.
Resolution: closed resolved
Reason: The maintainer linked PR #2094 as the fix, and it was merged in commit 0d8602cc5 with improved Store API network-error handling.
Evaluated by: mr-cal-bot
No scores available.
Issue body
root@snapcrafters:~# snapcraft status ddgr
Retrying (Retry(total=4, connect=None, read=None, redirect=None)) after connection broken by 'NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fc089548e80>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',)': /dev/api/account
Maybe we can suppress that and give a more useful error message?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by snapcore/snapcraft#2094, merged as 0d8602cc5, improving handling and presentation of Store API network errors and retries. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by snapcore/snapcraft#2094, merged as commit 0d8602cc5, improving Store API handling and presentation of network errors. | |
| stealth/space-bunny-alpha | — | closed resolved | Store query network failures were improved in #2094 (commit 0d8602cc5), addressing the exposed urllib3 retry and name-resolution error. | |
| qwen/qwen3.6-35b-a3b | — | — | A report of a raw DNS/connection error during snapcraft status was closed without resolution. The suggestion to improve error messaging was not implemented, indicating the report was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. Closed without comments or resolution, leaving the raw DNS error from snapcraft status unaddressed. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#2094
(confidence 100%)
Merged resolving PR titled "storeapi: better handle network errors and retries."
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4863 fix(cli): properly capture store errors | snapcraft | merged | Merged #4863 in commit 426df7ec3, restoring legacy-style store-error capture so store failures are no longer reported as Snapcraft internal errors. | |
| #1627865 Snapcraft errors when releasing a snap | snapcraft (launchpad) | closed | Resolved by improving snapcraft's error handling to check HTTP status codes before JSON decoding, alongside a fix for the underlying store race condition (bug #1610948). | |
| #585 Improve the store errors returning exceptions | snapcraft | merged | Merged in canonical/snapcraft#585 via commit ddbbdbd06, refactoring store error handling to raise exceptions and addressing LP #1594636. | |
| #5536 fix(store): catch credential decoding errors | snapcraft | merged | Merged in canonical/snapcraft#5536 (commit 3784560f3), converting malformed store credential decoding failures into a user-friendly error and updating craft-store. | |
| #1699232 Incorrect error message when the store returns 400 on login | snapcraft (launchpad) | closed | Fixed as a side effect of snapcore/snapcraft#1936: Snapcraft now displays messages returned by the store instead of labeling every 400 login response as an incorrect password. |