-
Notifications
You must be signed in to change notification settings - Fork 127
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
Failing to connect with matrix-org/node-irc
>= 1.0.0
#181
Comments
No issue with I updated after updating
|
@sam-mark Great, thanks! Care to open a pull request for your fix then, so it works for all |
done already #183 😄 |
Cool. However, I don't see anything changed about the config. The sort order of the respective lines has been changed, and default values have been added. But how does it solve the issue when you already set the correct environment variables? |
it fixed two issue.
they can be set as
source matrix-org/node-irc to get defaults
so all those fields i set are optional but required because they didn't get default values |
Thanks. I tried those changes, and normal connections work now. However, SASL connections still time out for me. (I verified that the same credentials work fine in a desktop client, with the same chat network and from the same IP.) |
Working fine for me. I tested same account on both I tested it will |
Not too long after the last release of
hubot-irc
, which unpinnednode-irc
from a specific version, Matrix have released a 1.0.0 version and later a few other minor versions of theirnode-irc
fork.I just tried to upgrade our hubot to the latest
hubot-irc
release, and then encountered the following exception during the connect. I hunted it down, and was able to reproduce it working with the lastnode-irc
version tag just before their 1.0.0 release. As soon as I use 1.0.0 or higher, the exception appears and prevents the bot from connecting.My guess is that they changed the API slightly for the 1.0 release, but I haven't looked into that yet.
The text was updated successfully, but these errors were encountered: