Upgrade to Ruby 2.5.1 Support, avoid seg faults from old activesupport package.#67
Upgrade to Ruby 2.5.1 Support, avoid seg faults from old activesupport package.#67zerkz wants to merge 1 commit into
Conversation
Reference Ruby 2.5.1, update Gemfile/go past v5 for minitest.
|
@macobo @nelhage @nelhage-stripe Are any of yall active maintainers or know someone you could point me to, to take a look at this PR? Thanks! |
|
FYI this is probably better than not having it, but even with this I can't get it to run due to probably a too-old version of activesupport. I am getting stuff like Looks like https://stackoverflow.com/questions/41504106/ruby-2-4-and-rails-4-stack-level-too-deep-systemstackerror etc Gonna try to figure out how to stick to heroku-16! |
|
Hmm, looks like Ruby prior to 2.4 isn't supported by Heroku (https://devcenter.heroku.com/articles/ruby-support#ruby-versions) so sticking with old stuff isn't going to work. Somebody who understands Ruby/Rails more than me is going to have to upgrade activesupport/rails appropriately... |
|
@glasser I have pagerbot running on |
|
It didn't work for me (with a brand new app from scratch). I get infinite recursion stack traces like above. Are you able to do a from-scratch deploy to heroku? |
I had issues deploying this on a heroku-18 stack with the version of ruby defined. Segfaults were occurring from a 4.0.3
activesupportdependency, supplied by the ruby package system when using the defined ruby versions (2.2? 2.3?).This pull request upgrades everything to 2.5.1 ruby, including all of its dependencies.
Tests pass after rebuilding the dockerimage (updated to extend from RUBY:2.5)
Let me know if there's a better way of defining these version restrictions. It's possible it might work with 2.4 well, but I haven't had the time to try. The ruby buildpack does not support Ruby 2.3 running on the latest stack (heroku-18).