-
-
Notifications
You must be signed in to change notification settings - Fork 224
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
Updating Celluloid logger reference #47
Conversation
First question, why is the integration test succeeding without this change? Or is Either way, please do rebase/squash the commits. |
I don't see celluloid or celluloid-io pulled in by the .gemspec file (which makes sense as you are trying to dynamically support either one) Therefore you must have an older version installed on your dev box. |
Hm, nope, https://travis-ci.org/dblock/slack-ruby-client/jobs/101613182#L107 has pulled in 0.17.2. Locally you can run What do you see when you run this? |
I see 2 successful tests. What do you see with my merge? I'm running Ruby 2.0.0-p645. |
I am saying that even without your merge I am seeing 2 successful tests. |
You could try integrating slack-ruby-client into a new project with Celluloid and Reel and see what happens when you try and run it. It's definitely the case that the current version of Celluloid uses Celluloid::Internal::Logging |
So what happens when you try to run it? What output do you get? I know this is a trivial change and it seems like it's the right thing, I am just trying to understand what's going on, not being annoying :) I'd like a test that reproduces whatever error you're getting. |
No problem. This reproduces the issue. Just run Isn't |
I figured it out, Celluiloid docs say in https://github.com/celluloid/celluloid: You did Fixed in dblock@33360aa. Can you try with |
Confirmed that I everything builds fine now. Thanks! |
@jlyonsmith I cut 0.5.3, thanks for your help. |
No description provided.