Cycles in team data kill mailing lists
Bug #214843 reported by
Barry Warsaw
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Barry Warsaw | ||
Bug Description
The ubuntume.team is a member of itself. This causes a cycle in the calculation of the notification recipients for when a mailing list gets created. That causes an infinite recursion error in Python, which in turn Faults Mailman's XMLRPC runner. This means that no mailing list creations ever get acknowledged to Launchpad.
The zero-order fix is to fix the data, and that has been requested. First order fix is to refactor the XMLRPCRunner to call reportStatus() individually for each list that it's taking action on. That way if one team is hosed, it doesn't crash things for all teams.
For robustness, all reportStatus() calls should be so refactored.
OOPS-830XMLP2
Exception type RuntimeError
Exception value maximum recursion depth exceeded
| Changed in launchpad: | |
| assignee: | nobody → barry |
| importance: | Undecided → Critical |
| milestone: | none → 1.2.4 |
| status: | New → Confirmed |
Revision history for this message
| Guilherme Salgado (salgado) wrote Re: [Bug 214843] [NEW] Cycles in team data kill mailing lists | #1 |
| description: | updated |
| Changed in launchpad: | |
| importance: | Critical → High |
| Changed in launchpad: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Barry Warsaw (barry) wrote | #2 |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Do we know how people managed to add a team as a member of itself? The
+addmember page doesn't allow that, for sure.
I think the only way would be for a member to propose the team as a
member of itself and then one of the team admins approve later.
subscribe