This repository has been archived by the owner on Jun 30, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 130
im.open returned an error #87
Labels
Comments
btw if you proceed despite the error and use the bot, it will still work just fine. Note sure that triggers the error, and it's inconsistent - happens sometimes; gone after restarting the computer. |
also seeing this on a fresh lita install, no changes made yet besides adding redis configs. it didn't happen the first ~2 times I started lita, then after that it comes up on every start |
seedalpha/slackbot@0c790fe references the same error, it probably is easily fixed |
Are you all still seeing this problem? I'm betting it was addressed by the recent fix to stop Lita from receiving other bot messages. |
I don't see it anymore. |
Actually can confirm this problem present on 1.8.0 version |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using master as my gem.
No optional configs set.
Works fine if I just use the gem from rubygems.org. Unfortunately the optional parse options weren't available from there so tried out master.
The text was updated successfully, but these errors were encountered: