-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catch ping timeouts #48
Comments
Is this still an issue on |
Closing, assuming fixed. |
Yes, it's still an issue. I'm using 2.0.0-beta. My bot already catches * but doesn't get info if the connection has timed out. Is there some timeout at all? How big is it? How do you find out that a connection has been lost? My workaround is catching * and let the bot remember the last time some event happened. So I could start a reconnect if the delay was too big. But I'd really like to see irc-js handle this. |
Please reopen the bug. |
Which server are you connecting to? |
My IRC server ist irc.mibbit.net. |
Just to explain this in more detail: I run the bot from my home PC. My internet provider disconnects every night at about 3 to 5 am (Unfortunately I cannot change this). So the bot disconnects every day at night. But it isn't able (using irc-js) to detect that it has been disconnected. |
When the connection is lost somehow, I get no event about this (I already catch *).
The irc-client shows that my bot is gone with a "ping timeout" message.
The bot itself doesn't recognize this.
(Additional question: Is there a workaround?)
The text was updated successfully, but these errors were encountered: