racker/irccat — pull request #3 by bison (2014-01-01 00:30:12+00:00)
Title: Don't give up when connect() throws an exception

Currently, if the initial connect() throws an exception, IRCCat stops
trying and just moves on with no active connection to a server. This
catches the exception within the while loop and keeps trying.

We've had issues several times where the bot gets disconnected, and
tries to reconnect too quickly. An exception is throw for the server thinking
the nick is already in use and the bot just hangs.

This retries forever, but it looks like that's already the case unless an
exception is thrown.