From 733f607bfaa34aa949df2602aec3b46aa2c3a46f Mon Sep 17 00:00:00 2001 From: Wilmer van der Gaast Date: Mon, 17 Oct 2011 23:58:14 -0400 Subject: Stupid work-around for bug #838. The troublesome condition is known, I just don't know exactly how BitlBee gets into it. Any more info from people who see this problem often would be useful. --- protocols/twitter/twitter_lib.c | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'protocols/twitter/twitter_lib.c') diff --git a/protocols/twitter/twitter_lib.c b/protocols/twitter/twitter_lib.c index 4c680930..dd9c3ac6 100644 --- a/protocols/twitter/twitter_lib.c +++ b/protocols/twitter/twitter_lib.c @@ -726,6 +726,13 @@ void twitter_get_timeline(struct im_connection *ic, gint64 next_cursor) struct twitter_data *td = ic->proto_data; gboolean include_mentions = set_getbool(&ic->acc->set, "fetch_mentions"); + if ((td->flags & 0xf0000) == (TWITTER_DOING_TIMELINE | TWITTER_DOING_TIMELINE_SLOW)) { + imcb_log(ic, "Connection seems to have stalled again.\n" + "This is a known bug, if you see this happen a lot " + "please generate some traffic dumps."); + td->flags &= ~0xf0000; + } + if (td->flags & TWITTER_DOING_TIMELINE) { return; } -- cgit v1.2.3