You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!, I have a recently problem with the gem (I don't know what change broke this). When try to run any task related with version gem seem to try connect to the database (bizarre!)
This is the result when execute rake version --trace
** Invoke version (first_time)
** Invoke VERSION (first_time, not_needed)
** Execute version
rake aborted!
ActiveRecord::ConnectionNotEstablished
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/activerecord-3.0.17/lib/active_record/connection_adapters/abstract/connection_pool.rb:317:in `retrieve_connection'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/activerecord-3.0.17/lib/active_record/connection_adapters/abstract/connection_specification.rb:97:in `retrieve_connection'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/activerecord-3.0.17/lib/active_record/connection_adapters/abstract/connection_specification.rb:89:in `connection'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/activerecord-3.0.17/lib/active_record/base.rb:685:in `columns'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/activerecord-3.0.17/lib/active_record/base.rb:693:in `columns_hash'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/activerecord-3.0.17/lib/active_record/attribute_methods.rb:13:in `define_attribute_methods'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/activerecord-3.0.17/lib/active_record/attribute_methods.rb:51:in `respond_to?'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/version-1.0.0/lib/rake/version_task.rb:63:in `puts'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/version-1.0.0/lib/rake/version_task.rb:63:in `puts'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/version-1.0.0/lib/rake/version_task.rb:63:in `block in define'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/task.rb:228:in `call'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/task.rb:228:in `block in execute'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/task.rb:223:in `each'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/task.rb:223:in `execute'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/task.rb:166:in `block in invoke_with_call_chain'
/home/maxi/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/task.rb:159:in `invoke_with_call_chain'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/task.rb:152:in `invoke'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/application.rb:143:in `invoke_task'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/application.rb:101:in `block (2 levels) in top_level'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/application.rb:101:in `each'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/application.rb:101:in `block in top_level'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/application.rb:110:in `run_with_threads'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/application.rb:95:in `top_level'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/application.rb:73:in `block in run'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/application.rb:160:in `standard_exception_handling'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/lib/rake/application.rb:70:in `run'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/gems/rake-10.0.3/bin/rake:33:in `<top (required)>'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/bin/rake:23:in `load'
/home/maxi/.rvm/gems/ruby-1.9.3-p194/bin/rake:23:in `<main>'
Tasks: TOP => version
Mmmmm I think I found the problem...
Someone added the gem PaperTrail that add a model called Version :(
When call Version.some use the model instead the version class from your gem.
No worries. It seems they already have an issue open for exactly this, but are waiting for version 3 to deploy a fix, which is regrettable but understandable. In the meantime, you could probably solve the issue with a small bit of monkeypatching to namespace the class yourself.
Hi!, I have a recently problem with the gem (I don't know what change broke this). When try to run any task related with version gem seem to try connect to the database (bizarre!)
This is the result when execute rake version --trace
And my bundle list:
can you help me with this?
Thanks!!!
The text was updated successfully, but these errors were encountered: