-
Notifications
You must be signed in to change notification settings - Fork 64
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
nanite does not startup in ruby1.9 #17
Comments
I'll check it out. I thought I had caught most of the Ruby 1.9 issues, but I'll look into your fork. |
mattmatt: i fixed this on mine, it's 1.9 getting confused on where FileUtils is. It thinks it's a Nanite class. Putting in a "require 'fileutils'" inside nanite.rb solved the issue for me. There is probably a better place for the require, but I didn't feel like digging through and finding all recurrences of FileUtils inside Nanite, and confining the require to those. |
i think its global to 1.9? irb doesn't recognize fileutils either until it's required.. at least on our system. we put ours in nanite.rb too |
sent pull request |
btw: this only happens when clustering... |
nanite wont startup in ruby1.9 without some code changes. nanite uses FileUtils which does not seem to be available by default in 1.9. I have sent a pull request with a fix to the issue but never got a response (probably with good reason). in any case, with the change nanite runs flawlessly on 1.9. we have it running on several servers without any issues once that change is made.
The text was updated successfully, but these errors were encountered: