There was a problem in the automatic reconnect loop: If the connection to the IRC server is dropped it will not be reestablished because the call to client.Server() blocks forever. This is fixed by not calling it at this point. But there are other issues we have to tackle.
The first one is our locking. We still have a big issue here if the following happens:
if the connection goes down, client.Connect() returns an error
we acquire the lock: clientLock.Lock()
we sleep some time
we call client.Connect() again and it fails again because our Internet is still broken
As our handler (CONNECTED) was not called, the lock is still in use
If we want to rewrite the lock logic, we have to think about two scenarios:
1) How do we handle the time between irc-connection-is-down and the-library-knows-that-the-connection-is-down?
The library sends continuously a PING (every 20 seconds is the smallest time interval we can use). If now() - time_last(PONG) is > 60 seconds, the connection goes in state disconnected. Then Connect() returns and we reconnect.
2) What happens if the connection to the IRC server is down, but our http server works and is used? We can
send a 500 because the IRC connection is down (if we know it; good for alertmanager, probably bad for other things that don't automatically resend)
handle the received data in a go routine and always return a 200 (never blocks, but we have to buffer the messages until IRC is up again)
we keep the logic as it is and increase the channel size. Right now, http connections are held open if we cannot write into the channel (because the IRC sender does not work and stops reading from the channel)
There was a problem in the automatic reconnect loop: If the connection to the IRC server is dropped it will not be reestablished because the call to
client.Server()blocks forever. This is fixed by not calling it at this point. But there are other issues we have to tackle.The first one is our locking. We still have a big issue here if the following happens:
client.Connect()returns an errorclientLock.Lock()client.Connect()again and it fails again because our Internet is still brokenhttps://github.com/fleaz/CptHook/blob/4d1839ae1aa619f6648c7aa03d412722d378def5/irc.go#L121-L129
If we want to rewrite the lock logic, we have to think about two scenarios:
1) How do we handle the time between irc-connection-is-down and the-library-knows-that-the-connection-is-down? The library sends continuously a PING (every 20 seconds is the smallest time interval we can use). If now() - time_last(PONG) is > 60 seconds, the connection goes in state disconnected. Then
Connect()returns and we reconnect.2) What happens if the connection to the IRC server is down, but our http server works and is used? We can