Bug #294
Smuxi needs to tolerate temporarly Twitter issues
Status: | Closed | Start: | 01/13/2010 | |
Priority: | Normal | Due date: | ||
Assigned to: | Mirco Bauer | % Done: | 100% |
|
Category: | Engine Twitter | |||
Target version: | 0.7.1 | |||
Complexity: | Medium |
Found in Version: | ||
Votes: | 0 |
Description
Twitter has often temporarly issues and Smuxi is giving up too early (on the first error). Smuxi has tolerate such issues, examples:
03:28:52 -!- An error occurred while fetching the friends timeline from Twitter. Reason: Error getting response stream (ReadDone1): ReceiveFailure 03:35:05 -!- An error occurred while fetching direct messages from Twitter. Reason: Error getting response stream (ReadDone1): ReceiveFailure 09:23:31 -!- An error occurred while fetching the replies from Twitter. Reason: Twitter is currently unavailable.
Associated revisions
Revision f6b2103764d21b2131249efbf0768c60a0834b46
Ignore many temporarly connect and retrieve issues with Twitter (closes: #294)
Revision 9927293a2841341b545ee7e242f1d2d243f6d3af
Really fix temporarly Twitter issues (closes: #294)
History
Updated by Mirco Bauer 5441 days ago
- Category set to Engine Twitter
Updated by Mirco Bauer 5439 days ago
I wonder if Smuxi should catch System.Net.WebException, see:
http://mono.ximian.com/tests/displayDetails.php?&testsuite=System.Web.Services-standalone&file=20050530&status=1&profile=0&distro=1#3
Updated by Mirco Bauer 5433 days ago
- Tracker changed from Feature to Bug
Updated by Mirco Bauer 5430 days ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset f6b2103764d21b2131249efbf0768c60a0834b46.