Issue 127 in perlwikipedia: When remote end hangs up, don't wait forever

0 views
Skip to first unread message

perlwi...@googlecode.com

unread,
Aug 13, 2010, 5:48:20 PM8/13/10
to perlwiki...@googlegroups.com
Status: New
Owner: mike.lifeguard
Labels: Type-Defect Priority-Medium

New issue 127 by mike.lifeguard: When remote end hangs up, don't wait
forever
http://code.google.com/p/perlwikipedia/issues/detail?id=127

When the Commons API was hanging up on us, test scripts simply waited
forever. This shouldn't happen. It might be more appropriate to report this
to MediaWiki::API.

perlwi...@googlecode.com

unread,
Sep 19, 2010, 5:07:27 PM9/19/10
to perlwiki...@googlegroups.com
Updates:
Owner: ---
Cc: mike.lifeguard
Labels: -Priority-Medium Priority-High

Comment #1 on issue 127 by mike.lifeguard: When remote end hangs up, don't
wait forever
http://code.google.com/p/perlwikipedia/issues/detail?id=127

(No comment was entered for this change.)

perlwi...@googlecode.com

unread,
Oct 24, 2010, 8:36:18 PM10/24/10
to perlwiki...@googlegroups.com
Updates:
Status: Invalid

Comment #2 on issue 127 by mike.lifeguard: When remote end hangs up, don't
wait forever
http://code.google.com/p/perlwikipedia/issues/detail?id=127

Yeah, I think this isn't something that needs to be fixed in our codebase.
Someone should work with Jools to fis this in MediaWiki::API.

perlwi...@googlecode.com

unread,
Jan 13, 2011, 10:09:32 PM1/13/11
to perlwiki...@googlegroups.com
Updates:
Status: Started
Owner: mike.lifeguard

Comment #3 on issue 127 by mike.lifeguard: When remote end hangs up, don't
wait forever
http://code.google.com/p/perlwikipedia/issues/detail?id=127

We apparently told MediaWiki::API to keep trying forever. D'oh!

perlwi...@googlecode.com

unread,
Jan 13, 2011, 10:13:34 PM1/13/11
to perlwiki...@googlegroups.com
Updates:
Status: Fixed

Comment #4 on issue 127 by mike.lifeguard: When remote end hangs up, don't
wait forever
http://code.google.com/p/perlwikipedia/issues/detail?id=127

This issue was closed by revision r466.

Reply all
Reply to author
Forward
0 new messages