How to determine what triggers a Rake denial warning

Question

When I do bundle exec rake -T (or bundle exec rake ), I get a failure warning:

 Andrews-Air:nabu agrimm$ bundle exec rake --trace -T [DEPRECATION] `last_comment` is deprecated. Please use `last_description` instead. [DEPRECATION] `last_comment` is deprecated. Please use `last_description` instead. [DEPRECATION] `last_comment` is deprecated. Please use `last_description` instead. [DEPRECATION] `last_comment` is deprecated. Please use `last_description` instead. [DEPRECATION] `last_comment` is deprecated. Please use `last_description` instead. [DEPRECATION] `last_comment` is deprecated. Please use `last_description` instead. [DEPRECATION] `last_comment` is deprecated. Please use `last_description` instead. [DEPRECATION] `last_comment` is deprecated. Please use `last_description` instead. [DEPRECATION] `last_comment` is deprecated. Please use `last_description` instead. [DEPRECATION] `last_comment` is deprecated. Please use `last_description` instead. rake about # List versions of all Rails frameworks and the environment [snip] 

Although this is not very relevant, here's the gemfile:

 source 'https://rubygems.org' gem 'rails', '~> 3.2.22.2' gem 'mysql2' group :assets do gem 'coffee-rails', '~> 3.2.1' gem 'compass-rails' gem 'therubyracer' gem 'libv8' gem 'uglifier', '>= 1.0.3' end gem 'jquery-rails' gem 'haml-rails' gem 'to-csv', :require => 'to_csv' gem 'kaminari' gem 'oai' gem 'analytical' gem 'country-select' gem 'activeadmin' gem 'sass-rails', '~> 3.2.3' gem 'meta_search', '>= 1.1.0.pre' gem 'devise', '2.2.3' gem 'cancancan', '~> 1.12.0' gem 'squeel' gem 'nilify_blanks' gem 'sunspot_rails' gem 'sunspot_solr' gem 'unicorn' gem 'ruby-filemagic' gem 'capistrano' gem 'capistrano-ext' gem 'capistrano-unicorn' gem 'rollbar', '~> 2.8.3' gem 'newrelic_rpm' gem 'progress_bar' gem 'paper_trail', '~> 2' gem 'quiet_assets' gem 'roo', '~> 2.1.0' gem 'roo-xls', :github => 'roo-rb/roo-xls', :ref => '0a5ef88' gem 'streamio-ffmpeg' gem 'rake' gem 'rmagick' gem 'whenever', :require => false group :development, :test do gem 'turn', '~> 0.8.3', :require => false gem 'rspec-rails', '~> 2.0' gem 'sextant' gem 'thin' gem 'spring' gem 'spring-commands-rspec' gem 'pry' gem 'pry-rails' gem 'letter_opener' gem 'guard-bundler' gem 'guard-rails' gem 'guard-rspec' gem 'guard-sunspot' gem 'rb-inotify', :require => RUBY_PLATFORM.include?('linux') ? 'rb-inotify' : false gem 'rb-fsevent', :require => RUBY_PLATFORM.include?('darwin') ? 'rb-fsevent' : false end group :development do gem 'annotate' gem 'binding_of_caller' gem 'better_errors' gem 'rubocop' end group :test do gem 'capybara' gem 'poltergeist' gem 'factory_girl_rails' gem 'database_cleaner' gem 'email_spec' gem 'launchy' end 

Running git grep -i last_comment means that it is not in my code - presumably it is in a third-party gem.

How do I decide what causes obsolescence warnings?

Answer 1

I find it easier to modify the line from warn to raise in rake-11.1.0/lib/rake/task_manager.rb:10 .

For me, offensive gems are rspec ( fixed in 3.4.4 ) and rubocop ( fixed in 0.38.0 ).

Answer 2

Try updating the gem "rspec-rails", "~> 3.4.4" , which resolved obsolescence warnings for me.

Answer 3

You can recursively grep your gems with:

 grep -r last_comment /path/to/gems 

Answer 4

This is not an rspec error , the error comes from the rake, there was a commit a couple of weeks ago that added a warning, it was here.

It seems that Rspec is already observing when using last_description over last_comment . If possible, try rspec-core to a newer version of rspec-core Gem, as @ chris-scott suggested. I ran to do the trick

bundle update rspec-core

Answer 5

As described in this post, you can do:

 # application.rb ActiveSupport::Deprecation.debug = true 

This will give you a complete evaluation of the stack stack.