Last modified: 2014-09-04 13:34:48 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T70472, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 68472 - Flow: reopen topic "Failed contacting Parsoid" API error not reported to user
Flow: reopen topic "Failed contacting Parsoid" API error not reported to user
Status: RESOLVED WORKSFORME
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
master
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-23 20:52 UTC by spage
Modified: 2014-09-04 13:34 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description spage 2014-07-23 20:52:33 UTC
While testing reopen topic, I repeatedly Close topic/Reopen topic on mediawiki.org. After about three attempts, the titlebar stopped responding -- no textarea with a submit button appeared.

In the browser console net tab, the GET api.php action=flow, submodule=view-post, cotmoderationState=reopen request is getting an error response:

  {"servedby":"mw1201","error":{"code":"internal_api_error_Flow\\Exception\\WikitextException","info":"Exception Caught: Failed contacting Parsoid","*":""}}
and the console prints the info message in a warning from FlowBoardComponent.UI.showError(),
but nothing is reported to the user.  All API failures must result in a pink errorbox so the user knows something went wrong.  
To be clear, "Failed contacting parsoid" isn't the issue, not reporting anything is.

I couldn't reproduce on my local wiki. I stopped parsoid while viewing a Flow board. When I clicked Reopen topic the GET succeeded and the form displayed, and it was only when I submitted from the form that the POST got an error, and correctly showed it in an error box.
Comment 1 Danny Horn 2014-07-24 17:59:15 UTC
in backlog: https://trello.com/c/NfsMMzTV
Comment 2 spage 2014-07-30 17:57:20 UTC
This might be fixed by recent changes to error reporting.
Comment 3 Jon 2014-09-04 13:29:04 UTC
Can't replicate the error.
Comment 4 Matthias Mullie 2014-09-04 13:34:48 UTC
Should have been fixed by recent error reporting re-implementation

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links