Cycles in team data kill mailing lists

Bug #214843 reported by Barry Warsaw on 2008-04-09
Affects Status Importance Assigned to Milestone
Launchpad itself
Barry Warsaw

Bug Description

The 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.

Exception type RuntimeError
Exception value maximum recursion depth exceeded

Barry Warsaw (barry) on 2008-04-09
Changed in launchpad:
assignee: nobody → barry
importance: Undecided → Critical
milestone: none → 1.2.4
status: New → Confirmed
  • unnamed Edit (189 bytes, application/pgp-signature; name=signature.asc)

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.


description: updated
Barry Warsaw (barry) on 2008-04-10
Changed in launchpad:
importance: Critical → High
Barry Warsaw (barry) on 2008-04-10
Changed in launchpad:
status: Confirmed → In Progress
Barry Warsaw (barry) wrote :

The first order fix is working its way through pqm.

Barry Warsaw (barry) on 2008-04-15
Changed in launchpad:
status: In Progress → Fix Committed
Barry Warsaw (barry) on 2008-05-06
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments