When oulu is unable to successfully post a message to the Flowdock API, it records the error in its logs. However, it does not inform the user that the message was not delivered. This means that when the API is having trouble receiving messages (like last Friday), IRC users have no way of knowing which (if any) of their messages have actually been sent.
This very severely impacts the usability of the IRC gateway, since there is no way to trust that it has actually delivered any messages - and no way to check, apart from using the web interface or a native client (and avoiding these is usually the point of using the IRC gateway in the first place).
The problem is on line 290 and line 297 of irc_connection.rb. This is where $logger.error is called, but what is almost certainly needed is something like
When oulu is unable to successfully post a message to the Flowdock API, it records the error in its logs. However, it does not inform the user that the message was not delivered. This means that when the API is having trouble receiving messages (like last Friday), IRC users have no way of knowing which (if any) of their messages have actually been sent.
This very severely impacts the usability of the IRC gateway, since there is no way to trust that it has actually delivered any messages - and no way to check, apart from using the web interface or a native client (and avoiding these is usually the point of using the IRC gateway in the first place).
The problem is on line 290 and line 297 of
irc_connection.rb. This is where$logger.erroris called, but what is almost certainly needed is something likeor