"There are 50 errors" when updating import queue entry status

Bug #139176 reported by Данило Шеган
6
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Данило Шеган

Bug Description

Go to a filtered, multi-batch translation import queue page, e.g.: https://translations.edge.launchpad.net/+imports/+index?field.filter_target=all&field.filter_status=NEEDS_REVIEW&field.filter_extension=pot&start=50&batch=50 and try to change status for any entry to eg. "Blocked".

It fails and a first batch is shown along with the error message "There are 50 errors." (it probably tries to set this on the first batch, but IDs don't match).

Similarly, if you hack a URL and use larger batch size and start from the beginning, eg.
 https://translations.edge.launchpad.net/+imports/+index?field.filter_target=all&field.filter_status=NEEDS_REVIEW&field.filter_extension=pot&start=0&batch=100

you still won't be able to set the status, because it again shows you just a first default batch.

Revision history for this message
Данило Шеган (danilo) wrote :

Also, changing entries which are among the first fifty in the batch even on a page with 100 entries still works.

Changed in rosetta:
assignee: nobody → carlos
importance: Undecided → Medium
status: New → Confirmed
Changed in rosetta:
assignee: carlos → nobody
Changed in rosetta:
importance: Medium → High
description: updated
Revision history for this message
Matthew East (mdke) wrote :

I had this problem (or a different one?) when attempting to delete a template which I'd accidentally imported in the wrong place, from this url:

https://translations.edge.launchpad.net/ubuntu/intrepid/+source/ubuntu-docs/+imports?field.filter_status=all&field.filter_extension=pot

The error message was: "There are 19 errors." Obviously, it didn't tell me what the errors were, that would be too easy.

Revision history for this message
Данило Шеган (danilo) wrote :

I believe functionality provided by lp:~michael.nelson/launchpad/batchnavigator_use_query_string should help resolve this in an easy and elegant way (used for bug 225131 fix).

Revision history for this message
Данило Шеган (danilo) wrote :

It seems the elegant and easy fix after Michael's branch landed consisted of QAing that everything works. It does now.

Changed in rosetta:
assignee: nobody → danilo
milestone: none → 2.2.2
status: Triaged → Fix Committed
Changed in rosetta:
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.