-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Couldn't cleanly terminate all actors in 10 seconds w/ celluloid-io #199
Comments
Do you see this right away? It looks like something is blocking the execution and eventually it runs out of worker threads. |
Seeing this also on a first install using the examples in README.md. Relevant gems & versions:
|
This is just from running any sample? What's the easiest way to reproduce? |
Thanks for the quick response! Yep, any sample. My steps are: Added the following to a Gemfile:
Added the following to test.rb:
Executed via:
Full stack trace:
|
Also tested on a Centos 7 server with the same results, so it's not OSX specific. |
I can reproduce. This is specific to celluloid and is caused by the replacement of the Actor by a Thread in slack-ruby/slack-ruby-client#224. I am confused though to why this is happening, as the synchronous slack-ruby-client examples without the bot wrappers work fine. That was done entirely to make specs happy, so I am going to try and undo this in slack-ruby/slack-ruby-client#228 and work around that problem. |
Anyone care to try my branch? gem 'slack-ruby-client', github: 'dblock/slack-ruby-client', branch: 'undo-224' |
Thanks @dblock, that looks to work perfectly now. |
I released 0.13.2. I don't think we need to update the minimal version of slack-ruby-bot since it just affects celluloid. Everyone on this thread should |
Thank you both for the help! We updated to the latest and its working for us. |
Hello,
I've had a bot before but after updating the gem I've been seeing this error. I couldn't find any documentation/issue mentioning this. Any idea how to fix?
The text was updated successfully, but these errors were encountered: