msjit / testcasedb

TestCaseDB - Web based test case management
MIT License
40 stars 18 forks source link

undefined method value' for nil:NilClass /home/kiran/testcasedb/config/initializers/omniauth.rb #19

Closed kirantpatil closed 10 years ago

kirantpatil commented 10 years ago

With the migrated database, I cloned again the project and try to do db:migrate on the old database and am getting below error

db:migrate error


kiran@jaihanuman:~/testcasedb$ bundle exec rake db:migrate RAILS_ENV='production' rake aborted! undefined method value' for nil:NilClass /home/kiran/testcasedb/config/initializers/omniauth.rb:3:inblock in <top (required)>' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/builder.rb:51:in instance_eval' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/builder.rb:51:ininitialize' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/omniauth-1.1.3/lib/omniauth/builder.rb:7:in initialize' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.14/lib/action_dispatch/middleware/stack.rb:43:innew' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.14/lib/action_dispatch/middleware/stack.rb:43:in build' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.14/lib/action_dispatch/middleware/stack.rb:113:inblock in build' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.14/lib/action_dispatch/middleware/stack.rb:113:in each' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.14/lib/action_dispatch/middleware/stack.rb:113:ininject' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.14/lib/action_dispatch/middleware/stack.rb:113:in build' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/railties-3.2.14/lib/rails/engine.rb:475:inapp' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/railties-3.2.14/lib/rails/application/finisher.rb:31:in block in <module:Finisher>' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/railties-3.2.14/lib/rails/initializable.rb:30:ininstance_exec' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/railties-3.2.14/lib/rails/initializable.rb:30:in run' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/railties-3.2.14/lib/rails/initializable.rb:55:inblock in run_initializers' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/railties-3.2.14/lib/rails/initializable.rb:54:in each' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/railties-3.2.14/lib/rails/initializable.rb:54:inrun_initializers' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/railties-3.2.14/lib/rails/application.rb:136:in initialize!' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/railties-3.2.14/lib/rails/railtie/configurable.rb:30:inmethod_missing' /home/kiran/testcasedb/config/environment.rb:5:in <top (required)>' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.14/lib/active_support/dependencies.rb:251:inrequire' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.14/lib/active_support/dependencies.rb:251:in block in require' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.14/lib/active_support/dependencies.rb:236:inload_dependency' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.14/lib/active_support/dependencies.rb:251:in require' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/railties-3.2.14/lib/rails/application.rb:103:inrequire_environment!' /home/kiran/testcasedb/vendor/bundle/ruby/1.9.1/gems/railties-3.2.14/lib/rails/application.rb:305:in `block (2 levels) in initialize_tasks' Tasks: TOP => db:migrate => environment (See full trace by running task with --trace)

kirantpatil commented 10 years ago

I have edited db file and provided the values for client id and secret and still getting the same error.

joffems commented 10 years ago

I have pushed a commit for the install. It was broken in a few places by the new Google Auth code.

Please pull the latest commit and retry.

kirantpatil commented 10 years ago

Thanks, will test the fix and report if there are any issue by tomorrow.

kirantpatil commented 10 years ago

The fix has resolved the issue.