Skip to content
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

uninitialized constant ActiveResource (NameError) #1

Open
elikem opened this issue Jul 12, 2015 · 3 comments · May be fixed by #2
Open

uninitialized constant ActiveResource (NameError) #1

elikem opened this issue Jul 12, 2015 · 3 comments · May be fixed by #2

Comments

@elikem
Copy link

elikem commented Jul 12, 2015

I get a the following error when I restart my app after adding this peek plugin.

gems/peek-active_resource-1.0.0/lib/peek/views/active_resource.rb:1:in `<top (required)>': uninitialized constant ActiveResource (NameError)

How would I go about fixing this?
Is there any log data I could provide to help?

@MaRoe
Copy link

MaRoe commented Aug 12, 2015

I have the same issue.

@gungorkocak gungorkocak linked a pull request Dec 8, 2015 that will close this issue
@andreorvalho
Copy link

I have got the same issue here is a stacktrace:

bundle exec rake db:drop --trace
rake aborted!
NameError: uninitialized constant ActiveResource::Connection::Atomic
/opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/peek-active_resource-1.0.0/lib/peek/views/active_resource.rb:5:in class:Connection' /opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/peek-active_resource-1.0.0/lib/peek/views/active_resource.rb:1:in'
/opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/peek-active_resource-1.0.0/lib/peek-active_resource.rb:2:in <top (required)>' /opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/bundler-1.7.9/lib/bundler/runtime.rb:76:inrequire'
/opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/bundler-1.7.9/lib/bundler/runtime.rb:76:in block (2 levels) in require' /opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/bundler-1.7.9/lib/bundler/runtime.rb:72:ineach'
/opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/bundler-1.7.9/lib/bundler/runtime.rb:72:in block in require' /opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/bundler-1.7.9/lib/bundler/runtime.rb:61:ineach'
/opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/bundler-1.7.9/lib/bundler/runtime.rb:61:in require' /opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/bundler-1.7.9/lib/bundler.rb:134:inrequire'
/Users/andreorvalho/projects/foodies_cube/config/application.rb:8:in <top (required)>' /Users/andreorvalho/projects/foodies_cube/Rakefile:4:inrequire'
/Users/andreorvalho/projects/foodies_cube/Rakefile:4:in <top (required)>' /opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/rake-11.1.1/lib/rake/rake_module.rb:28:inload'
/opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/rake-11.1.1/lib/rake/rake_module.rb:28:in load_rakefile' /opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/rake-11.1.1/lib/rake/application.rb:689:inraw_load_rakefile'
/opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/rake-11.1.1/lib/rake/application.rb:94:in block in load_rakefile' /opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/rake-11.1.1/lib/rake/application.rb:176:instandard_exception_handling'
/opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/rake-11.1.1/lib/rake/application.rb:93:in load_rakefile' /opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/rake-11.1.1/lib/rake/application.rb:77:inblock in run'
/opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/rake-11.1.1/lib/rake/application.rb:176:in standard_exception_handling' /opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/rake-11.1.1/lib/rake/application.rb:75:inrun'
/opt/boxen/rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/rake-11.1.1/bin/rake:33:in <top (required)>' /opt/boxen/rbenv/versions/2.1.1/bin/rake:23:inload'
/opt/boxen/rbenv/versions/2.1.1/bin/rake:23:in `

@Daniel-ltw
Copy link

https://github.com/ruby-concurrency/atomic

The Atomic.new call is deprecated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants