-
-
Notifications
You must be signed in to change notification settings - Fork 217
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
undefined method `Async' for #<Slack::RealTime::Concurrency::Async::Socket> (NoMethodError) #272
Comments
Adding
|
We always properly refer to |
@dblock Socrates, while intended to be a library, also includes a mini chatbot example which is easy to fire up for demo purposes. So, here are 2 ways to quickly reproduce the error...
The second version might result in newer versions of gem dependencies, but I'm not 100% certain. I think it might depend on what is already installed. Thanks for looking! Please don't hesitate to ask if I can help debug on my end. |
I tried changing the reference to |
Using Adding
I didn't jump any further down the rabbit hole. |
This is because async-websocket 0.9 has a backwards incompatible set of changes from 0.8. For now the best solution is to lock down to 0.8.0. I opened #282 to upgrade. |
Not sure if this is still active (and not just open), but for what its worth - I used to have this problem also (with my slacktail gem), but now testing it with 0.15.1, it seems to be working fine. |
We locked it in #283. Closing. |
The project https://github.com/carbonfive/socrates uses slack-ruby-client.
When using version
slack-ruby-client (0.14.2)
, I get this error when starting the bot:Looking at
slack-ruby-client/lib/slack/real_time/concurrency/async.rb
Line 28 in e6a3276
Async
will resolve to the moduleAsync
on line 8 of the same file, instead of the intended version (https://github.com/socketry/async/blob/master/lib/async.rb#L33). The error I'm seeing (above) suggests that's what's happening.Reverting to
0.14.1
resolves the problem.The text was updated successfully, but these errors were encountered: