Skip to content
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

Open
sam1919 opened this issue Oct 27, 2011 · 7 comments
Open

Catch ping timeouts #48

sam1919 opened this issue Oct 27, 2011 · 7 comments

Comments

@sam1919
Copy link

sam1919 commented Oct 27, 2011

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?)

@gf3
Copy link
Owner

gf3 commented Feb 10, 2012

Is this still an issue on 2.0.0-beta?

@gf3
Copy link
Owner

gf3 commented Feb 24, 2012

Closing, assuming fixed.

@gf3 gf3 closed this as completed Feb 24, 2012
@sam1919
Copy link
Author

sam1919 commented Mar 1, 2012

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.

@sam1919
Copy link
Author

sam1919 commented Mar 1, 2012

Please reopen the bug.

@gf3 gf3 reopened this Mar 2, 2012
@gf3
Copy link
Owner

gf3 commented Mar 2, 2012

Which server are you connecting to?

@sam1919
Copy link
Author

sam1919 commented Mar 2, 2012

My IRC server ist irc.mibbit.net.

@sam1919
Copy link
Author

sam1919 commented Mar 2, 2012

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants