Campy goes AWOL after long periods of inactivity

[bbelchak]

Campy will stay in the room indefinitely now, but he will stop answering after any extended period of inactivity. I think this is caused by the streamer losing connection but not realizing it, so it doesn't reconnect.

[askedrelic]

+1

I've been running/tweaking a fork of the non-threaded campy from last week. I fixed a reactor/streaming bug where it would start listening on the first room and not all rooms here: askedrelic@040f214

Today, I've been testing the latest threaded version, which definitely seems more stable, but I'm running into the AWOL bug also.

[askedrelic]

The only failure pattern I've noticed is that Campy receives a "KickMessage". Campy remains running in perma-while loop, the threads stop running and handling messages, and Campy does not issue a 'leave' command for the Campfire chat room; the bot still shows as running in the chatroom.

Failure messages:

Thread-4: Handling {u'body': None, u'user_id': None, u'created_at': u'2011/10/04 01:20:00 +0000', u'room_id': xxxxxx, u'type': u'TimestampMessage', u'id': xxxxxxxxx}
Thread-4: Handling {u'body': None, u'user_id': XXXXXXX, u'created_at': u'2011/10/04 01:20:18 +0000', u'room_id': xxxxxx, u'type': u'KickMessage', u'id': xxxxxxxxx}

[bbelchak]

I have also noticed this issue. I think I have a fix for it, but requires more testing.

[bbelchak]

I have added some debugging statements into my local copy and I'm seeing it lose connection even without the KickMessage ... Needs more investigation.