DataError: OFFSET must not be negative

[Diogo Matsubara]

As seen on OOPS-2049AW40 a DataError: OFFSET must not be negative was logged accessing the +translate page.

It seems like an URL hack given that the OOPSes have no referrer. In any case the page shouldn't oops or at least raise a UnexpectedFormData error

Another oops: OOPS-2054H61: ForbiddenAttribute: ('__len__', <storm.sqlobject.SQLObjectResultSet object at 0x1269f150>) was recorded when Brad tried to reproduce this bug.

[Brad Crittenden (bac)]

I've tried to replicate the original problem by hacking the following URL to mimic what I see in the OOPS (note there is no 'memo' field):

https://translations.launchpad.net/transmission/trunk/+pots/transmission/vi/+translate?direction=backwards&start=180

There is no OOPS but the numbering of the items is incorrect as it shows "181 -> 186 of 476" but the first item is 471. See the attached screenshot

[Brad Crittenden (bac)]

Aha! The OOPS seems to be triggered by attempting to view a translations page with "show=untranslated" and "direction=backwards" when there are no untranslated messages. Probably would happen any time the filter does not match and a direction is given.

[Launchpad QA Bot (lpqabot)]

Fixed in stable r13743 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/13743>.

[Brad Crittenden (bac)]

https://translations.qastaging.launchpad.net/transmission/trunk/+pots/transmission/eu/+translate?start=0&batch=10&show=untranslated&direction=backwards

The Basque (eu) translation on qastaging has zero untranslated strings. Using the above URL to replicate the problem of going backwards in an empty result set did not OOPS. The problem is fixed.