Closed
Bug 1433825
Opened 8 years ago
Closed 8 years ago
If I try to tag a comment, it triggers a red error-box saying e.g. "13001142 is not a valid comment id"; and bug pages sometimes trigger "Missing Bug ID" error page
Categories
(bugzilla.mozilla.org :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dholbert, Unassigned)
Details
Attachments
(2 files)
|
127.22 KB,
image/png
|
Details | |
|
248.36 KB,
image/png
|
Details |
STR:
0. Be logged in to bugzilla.mozilla.org
1. Visit some BMO bug page (e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=1431565 or probably this very bug page here)
2. Click "Tag" at the top right of some comment box.
ACTUAL RESULTS:
Sometimes, a red box appears below the "Add Tag" textfield that says e.g.
"13001142 is not a valid comment id."
(In practice, this does not seem to actually block me from adding a tag, but it superficially looks broken & reduces my confidence that the tag will stick.)
EXPECTED RESULTS:
No such red box.
I'm using Firefox Nightly 60.0a1 (2018-01-27) (64-bit) on Ubuntu 17.10 64-bit
| Reporter | ||
Comment 1•8 years ago
|
||
Relatedly: if I try to load this very bug page ( https://bugzilla.mozilla.org/show_bug.cgi?id=1433825 ) in a fresh profile, then half the time I get an error page saying...
> Missing Bug ID
> You must enter a valid bug number!
...and half the time it works. (And if I reload, I randomly get a working result vs. a broken result.)
Seems like maybe one of the bugzilla servers is busted, and I'm getting arbitrarily load-balanced between the broken server & a working one...?
Summary: If I try to tag a comment, it triggers a red error-box saying e.g. "13001142 is not a valid comment id" → If I try to tag a comment, it triggers a red error-box saying e.g. "13001142 is not a valid comment id"; and bug pages sometimes trigger "Missing Bug ID" error page
| Reporter | ||
Updated•8 years ago
|
Attachment #8946170 -
Attachment description: screenshot → screenshot of error when trying to tag
| Reporter | ||
Comment 2•8 years ago
|
||
| Reporter | ||
Comment 3•8 years ago
|
||
cvalaas took some action on a long-running database operation of some sort, and that seems to have fixed things. (I can't reproduce comment 0 or comment 1 anymore, at least.)
--> WFM
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•