Handle translation upload approver conflicts

Bug #613823 reported by Jeroen T. Vermeulen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Jeroen T. Vermeulen

Bug Description

We sometimes have failures in the approver: we check for and log approval conflicts (but we don't normally see the log output any more) and it still violates the occasional unique constraint (as in bug 613821). These should be logged as oopses so we can track them properly.

Related branches

tags: added: tech-debt
Changed in rosetta:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Actually, approval conflicts are now things that users can address and should know about. So no need to oops: notify!

summary: - Approver should log oopses
+ Handle translation upload approver conflicts
Changed in launchpad:
importance: Low → High
status: Triaged → In Progress
assignee: nobody → Jeroen T. Vermeulen (jtv)
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
William Grant (wgrant) wrote :

https://translations.qastaging.launchpad.net/api/devel/+imports/4890787 is one that has been cronspamming us for a while, and it has error_output set correctly.

tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
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.