guard/guard-spork — Issue #35: spork stops running
Author: frankapimenta
Created: 2011-10-08 12:49:41+00:00
State: open

When I hit spork or guard (spork) I have the following error:

rvm/gems/ruby-1.9.2-p180@rails31/gems/bundler-1.0.18/lib/bundler/runtime.rb:68:in `require'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/bundler-1.0.18/lib/bundler/runtime.rb:68:in `block (2 levels) in require'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/bundler-1.0.18/lib/bundler/runtime.rb:66:in `each'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/bundler-1.0.18/lib/bundler/runtime.rb:66:in `block in require'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/bundler-1.0.18/lib/bundler/runtime.rb:55:in `each'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/bundler-1.0.18/lib/bundler/runtime.rb:55:in `require'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/bundler-1.0.18/lib/bundler.rb:120:in `require'
.../config/application.rb:7:in `'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/spork-0.9.0.rc9/lib/spork/app_framework/rails.rb:48:in `require'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/spork-0.9.0.rc9/lib/spork/app_framework/rails.rb:48:in `preload_rails'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/spork-0.9.0.rc9/lib/spork/app_framework/rails.rb:7:in `preload'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/spork-0.9.0.rc9/lib/spork/test_framework.rb:134:in `block in preload'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/spork-0.9.0.rc9/lib/spork.rb:62:in `exec_prefork'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/spork-0.9.0.rc9/lib/spork/test_framework.rb:120:in `preload'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/spork-0.9.0.rc9/lib/spork/run_strategy/forking.rb:25:in `preload'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/spork-0.9.0.rc9/lib/spork/runner.rb:74:in `run'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/spork-0.9.0.rc9/lib/spork/runner.rb:10:in `run'
.rvm/gems/ruby-1.9.2-p180@rails31/gems/spork-0.9.0.rc9/bin/spork:10:in `'
.rvm/gems/ruby-1.9.2-p180@rails31/bin/spork:19:in `load'
.rvm/gems/ruby-1.9.2-p180@rails31/bin/spork:19:in `

'

Which is caused by:

Bundler.require *Rails.groups(:assets => %w(development test))

in application.rb

if I comment the line above everything works fine. My questions are what is the problem? how can it be solved? is it a bug?

Best.