Merge lp:~allenap/launchpad/bugwatch-bugtasks-as-a-list into lp:launchpad
Proposed by
Gavin Panella
Status: | Merged |
---|---|
Approved by: | Brad Crittenden |
Approved revision: | not available |
Merged at revision: | not available |
Proposed branch: | lp:~allenap/launchpad/bugwatch-bugtasks-as-a-list |
Merge into: | lp:launchpad |
Diff against target: |
164 lines (+38/-20) 4 files modified
lib/lp/bugs/browser/bugwatch.py (+1/-3) lib/lp/bugs/model/bugtask.py (+0/-1) lib/lp/bugs/model/bugwatch.py (+17/-13) lib/lp/bugs/tests/test_bugwatch.py (+20/-3) |
To merge this branch: | bzr merge lp:~allenap/launchpad/bugwatch-bugtasks-as-a-list |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Данило Шеган (community) | release-critical | Approve | |
Brad Crittenden (community) | code | Approve | |
Review via email: mp+16200@code.launchpad.net |
Commit message
Make BugWatch.bugtasks a list instead of a result set. This may help us narrow down the causes behind the 2009-12-14 outage.
To post a comment you must log in.
Change BugWatch.bugtasks into a property that returns a list, instead of being a SQLMultipleJoin which returns a result set. This relates to:
https:/ /wiki.canonical .com/IncidentRe ports/2009- 12-14-Launchpad -Appserver- Outage
The long-lived query in the paste linked to from the report seems to have come from this bugtasks property. By changing it to immediately suck the results back from the DB we (gmb and I) hope to try and isolate the real issue, or at least narrow it down.