-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Sidekiq affecting Celluloid in other gems? #1858
Comments
Yeah, that's due to Sidekiq nil'ing out the logger. PRs welcome. I'm not sure why I'm not just setting the level to WARN. BTW Sidekiq 3 does not support Ruby 1.9. |
This is a listen bug. It should check the logger is defined before attempting to change the loglevel. |
Thanks for the quick response! I downgraded my sidekiq to the highest 2.x version since I'm on ruby 1.9 & I added this to sidekiq initializer... But I'm still getting the same error when I run 'bundle exec sidekiq'. This seems to be reproducible in dev as well. What is the easiest way to bypass this error? |
The first arg is not a String.
|
Hmm I'm stumped I tried and still the same error. I also tried forking the listen gem and modifying the listener.rb file but I have no knowledge of that gem and wasn't able to resolve it. |
Try this in listen: Celluloid.logger.level = _debug_level if Celluloid.logger.respond_to?(:level=) |
Celluloid.logger.try(:level=, _debug_level) if you are using rails |
I had to remove all the log calls in the listen gem and now the error is not displaying, this is probably not the best thing to do, but I can live without the logs for the listen gem. Thank you all for your comments and for the work on the sidekiq gem. |
Hi,
I have a working Rails 3 app that is using sidekiq & the listen gem - https://github.com/guard/listen
It boots up fine, but when I try to start sidekiq in a non-dev environment I get the following error....
If I look at the listener.rb:37 line - https://github.com/guard/listen/blob/master/lib/listen/listener.rb - it has this code...
Celluloid.logger.level = _debug_level
And based on the above stack trace, it seems like it can't find Celluloid. What is strange is if I boot up sidekiq in development mode it's fine. Only qa or great has an issue on my ubuntu 12 box. I'm wondering since sidekiq defaults the logger to nil, does this affect the above code? Is there a work around? Thanks in advance.
The text was updated successfully, but these errors were encountered: