Default content of the /people collection times out

Bug #244282 reported by Guilherme Salgado
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Guilherme Salgado

Bug Description

We use PersonSet.find() as the default content for the collection exposed as /people. That's problematic because PersonSet.find("") will issue a query which takes too long to run, as seen in OOPS-912S19.

We should probably keep PersonSet.find() exposed (but change it to fail when an empty string is passed) and used something else as that collection's default content.

Changed in launchpad:
assignee: nobody → salgado
importance: Undecided → High
milestone: none → 1.2.6
status: New → Confirmed
Changed in launchpad:
status: Confirmed → In Progress
Changed in launchpad:
milestone: 1.2.6 → 1.99
Revision history for this message
Guilherme Salgado (salgado) wrote :

landed on mainline r6634

Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
Guilherme Salgado (salgado) wrote :

Reopening as it's still taking too long (7s SQL time). I have a fix already but it depends on a couple other fixes to storm which are going to land next week after Monday's roll out.

Changed in launchpad:
status: Fix Committed → In Progress
Changed in launchpad:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.