rake db: reset jette l'erreur

Question

Je suis le napa api framework tutorial sur la façon de créer des API. Mais sur l'exécution de son rake db:reset soulevant l'erreur suivante

WARN: Unresolved specs during Gem::Specification.reset: 
    minitest (~> 4.2) 
WARN: Clearing out unresolved specs. 
Please report a bug if this causes problems. 
rake aborted! 
NameError: uninitialized constant Virtus::Configuration::Coercible 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/virtus-1.0.5/lib/virtus/configuration.rb:40:in `initialize' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/virtus-1.0.5/lib/virtus/builder.rb:28:in `new' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/virtus-1.0.5/lib/virtus/builder.rb:28:in `call' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/virtus-1.0.5/lib/virtus.rb:152:in `model' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/representable-1.8.5/lib/representable/coercion.rb:5:in `<class:Coercer>' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/representable-1.8.5/lib/representable/coercion.rb:4:in `<module:Coercion>' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/representable-1.8.5/lib/representable/coercion.rb:3:in `<top (required)>' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/roar-0.12.9/lib/roar/representer/feature/coercion.rb:2:in `require' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/roar-0.12.9/lib/roar/representer/feature/coercion.rb:2:in `<top (required)>' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/napa-0.4.3/lib/napa/output_formatters/representer.rb:3:in `require' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/napa-0.4.3/lib/napa/output_formatters/representer.rb:3:in `<top (required)>' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/napa-0.4.3/lib/napa.rb:27:in `require' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/napa-0.4.3/lib/napa.rb:27:in `<top (required)>' 
/home/jay/AppService/app.rb:6:in `require' 
/home/jay/AppService/app.rb:6:in `<top (required)>' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:126:in `require' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:126:in `require' 
/home/jay/AppService/Rakefile:6:in `<top (required)>' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/rake-10.4.2/lib/rake/rake_module.rb:28:in `load' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/rake-10.4.2/lib/rake/rake_module.rb:28:in `load_rakefile' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:689:in `raw_load_rakefile' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:94:in `block in load_rakefile' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:93:in `load_rakefile' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:77:in `block in run' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:75:in `run' 
/home/jay/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/rake-10.4.2/bin/rake:33:in `<top (required)>' 
/home/jay/.rbenv/versions/2.0.0-p576/bin/rake:23:in `load' 
/home/jay/.rbenv/versions/2.0.0-p576/bin/rake:23:in `<main>' 

Toute aide serait appréciée.

Answer 1

Un an plus tard, je suis confronté à un problème similaire. Je l'ai résolu. En essayant de parcourir Napa quickstart sur Mac OS El Capitan, j'ai remarqué qu'il tirait napa 0.5.1 ce qui n'était pas compatible. La première chose que j'ai faite a été de changer pour napa 0.5.0.

La prochaine chose était de changer l'enregistrement actif 4.2.0 de 4.0.0 qui s'est débarrassé du problème minitest gem.

J'espère que cela aidera quiconque visite napa pour la première fois et ne peut pas faire fonctionner le quicstart.

Aussi, j'ai essayé le quickstart avec MySQl et non Postgres que le tutoriel utilise.