packaging portlet cause timeout on distroseries index
Bug #612358 reported by
Curtis Hovey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Robert Collins |
Bug Description
OOPS-1673S138 and OOPS-1673S140 show that the timeout issue is not fixed on staging, and the oops continue to appear on edge.
To QA this, visit a distroseries - e.g. /ubuntu/lucid - and it should not time out, and should show the number of linked packages.
Related branches
lp://qastaging/~jcsackett/launchpad/packaging-portlet-timeouts
- Brad Crittenden (community): Approve (code)
- Robert Collins (community): Approve
-
Diff: 69 lines (+4/-23)4 files modifiedlib/lp/registry/browser/distroseries.py (+3/-1)
lib/lp/registry/browser/tests/test_distroseries_views.py (+1/-4)
lib/lp/registry/stories/distroseries/xx-distroseries-index.txt (+0/-4)
lib/lp/registry/templates/distroseries-portlet-packaging.pt (+0/-14)
lp://qastaging/~lifeless/launchpad/registry-packagings
- Robert Collins (community): Approve (release-critical)
- Curtis Hovey (community): Approve
- Julian Edwards: Pending (release-manager) requested
-
Diff: 86 lines (+23/-9)3 files modifiedlib/lp/registry/browser/distroseries.py (+1/-1)
lib/lp/registry/doc/distroseries.txt (+1/-1)
lib/lp/registry/model/distroseries.py (+21/-7)
tags: | added: bridging-the-gap |
summary: |
- packing portlet cause timeout on distroseries index + packaging portlet cause timeout on distroseries index |
Changed in launchpad-registry: | |
assignee: | nobody → j.c.sackett (jcsackett) |
status: | Triaged → In Progress |
Changed in launchpad-registry: | |
status: | In Progress → Fix Committed |
description: | updated |
Changed in launchpad-registry: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Still saw timeouts in this on sunday: https:/ /lp-oops. canonical. com/oops. py/?oopsid= 1681EB3871
However, this may *not* be the packaging portlet.
The oops traceback shows the portlet, *but* the timeout is triggering on the first storm query *after* 15 seconds of non-sql activity.
So, the packaging portlet may simply be *the first thing showing after the bad code* : we need to look more deeply.