-
Notifications
You must be signed in to change notification settings - Fork 613
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
undefined method =~
in Ruby 3.2
#431
Comments
@tilo With the current Ruby 3.2.0dev ruby/ruby@56cc3e9, it looks like no error according to the latest build. https://github.com/ruby/rake/runs/6872931931?check_suite_focus=true
Can you try the latest Ruby 3.2 head to reproduce? |
I was running into the same error and tried to reproduce it. In the end I just saw the error with rake 11, but was unable to repro with the current rake. I assume you'll be able to fix the problem by bumping rake to the most current version which appears to support ruby 3.2 just fine. |
Reference: GitHub / ruby / rake / undefined method =~ in Ruby 3.2 mizzy#431 [1] Error output: rake aborted! undefined method `=~' for #<Proc:0x00007f488b282050 /opt/hostedtoolcache/Ruby/3.2.2/x64/lib/ruby/gems/3.2.0/gems/rake-10.1.1/lib/rake/application.rb:357 (lambda)> (See full trace by running task with --trace) Error: Process completed with exit code 1. [1] ruby/rake#431
Reference: GitHub / ruby / rake / undefined method =~ in Ruby 3.2 mizzy#431 [1] Error output: rake aborted! undefined method `=~' for #<Proc:0x00007f488b282050 /opt/hostedtoolcache/Ruby/3.2.2/x64/lib/ruby/gems/3.2.0/gems/rake-10.1.1/lib/rake/application.rb:357 (lambda)> (See full trace by running task with --trace) Error: Process completed with exit code 1. [1] ruby/rake#431
This was fixed by #297. |
This line:
rake/lib/rake/application.rb
Line 395 in 86d7ad9
is causing this error when running against Ruby 3.2 or head
The text was updated successfully, but these errors were encountered: