When batch_start is >= the number of bugs shown, an error is raised

Bug #1235 reported by Steve Alexander
6
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Andrew Bennetts

Bug Description

When batch_start is >= the number of bugs shown, an error is raised.

For example (there are 412 bugs in the list of results as I write these example URLs):

<https://launchpad.net/products/launchpad/+bugs?batch_start=411&batch_end=412>

renders correctly, but

<https://launchpad.net/products/launchpad/+bugs?batch_start=412&batch_end=413>

raises an IndexError.

Steve Alexander (stevea)
summary: Going to a page that is past the last page of results gives a
- SystemError
+ SystemError. Instead, it should retain normal valid batch navigation
+ controls, and should say "There are no more results." rather than show
+ any results.
Changed in launchpad:
assignee: nobody → bjornt
Revision history for this message
Dafydd Harries (daf) wrote :

Does this bug still apply?

Revision history for this message
Björn Tillenius (bjornt) wrote :

Yes. I haven't seen this error in the error logs, though, so it hasn't had much priority.

Changed in launchpad:
status: New → Accepted
description: updated
Brad Bollenbach (bradb)
description: updated
summary: - Going to a page that is past the last page of results gives a
- SystemError. Instead, it should retain normal valid batch navigation
- controls, and should say "There are no more results." rather than show
- any results.
Revision history for this message
Björn Tillenius (bjornt) wrote : Re: [Bug 1235] When batch_start is >= the number of bugs shown, an error is raised

On Mon, Jan 09, 2006 at 02:51:55PM -0000, Brad Bollenbach wrote:
> Changed in: Launchpad (upstream)
> Priority: Medium => Low
> Explanation: With the new navigation controls, I believe this will
> only happen if the user hand-hacks the batch_start
> parameter. I'd need to test more to see if other
> conditions cause it to occur.

I'm not sure which new navigation controls you're referring to, so I
might be wrong. But I think that this still can happen without
hand-hacking the URL. Let's say that you have two pages, one with 20
bugs, the other with 1 bug. From the first page you go to edit a bug,
which results in the bug being removed from the bug listing (for
example by marking the bug Fixed). Now you should have only one page
with 20 bugs, but since there's no way getting back to the bug listing
without using the back button, you press the back button and get a
cached version of the page, with the possibility to navigate to the
now non-existant page.

Revision history for this message
Christian Reis (kiko) wrote :

This also happens when we hand-hack a URL, or when someone modifies the set we are viewing (mass-closing or reassigning, for instance) between page views.

OOPS-59A361

Andrew Bennetts (spiv)
Changed in launchpad:
assignee: bjornt → spiv
status: Confirmed → In Progress
Andrew Bennetts (spiv)
Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
Andrew Bennetts (spiv) wrote :
Changed in launchpad:
status: Fix Committed → 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.