MozReview gets into a broken state if I click "Publish" on a review when Bugzilla is down

NEW
Unassigned

Status

MozReview
General
10 months ago
10 months ago

People

(Reporter: dholbert, Unassigned)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

10 months ago
Created attachment 8851115 [details]
screencast of bug

See attached screencast.

Bugzilla is currently kinda-down (though it loads fine for already-logged-in users).  I thought that maybe I could still complete a MozReview review, but actually MozReview ends up in a broken state if I try to complete a review!

See attached screencast. If I click "Publish" on my review, the buttons all get grayed out!! (including "Finished Edit")   This leaves me with no way to dismiss the Edit Review overlay, and it leaves me with the sinking feeling that my review notes may have all just been horked...

Happily, I'm able to regain control if I adjust the r+/r- dropdown -- this forces the buttons to re-compute their enabled/disabled state, I guess.  But until I figured that out, this was pretty scary.
(Reporter)

Updated

10 months ago
Attachment #8851115 - Attachment description: out-6.ogv → screencast of bug
Attachment #8851115 - Attachment filename: out-6.ogv → screencast.ogv
(Reporter)

Updated

10 months ago
Flags: needinfo?(mcote)
(Reporter)

Comment 1

10 months ago
You can see the broken/sinking-feeling state from ~0:08 in my screencast.

I apply the workaround (tweaking r+/r- state) at ~0:15 in my screencast. But until that point, it's unclear what I can do (or whether anything is safe to do) to avoid losing state.

Comment 2

10 months ago
Yeah I agree that behaviour is less than ideal.  Fwiw no information is lost.  What's happening under the hood is that a hook in our extension is called which updates Bugzilla.  This happens before anything is recorded in the Review Board database, so if an error happens (as in this case), all the information is still in the review-request draft object.  The error successfully bubbles, but for some reason the UI gets disabled.  A force-refresh also solves the problem.
Flags: needinfo?(mcote)
You need to log in before you can comment on or make changes to this bug.