-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Network reset? #209
Comments
Do you have an event handler set up for the "error" event? If not, you should. You can then swallow the error there: Or see docs: https://github.com/AlCalzone/node-tradfri-client#handle-errors It mostly informative, but the mentioned error is disruptive enough that I want developers to catch it. |
Thanks, hadn't set that one up yet. I will try it out ! |
Thanks, worked fine. Does this also capture the error as mentioned in #108 by any change ? |
I'm not sure actually. Those DNS errors sometimes happen in internal callbacks I have no control over. |
Hi
I have the following situation ( using auto reconnect):
But then, as soon as first reconnect attempt is made i get this:
UnhandledPromiseRejectionWarning: Error: The network stack was reset. Pending promises will not be fulfilled
Which I dont understand.. was stopping the observers not sufficient? And where am I to catch/handle this error, on what promise? I tried on the 'connect' promise but that wasn;t the correct one from the looks of it..
Thanks.
The text was updated successfully, but these errors were encountered: