ISE when trying to access the revision dashboard

RESOLVED FIXED

Status

--
major
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: teoli, Assigned: groovecoder)

Tracking

({in-triage, regression})

Details

(Whiteboard: [specification][type:bug])

(Reporter)

Description

3 years ago
What did you do?
================
1. Go to https://developer.mozilla.org/en-US/dashboards/revisions


What happened?
==============
ISE

What should have happened?
==========================
THe revision dashboard

Is there anything else we should know?
======================================
It is a regression. It is pretty severe as we are not able to fight spam and to review edits.

It is these kinds of pages I have always open and consult 10-30 times a day.
(Reporter)

Comment 1

3 years ago
The revision dashboard must be on the 'must never fail in production' list of items.
Severity: normal → critical
(Reporter)

Comment 2

3 years ago
This happens only when I am logged in. So I'm lowering the priority to major.
Severity: critical → major
Only happens if there is a banned user entry (for which only admins can see who did ban etc.).

Same story as in bug 1178492 which had this PR https://github.com/mozilla/kuma/pull/3292
Keywords: regression
(Assignee)

Comment 4

3 years ago
Bah, sorry I didn't test with a banned user. https://github.com/mozilla/kuma/pull/3479 to revert for now. It was just an optimization. It's more important to have the dashboard working than to have it optimized.

Comment 5

3 years ago
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/976351f08f29f15ed233e2a447819507b013d9cf
Bug 1203403 - Revert commit aad6fce

https://github.com/mozilla/kuma/commit/4f6ae1c38b3370184050fcde4d506bcbffef7fa6
Merge pull request #3479 from mozilla/revert-revisions-ban-1203403

Bug 1203403 - Revert commit aad6fce
Assignee: nobody → lcrouch
Keywords: in-triage
(Reporter)

Comment 7

3 years ago
Closing this, the revision dashboard is working well.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.