-
Notifications
You must be signed in to change notification settings - Fork 226
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
Better: Add ruby 3.1 compatibility. #279
Better: Add ruby 3.1 compatibility. #279
Conversation
#276 also has a fix for ruby 3.1 |
Indeed, however ruby2_keyword is a temporary method devs can use until they get the code compatible and I read it will be deprecated and removed in future ruby version https://github.com/ruby/ruby/blob/master/vm_method.c#L2145 |
pvoutput uses this gem, also has this ruby 3.1 problem, see johnf/pvoutput#22 |
@ylecuyer I like having a fix that we won't have to worry about down the road, but I think this change has an infinite loop on ruby-head. |
Workaround for faker-ruby#2260. This PR suspends ruby-head CI until travisjeffery/timecop#279 is resolved. GitHub Actions doesn't seem to have a mechanism like Travis CI's allow-failure yet. https://github.com/actions/toolkit/issues/399
Workaround for faker-ruby#2260. This PR suspends ruby-head CI until travisjeffery/timecop#279 is resolved. GitHub Actions doesn't seem to have a mechanism like Travis CI's `allow_failures` yet. https://github.com/actions/toolkit/issues/399
Fixes faker-ruby#2260. This PR suspends ruby-head CI until travisjeffery/timecop#279 is resolved. GitHub Actions doesn't seem to have a mechanism like Travis CI's `allow_failures` yet. https://github.com/actions/toolkit/issues/399
Looks like the build is failing for 1.9.3 I merged another PR for ruby 3.1 support that is going into our 0.9.4 release. I still like the idea of this one since it doesn't use a method that will be removed in ruby 3.2 (maybe), but wanted to get things working for people. Feel free to get this approach working. We can revisit it. |
Fixes faker-ruby#2260. This PR suspends ruby-head CI until travisjeffery/timecop#279 is resolved. GitHub Actions doesn't seem to have a mechanism like Travis CI's `allow_failures` yet. https://github.com/actions/toolkit/issues/399
While this was workaround in #288, I think this is superior fix. |
I tried merging this but the build fails for ruby 3.1 I have reverted it. |
In https://github.com/ylecuyer/puma-status I had a red build because timecop isn't yet compatible with ruby 3.1
This is because of this new change in ruby 3.1: https://bugs.ruby-lang.org/issues/17485
This PR adds the support for it