Closed
Bug 844102
Opened 12 years ago
Closed 12 years ago
TBPL does not display errors that occurred during bug starring comment submission
Categories
(Tree Management Graveyard :: TBPL, defect)
Tree Management Graveyard
TBPL
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: emorley)
References
Details
Attachments
(1 file)
1.43 KB,
patch
|
Swatinem
:
review+
|
Details | Diff | Splinter Review |
Starring bugs using a Vagrant TBPL instance currently fails to add a comment to the bug, even with the correct tbplbot credentials filled out in config.php
Similarly, in bug 802104 tbpl-dev wasn't able to submit bug comments, even though no failure message was displayed in the TBPL UI (the root cause there was out of sync credentials in config.php for tbplbot).
We should make submitBugzillaComment.php correctly return failure & then AddCommentUI.js::_postOneBug() handle them, displaying an error in the TBPL message bar (similar to failed retrigger requests).
Assignee | ||
Comment 1•12 years ago
|
||
Ideally we'd split more of this handling out to somewhere central, but at least this gets us error messages for now :-)
[And in the case of bug 844103, revealed that we're hitting the die('Needs CURL!') when using Vagrant]
Comment 2•12 years ago
|
||
Comment on attachment 717209 [details] [diff] [review]
Patch v1
Review of attachment 717209 [details] [diff] [review]:
-----------------------------------------------------------------
As long as the `complete` callback is still being fired this looks good.
Attachment #717209 -
Flags: review?(arpad.borsos) → review+
Assignee | ||
Comment 3•12 years ago
|
||
Yup, I've just checked and the complete still fires fine.
Thank you for the review :-)
https://hg.mozilla.org/webtools/tbpl/rev/c476a0079171
Assignee | ||
Comment 4•12 years ago
|
||
In production :-)
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: Webtools → Tree Management
Updated•10 years ago
|
Product: Tree Management → Tree Management Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•