Closed craig1410 closed 8 years ago
@craig1410 Would you please explain how to debug this in order to find which gem is causing the warnings?
@acrolink It was a few months ago when I did this but I think I just used my RubyMine IDE debugger tools to step into the code and framework and eventually by interrogating the variables during loading of gems I found the gem responsible. Sorry I can't be more specific and I'm sure there are better ways to do this but I'm pretty sure this is what I did.
Hope this helps, Craig.
Thanks @craig1410 I will give that a try.
Any plans for a release with this change? Since Rails 5 is out and all :)
@aried3r Yes, hopefully in another week or so.
Anyone coming here, I found adding a little debug to the rails file ...gems/railties-5.0.0/lib/rails/initializable.rb
was enough to point me in the right direction....
def run_initializers(group=:default, *args)
return if instance_variable_defined?(:@ran)
initializers.tsort_each do |initializer|
puts "Initializer: #{initializer.name}" <<<<<<<<<<<<<< HERE
initializer.run(*args) if initializer.belongs_to?(group)
end
@ran = true
end
@ktec Thanks, I will try the method you had suggested later and report back.
@WilHall @aried3r any updates on resolving this issue?
I'm also curious about how to resolve this.
This has been fixed in 3.0.9 I believe, see https://github.com/lassebunk/gretel/blob/v3.0.9/lib/gretel/deprecated/show_root_alone.rb
When booting up my rails app either via rake test or rails server, I get 3 deprecation warnings as follows:
The line failing is:
Upon debugging I found these warnings were issued during the loading of the gretel gem and on reviewing the code I found 3 places where alias_method_chain is called. I have created a pull request which seems to work in Ruby 1.9.3 through 2.2.3. I'll post the PR in a moment and would appreciate any feedback.