How to fix Rails's warning messages with Ruby 2.7.0

34,222

Solution 1

To suppress warnings like:

warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call

For now, simply prefix/pass the RUBYOPT environment variable to your rails commands:

RUBYOPT='-W:no-deprecated -W:no-experimental' rails server
or
RUBYOPT='-W:no-deprecated -W:no-experimental' rails db:migrate

This may not work with earlier versions of ruby.

For backward compatibility with earlier versions of ruby prefix it with RUBYOPT='-W0' instead.

example:

RUBYOPT='-W0' bundle exec rspec

If you don't want to prefix this each time you run a command, then simply add this to the last line of your .zshrc or .bashrc (whatever you're using):

export RUBYOPT='-W:no-deprecated -W:no-experimental'
or
export RUBYOPT='-W0'

Also see last point of the notes here:
https://rubyreferences.github.io/rubychanges/2.7.html#warning-and-

Solution 2

Update to Rails 6.0.3, they fixed the warnings.

If you still get warnings, it's other libraries (see if there are fixed versions or submit a patch) or your own code (how to fix it).

Solution 3

Obviously it will take some time to for ruby team to remove all this warning in next ruby version. For now the command in your terminal

`RUBYOPT='-W:no-deprecated' rails s` 

on my basic, plain new rails 6.0.2.1 && ruby 2.7.0 project remove these two warnings lines above in a question.

Also, with command

RUBYOPT='-W:no-experimental' rails s

you will hide warnings about experimental features.

You can combine these two in one command like:

RUBYOPT='-W:no-deprecated -W:no-experimental' rails s

However, I tried these commands inside my old project built with rails 5.2 and ruby 2.6.4 later upgraded to rails 6.0.1 and they didn't worked well on for all warnings messages I got from different rails Active* modules and ruby gems.

Probably we will need some time for upgrading code and gems for new latest stuff.

Share:
34,222
Nezir
Author by

Nezir

Full Stack Software developer Ruby On Rails REMOTE Contractor and MCPD for Asp.Net C#, 16+ years of professional experience. Interested in Remote work. Preferred technologies JavaScript, Ruby On Rails, Asp.NET, NodeJs.

Updated on February 16, 2022

Comments

  • Nezir
    Nezir over 2 years

    Did anyone resolve this issue with Ruby 2.7.0?

    I used rbenv and installed Ruby v2.7.0 and then created a Rails project using Rails v6.0.2.1.

    Currently, by running one of

    rails s
    rails s -u puma
    rails s -u webrick
    

    the server is up and the site is served but in the Console log I see two warning messages:

    local:~/rcode/rb27$ rails s
    => Booting Puma
    => Rails 6.0.2.1 application starting in development 
    => Run `rails server --help` for more startup options
    .rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/actionpack-6.0.2.1/lib/action_dispatch/middleware/stack.rb:37: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
    .rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/actionpack-6.0.2.1/lib/action_dispatch/middleware/static.rb:110: warning: The called method `initialize' is defined here
    Puma starting in single mode...
    * Version 4.3.1 (ruby 2.7.0-p0), codename: Mysterious Traveller
    * Min threads: 5, max threads: 5
    * Environment: development
    * Listening on tcp://127.0.0.1:3000
    * Listening on tcp://[::1]:3000 
    

    So, the warning messages are:

    **.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/actionpack-6.0.2.1/lib/action_dispatch/middleware/stack.rb:37: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call**
    
    **.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/actionpack-6.0.2.1/lib/action_dispatch/middleware/static.rb:110: warning: The called method `initialize' is defined here**
    

    I saw this link and there are some suggestion to switch of warnings like "If you want to disable the deprecation warnings, please use a command-line argument -W:no-deprecated or add Warning[:deprecated] = false to your code." but I was thinking on little bit better solution/fix for actionpack v6.0.2.1