Closed
Bug 1164289
Opened 10 years ago
Closed 9 years ago
reverting to prior rules and releases is busted
Categories
(Release Engineering Graveyard :: Applications: Balrog (frontend), defect)
Release Engineering Graveyard
Applications: Balrog (frontend)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hwine, Assigned: bhearsum)
Details
Attachments
(1 file)
|
41 bytes,
text/x-github-pull-request
|
nthomas
:
review+
bhearsum
:
checked-in+
|
Details | Review |
When attempting to disable updates to 38.0, I could not revert to the prior rule from the history view.
When I attempted that, I got a series of "are you sure" alerts. Clicking "yes" visibly dismissed the alert, only to be replaced by a new instance of the same alert.
| Assignee | ||
Comment 1•10 years ago
|
||
I repro'ed this in dev. The response the UI gets back is a 400 which says "no change_id". The request payload is:
{"change_id":512,"csrf_token":"xxxxxxxxxxxxxxxxxxxx"}
...so something is messed up, clearly. It wouldn't shock me if one or both of bug 1163170 or bug 1129149 are rooted in the same issue. Seems like there's some general wonkiness around the history UI.
Comment 2•10 years ago
|
||
Saw this today too. Any idea which bug you mean instead of bug 1163170 ?
| Assignee | ||
Comment 3•9 years ago
|
||
I rediscovered this bug today, and found a fix. I'll post it once I get a regression test or two written.
Assignee: nobody → bhearsum
| Assignee | ||
Updated•9 years ago
|
Summary: could not revert to prior rule → reverting to prior rules and releases is busted
| Assignee | ||
Comment 4•9 years ago
|
||
Attachment #8698972 -
Flags: review?(nthomas)
Comment 5•9 years ago
|
||
Commits pushed to master at https://github.com/mozilla/balrog
https://github.com/mozilla/balrog/commit/2d6aa83a7ee90232c8054fe0b6fe31699ef6d4af
bug 1164289: reverting to prior rules and releases is busted.
https://github.com/mozilla/balrog/commit/f916721837fa9b173fc29675df69f6279b434a40
Merge pull request #34 from bhearsum/fix-revert-button
bug 1164289: reverting to prior rules and releases is busted. r=nthomas
| Assignee | ||
Comment 6•9 years ago
|
||
(In reply to Nick Thomas [:nthomas] (away Dec 21-Jan 24) from comment #2)
> Saw this today too. Any idea which bug you mean instead of bug 1163170 ?
Just saw this comment...no idea which bug I meant =\.
Comment 7•9 years ago
|
||
Comment on attachment 8698972 [details] [review]
look for json data instead of basic form data
Oops, r+'d on github but not here.
Attachment #8698972 -
Flags: review?(nthomas) → review+
| Assignee | ||
Updated•9 years ago
|
Attachment #8698972 -
Flags: checked-in+
| Assignee | ||
Comment 8•9 years ago
|
||
This is now in production and working.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•