Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

ActiveSupport::Memoizable deprecation warning in Rails 3.2 #4678

Closed
kirs opened this Issue Jan 25, 2012 · 6 comments

Comments

Projects
None yet
5 participants
Contributor

kirs commented Jan 25, 2012

I just upgraded to 3.2 from 3.1, and found this line in log:

DEPRECATION WARNING: ActiveSupport::Memoizable is deprecated and will be removed in future releases,simply use Ruby memoization pattern instead. (called from <top (required)> at /Users/kirs/Sites/myapp/config/environment.rb:5)

The config/environment.rb contains only this:

# Load the rails application
require File.expand_path('../application', __FILE__)

# Initialize the rails application
Myapp::Application.initialize!

Is it something wrong with Myapp::Application.initialize!?

Member

sikachu commented Jan 25, 2012

Nah, that probably mean there's something in your config/initializers, gem, or plugin that use Memoizable.

Contributor

kirs commented Jan 25, 2012

Thanks, it there any way to detect that gem?

@kirs kirs closed this Jan 25, 2012

Owner

rafaelfranca commented Jan 25, 2012

@kirs are you using carrierwake? I got the same warning and it was caused by carrierwave 0.5.8

Contributor

kirs commented Jan 25, 2012

@rafaelfranca You are right. It seems to be that in 0.5.8 Carrierwave used Memoizable: in mount.rb and in carrierwave.rb. Current solution is to use it from git repo:

gem 'carrierwave', git: "git://github.com/jnicklas/carrierwave.git"
Contributor

mariovisic commented Mar 12, 2012

Hi all

Using the git repo in a Gemfile works fine but i'm currently working on an engine so I have to define the dependency in the gemspec so can only use the last stable.

Any chance of a 0.5.9 release anytime soon?

Contributor

bonsaiben commented Jun 15, 2012

marlovisic you should try raising the issue on the Carrierwave repo, better chance of getting a response there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment