registering too many snaps in a short time period fails without a proper error
Metadata
Current evaluation
Fixed by merged snapcore/snapcraft#630 (commit 1a5ff1f98), adding a clear error when snap registration is attempted too quickly.
Resolution: closed resolved
Reason: PR snapcore/snapcraft#630 was merged as commit 1a5ff1f98 and implemented a specific rate-limit message for rapid registration attempts.
Evaluated by: mr-cal-bot
No scores available.
Issue body
When I try to register a snap right after registerng another one, an error is returned:
Registration failed.
This error should explain that the I am trying to register too many snaps too fast.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged snapcore/snapcraft#630 (commit 1a5ff1f98), adding a clear error when snap registration is attempted too quickly. | |
| stealth/space-bunny-alpha | — | closed resolved | Snap registration rate-limit errors were improved by merged PR #630 (commit 1a5ff1f98), explaining when registration is attempted too quickly. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #630 (commit 1a5ff1f98), adding a clear error for rapid snap registrations instead of the generic 'Registration failed' message. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without comments or resolution. The rate-limiting error for rapid snap registrations was not implemented, indicating the report was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned due to inactivity. The issue requested a specific rate-limiting error when registering snaps too quickly, but no fix was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The rate-limiting error report was abandoned due to inactivity, with no improved messaging or fix implemented. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#630
(confidence 100%)
The linked PR is titled “Report a nice error when registering too fast” and resolving commit 1a5ff1f98.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1596782 Trying to register a snap already registered doesn't explain the error cause | snapcraft (launchpad) | closed | Added a clearer error for duplicate snap registration in snapcore/snapcraft PR #623, commit fca736b61. | |
| #630 Report a nice error when registering too fast | snapcraft | merged | Merged as 1a5ff1f98, adding a clear error when snap registration is attempted too soon and building on #629's already-registered-name handling. | |
| #1598932 Trying to register a snap already reserved doesn't explain the error cause | snapcraft (launchpad) | closed | Fixed by snapcore/snapcraft#629, merged as commit 250a350b9, adding a clearer message when registering a reserved snap name. | |
| #1610776 "snapcraft push" without registering first should fail fast | snapcraft (launchpad) | closed | Fixed by merged PR #1009 (commit 8d7b53aa3), adding a pre-check that rejects unregistered snap names before upload. |