-
Notifications
You must be signed in to change notification settings - Fork 38
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
When internet is down, library will eventually fail to connect without notifying client #318
Comments
Workaround, we can increase Modify chat = await Chat(twitch)
reconnect_steps = [i*i for i in range(50)] # 11 hours
print(f"Hours to reconnect: {sum(reconnect_steps) // 3600}") # replace to logger
chat.reconnect_delay_steps = reconnect_steps I not verified this, but it can work.
So |
correct, thats what that var is for |
Have this same issue with
Got around it by modifying |
thinking more about this: it does not really make sense to stop retrying if the error is a connection problem. I will probably change it to retry indefinitely with the period of the longest entry in that list |
I have a chat bot based on pytwitchapi. My internet was down for a few hours recently, and it was only when I happened to notice the bot wasn't working when I realised that it had failed to connect to the Twitch API (understandably) and gave up attempting to reconnect:
There apparently isn't a way that this exception could be caught so that the client can tell the library to initiate a re-connect.
Posting here at Lena's request (from Discord)
The text was updated successfully, but these errors were encountered: