Skip to content
This repository has been archived by the owner on Jun 30, 2022. It is now read-only.

im.open returned an error #87

Open
Jinkxed opened this issue Mar 28, 2016 · 6 comments
Open

im.open returned an error #87

Jinkxed opened this issue Mar 28, 2016 · 6 comments
Labels

Comments

@Jinkxed
Copy link

Jinkxed commented Mar 28, 2016

Using master as my gem.
No optional configs set.

[2016-03-28 20:45:56 UTC] ERROR: Lita::Handlers::Ai crashed. The exception was:
Slack API call to im.open returned an error: cannot_dm_bot.
Full backtrace:
/usr/local/rvm/gems/ruby-2.2.3/bundler/gems/lita-slack-38a968fd88e4/lib/lita/adapters/slack/api.rb:99:in `call_api'
/usr/local/rvm/gems/ruby-2.2.3/bundler/gems/lita-slack-38a968fd88e4/lib/lita/adapters/slack/api.rb:24:in `im_open'
/usr/local/rvm/gems/ruby-2.2.3/bundler/gems/lita-slack-38a968fd88e4/lib/lita/adapters/slack/im_mapping.rb:23:in `block in im_for'
/usr/local/rvm/gems/ruby-2.2.3/bundler/gems/lita-slack-38a968fd88e4/lib/lita/adapters/slack/im_mapping.rb:22:in `fetch'
/usr/local/rvm/gems/ruby-2.2.3/bundler/gems/lita-slack-38a968fd88e4/lib/lita/adapters/slack/im_mapping.rb:22:in `im_for'
/usr/local/rvm/gems/ruby-2.2.3/bundler/gems/lita-slack-38a968fd88e4/lib/lita/adapters/slack/rtm_connection.rb:36:in `im_for'
/usr/local/rvm/gems/ruby-2.2.3/bundler/gems/lita-slack-38a968fd88e4/lib/lita/adapters/slack.rb:65:in `channel_for'
/usr/local/rvm/gems/ruby-2.2.3/bundler/gems/lita-slack-38a968fd88e4/lib/lita/adapters/slack.rb:43:in `send_messages'
/usr/local/rvm/gems/ruby-2.2.3/gems/lita-4.7.0/lib/lita/robot.rb:129:in `send_messages'
/usr/local/rvm/gems/ruby-2.2.3/gems/lita-ai-0.1.1/lib/lita/handlers/ai.rb:13:in `chat'
/usr/local/rvm/gems/ruby-2.2.3/gems/lita-4.7.0/lib/lita/callback.rb:31:in `public_send'
/usr/local/rvm/gems/ruby-2.2.3/gems/lita-4.7.0/lib/lita/callback.rb:31:in `call'
/usr/local/rvm/gems/ruby-2.2.3/gems/lita-4.7.0/lib/lita/handler/event_router.rb:61:in `block in trigger'
/usr/local/rvm/gems/ruby-2.2.3/gems/lita-4.7.0/lib/lita/handler/event_router.rb:59:in `map'
/usr/local/rvm/gems/ruby-2.2.3/gems/lita-4.7.0/lib/lita/handler/event_router.rb:59:in `trigger'
/usr/local/rvm/gems/ruby-2.2.3/gems/lita-4.7.0/lib/lita/robot.rb:183:in `block in trigger'
/usr/local/rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/set.rb:283:in `each_key'
/usr/local/rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/set.rb:283:in `each'
/usr/local/rvm/gems/ruby-2.2.3/gems/lita-4.7.0/lib/lita/robot.rb:180:in `trigger'
/usr/local/rvm/gems/ruby-2.2.3/gems/lita-4.7.0/lib/lita/robot.rb:72:in `receive'
/usr/local/rvm/gems/ruby-2.2.3/bundler/gems/lita-slack-38a968fd88e4/lib/lita/adapters/slack/message_handler.rb:122:in `dispatch_message'
/usr/local/rvm/gems/ruby-2.2.3/bundler/gems/lita-slack-38a968fd88e4/lib/lita/adapters/slack/message_handler.rb:162:in `handle_message'
/usr/local/rvm/gems/ruby-2.2.3/bundler/gems/lita-slack-38a968fd88e4/lib/lita/adapters/slack/message_handler.rb:18:in `handle'
/usr/local/rvm/gems/ruby-2.2.3/bundler/gems/lita-slack-38a968fd88e4/lib/lita/adapters/slack/rtm_connection.rb:100:in `block in receive_message'
/usr/local/rvm/gems/ruby-2.2.3/bundler/gems/lita-slack-38a968fd88e4/lib/lita/adapters/slack/event_loop.rb:10:in `block in defer'
/usr/local/rvm/gems/ruby-2.2.3/gems/eventmachine-1.2.0.1/lib/eventmachine.rb:1076:in `call'
/usr/local/rvm/gems/ruby-2.2.3/gems/eventmachine-1.2.0.1/lib/eventmachine.rb:1076:in `block in spawn_threadpool'

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.

@eligiblekeng
Copy link

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.

@ekilah
Copy link

ekilah commented Jul 27, 2016

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

@ekilah
Copy link

ekilah commented Jul 27, 2016

seedalpha/slackbot@0c790fe references the same error, it probably is easily fixed

@jimmycuadra
Copy link
Contributor

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.

@eligiblekeng
Copy link

I don't see it anymore.

@liashukvladyslav
Copy link

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.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants