You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actual behaviour:
If you connect to a channel you can handle connection error with the promise handling .catch()
But if you set reconnect = true then this will only work for first try of connection.
For reconnects there is no error handling. So it results in "(node:20312) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 18): Unable to connect."
The reson is simply, that tmi.js has no error handling here (it calls simply this.connect() with out catching the error from returned promise)
Expected behaviour:
There should be any kind of error handling. Maybe via eventhandler "error" or maybe a new "reconnect error"
Actual behaviour:
If you connect to a channel you can handle connection error with the promise handling .catch()
But if you set reconnect = true then this will only work for first try of connection.
For reconnects there is no error handling. So it results in "(node:20312) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 18): Unable to connect."
The reson is simply, that tmi.js has no error handling here (it calls simply this.connect() with out catching the error from returned promise)
Expected behaviour:
There should be any kind of error handling. Maybe via eventhandler "error" or maybe a new "reconnect error"
Error log:
"(node:20312) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 18): Unable to connect."
Server configuration
The text was updated successfully, but these errors were encountered: