Closed amuta closed 3 years ago
So send a PR to fix it? I'm ok with Ruby 2.2+.
@mperham I guess it would be a good idea then to specify the required ruby version for this gem? There is
a required_ruby_version
configuration option for the Gemspec, that will give people trying to install it with a lower Ruby version an error when they try to install it. If you agree with me let me know and I'll open a PR.
Great idea.
On Tue, Oct 20, 2020 at 06:22 mayrsascha notifications@github.com wrote:
@mperham https://github.com/mperham I guess it would be a good idea then to specify the required ruby version for this gem? There is a required_ruby_version configuration option for the Gemspec https://guides.rubygems.org/specification-reference/#required_ruby_version, that will give people trying to install it with a lower Ruby version an error when they try to install it. If you agree with me let me know and I'll open a PR.
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/mperham/connection_pool/issues/133#issuecomment-712845727, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAAWX3NORZ2V4HF2M4RQATSLWFJRANCNFSM4PVOEJSQ .
Within the
v.2.2.3
release, the removal of the lineif Thread.respond_to?(:handle_interrupt)
fromlib/connection_pool.rb
will cause theNoMethodError
for ruby versions before2.0.0
.The commit that caused this behavior 5f72d5372f88b5ac696904009b01afe70feede64 at line 57
It breaks because the
handle_interrupt
was added (renamed from another method actually) to theThread
class only in the2.0.0
release, see it hereI think the main problem is that the
gemspec
does not say anything about not supporting projects with older ruby versions which would prevent the gem to update from such projects.