-
Notifications
You must be signed in to change notification settings - Fork 31
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
Set dependencies with ~> to prevent major verion breakage #27
base: master
Are you sure you want to change the base?
Conversation
Now the builds are broken due to a memory issue. |
The situation is quite confusing but basically I removed a previous memory leak fix. Maybe there really is a memory leak but the fix caused segfaults for me in certain cases. I only use this library in rake tasks so short-term memory leaks aren't a big issue for me. |
👍 |
Er, what I meant by that was - +1 to this change. The memory corruption thing is a separate issue. I really need to figure out what to do with this gem :\ In short, it probably needs to be rewritten or abandoned (I mean, it is now) |
I remembered that |
Thanks for taking the time to look into this, it is appreciated. |
Recent PRs #25 and #26 failed because rspec 3.0 matches ">= 2.0.0". This PR pins rspec, rake, rake-compiler as needed.