Skip to content
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

Allow newer nokogiris #425

Merged
merged 1 commit into from
May 16, 2016

Conversation

johnsyweb
Copy link
Contributor

Context

I'd like to use a later version of Nokogiri to test a fix for sparklemotion/nokogiri#1426

Change

Relax nokogiri version

@johnsyweb
Copy link
Contributor Author

Do I need to do anything else to get this merged, @ChrisBAshton?

@ChrisBAshton
Copy link
Contributor

Hi @johnsyweb - sorry for the slow reply on this.

Are you sure this is what you're intending? Merging this PR will install newer versions of Nokogiri up-to-and-NOT-including 1.7.0 (according to http://guides.rubygems.org/patterns/ - "Had we said ~> 2.2.0, that would have been equivalent to ['>= 2.2.0', '< 2.3.0'].")

EDIT: Looking more closely at the linked issue, you're looking at Nokogiri version gem 'nokogiri', '1.6.7.2' so this PR should be sufficient.

Happy to merge 👍

@ChrisBAshton ChrisBAshton merged commit e72b7a3 into bbc:master May 16, 2016
@johnsyweb
Copy link
Contributor Author

Thank you.

We bumped Nokogiri to 1.6.8.rc3 and the number of segmentation faults in our Rails application dropped by about 50%!

@johnsyweb
Copy link
Contributor Author

And now they're all gone: sparklemotion/nokogiri#1426 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants