AssertionError: BUG! Couldn't identify the user's access level for these translations.

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

Bug Description

Just saw these appear on edge:

OOPS-1523EA1409, OOPS-1523EB1289, OOPS-1523EB1290, OOPS-1523EC1445, OOPS-1523ED1456
OOPS-1523EB1175, OOPS-1523EC1392, OOPS-1523EC1452, OOPS-1523ED1329

Looks like the attempt to describe the user's access rights falls through because the code doesn't anticipate read-only mode.

Related branches

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Calling this Medium because it falls somewhere between "only happens to a few people in a rare mode" (Low) and "we have a zero-oops policy" (High). The fix is easy, and in the process I learned how to fake read-only mode in a test.

Changed in rosetta:
importance: Undecided → Medium
status: New → In Progress
assignee: nobody → Jeroen T. Vermeulen (jtv)
milestone: none → 10.03
Changed in rosetta:
status: In Progress → Fix Committed
tags: added: qa-needstesting
tags: added: qa-ok
removed: qa-needstesting
Revision history for this message
Ursula Junque (ursinha) wrote : Bug fixed by a commit
tags: added: qa-needstesting
removed: qa-ok
tags: added: qa-ok
removed: qa-needstesting
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.