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