Last modified: 2014-01-22 19:30:26 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 T54563, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 52563 - VisualEditor: Don't wait indefinitely for gadget servers that are not responding
VisualEditor: Don't wait indefinitely for gadget servers that are not responding
Status: RESOLVED INVALID
Product: VisualEditor
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: James Forrester
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-05 21:53 UTC by Chris McKenna
Modified: 2014-01-22 19:30 UTC (History)
3 users (show)

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


Attachments

Description Chris McKenna 2013-08-05 21:53:36 UTC
When a user has installed a gadget that relies on data from an external server, VisualEditor appears to wait indefinitely for that server to respond. Normally this is OK, but when that server is down VE will apparently wait forever (or at least longer than the 5 minutes I was prepared to wait) for a response.

The source editor appears to give up after a wile (2 minutes?), and loads as if the gadget was not called. VE should exhibit this behaviour too.

Tested with the HAPPI gadget ([[User:EpochFail/HAPPI]]). As of 21:52 UTC 05 August 2013 that gadget depends on a server at wikipedia.grouplens.org that is not responding
Comment 1 James Forrester 2014-01-22 19:30:26 UTC
Surely this is the responsibility of the gadget's author?

Also, not sure if the wikitext editor executes poorly-responding gadgets, or it's just apparent happenstance. Either way, 120 seconds is about an order of magnitude too high.

Sorry for very slow triage.

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


Navigation
Links