Timeout merging big teams
Bug #156217 reported by
Diogo Matsubara
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Edwin Grubbs | ||
Bug Description
1. Open https:/
2. Fill in "Duplicated team": ubuntu-art
3. Fill in "Target team": motu
4. Click Merge
5. Click Deactivate Members and merge
6. OOPS-661S36
Please complete the following once this bug has been fixed:
1. https:/
Revision history for this message
| Guilherme Salgado (salgado) wrote | #1 |
Revision history for this message
| Guilherme Salgado (salgado) wrote | #2 |
Revision history for this message
| Guilherme Salgado (salgado) wrote | #3 |
| Changed in launchpad: | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
| Changed in launchpad-registry: | |
| status: | Confirmed → Triaged |
Revision history for this message
| Diogo Matsubara (matsubara) wrote | #4 |
| tags: |
added: chr registry-people removed: registry |
Revision history for this message
| Gavin Panella (allenap) wrote | #5 |
| description: | updated |
| Changed in launchpad-registry: | |
| assignee: | nobody → Edwin Grubbs (edwin-grubbs) |
| Changed in launchpad-registry: | |
| status: | Triaged → In Progress |
| Changed in launchpad-registry: | |
| importance: | Low → High |
| milestone: | none → 2.2.7 |
| status: | In Progress → Fix Committed |
Revision history for this message
| Edwin Grubbs (edwin-grubbs) wrote | #6 |
Revision history for this message
| Khairul Aizat Kamarudzzaman (fenris) wrote | #7 |
Revision history for this message
| Curtis Hovey (sinzui) wrote Bug 156217 Fix released | #8 |
| Changed in launchpad-registry: | |
| status: | Fix Committed → Fix Released |
| tags: |
added: merge-deactivate removed: registry-people |
To post a comment you must log in.
As we can see in the OOPS, the timeout happens before we even start the merge. It times out when we try to deactivate all active members of the team (nearly 400) so that we can actually do the merge.
We may look into improving the functions which maintain the TeamParticipate table so that they issue less queries, but since this will only happen if we try to merge teams with /lots/ of members (which is something I don't think people will be doing in practice), I don't think it's something we need to worry about now.