Timeout when adding ~canonical (400 people) to private PPA
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Данило Шеган |
Bug Description
Variety of error messages when adding (trying to add) ~canonical to private PPA
Timeout error
Sorry, something just went wrong in Launchpad.
We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.
Trying again in a couple of minutes might work.
(Error ID: OOPS-1810C878)
The above failed, but:
Please try again
Sorry, there was a problem connecting to the Launchpad server.
Try reloading this page in a minute or two. If the problem persists, let us know in the #launchpad IRC channel on Freenode.
Thanks for your patience.
the latter succeeded. I wonder if there are better error messages that could be passed back to the User?
On QA staging: OOPS-2050QASTAGING39
Related branches
- Henning Eggers (community): Approve
-
Diff: 246 lines (+62/-46)4 files modifiedlib/canonical/launchpad/mailnotification.py (+2/-7)
lib/lp/soyuz/doc/archivesubscriber.txt (+22/-15)
lib/lp/soyuz/interfaces/archivesubscriber.py (+5/-3)
lib/lp/soyuz/model/archivesubscriber.py (+33/-21)
tags: | added: timeout |
Changed in soyuz: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in launchpad: | |
importance: | High → Critical |
description: | updated |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
The OOPS report doesn't seem to really correspond to the problem: perhaps something else still has no OOPS prefix set and has overwritten the OOPS from the appserver (process-mail on staging?).