Guard seems to load non-bundled RSpec version

Question

Guard seems to load non-bundled RSpec version

vrinek opened this issue 10 years ago · comments

I have rspec-core v2.14.7 bundled for my project and I have rspec-core v2.14.8 in my system gems. Bundler is complaining that the system rspec-core has been activated instead of the bundled one (see second gist).

bundle exec rspec spec/some_file_spec.rb works fine.

Not really sure if this is a bug with guard, guard-rspec, bundler or even rspec.

Guardfile https://gist.github.com/vrinek/48091a388ffa21864e91
Output https://gist.github.com/vrinek/16daf191d3d8b88b34bd
Ruby 2.1.0

Aleksei Chernenkov · Answer 1 · Mon Apr 07 2014 18:49:02 GMT+0800 (China Standard Time)

@vrinek Are you running guard with bundle exec guard?
ED: Sorry, I'm seeing it in the gist.

Kostas · Answer 2 · Mon Apr 07 2014 20:16:05 GMT+0800 (China Standard Time)

@907th yes, I have tried both with and without bundle exec and the result is the same complain about different versions of rspec-core.

Kostas · Answer 3 · Tue Apr 08 2014 18:21:44 GMT+0800 (China Standard Time)

I guess providing a showcase codebase able to reproduce the error would help, right?

Aleksei Chernenkov · Answer 4 · Tue Apr 08 2014 18:26:04 GMT+0800 (China Standard Time)

@vrinek Yes, it would be helpful.

Kostas · Answer 5 · Sat Apr 12 2014 01:11:00 GMT+0800 (China Standard Time)

I took my original Rails app and started deleting files https://github.com/vrinek/guard-rspec-bug. In order to re-create the bug:

bundle install
gem install rspec-core -v '2.14.8'
bundle exec rspec spec/routing/attachments_routing_spec.rb this should work
bundle exec guard and press enter <-- this should fail

Please let me know when you try it.

Kostas · Answer 6 · Tue Apr 22 2014 21:58:45 GMT+0800 (China Standard Time)

Did you try the code I linked to? Was it helpful to reproduce the bug?

Aleksei Chernenkov · Answer 7 · Fri Apr 25 2014 12:34:22 GMT+0800 (China Standard Time)

@vrinek Sorry. I didn't looked at it yet ( It were very busy weeks for me.

Joshua Kovach · Answer 8 · Wed Apr 30 2014 22:23:09 GMT+0800 (China Standard Time)

I'm seeing this with other guard-rspec dependencies as well. Despite calling bundle exec guard, when running rspec with it, it freaks out if there are versions different from what's currently activated by bundler on my system:

10:16:11 - INFO - Running all specs
WARN: Unresolved specs during Gem::Specification.reset:
      listen (~> 2.7)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
WARN: Unresolved specs during Gem::Specification.reset:
      rb-inotify (>= 0.9)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.

When listen had a lower bundled version than was available on the system, it would raise an error saying to prefix the command with bundle exec. Updating the bundle the use the latest version on the system fixed the error, but not the warnings.

I have several other guard plugins installed, and all of those seem to work fine without errors and warnings. Only when running with rspec does it seem to have a problem.

Thibaud Guillaume-Gentil · Answer 9 · Thu May 01 2014 03:58:15 GMT+0800 (China Standard Time)

@shekibobo on which version of ruby and rubygems are you?

Have you try with guard :rspec, cmd: 'bundle exec rspec' do

Joshua Kovach · Answer 10 · Thu May 01 2014 04:11:16 GMT+0800 (China Standard Time)

@thibaudgg Changing the command does eliminate the warnings, thanks!

Kostas · Answer 11 · Sat May 03 2014 06:41:54 GMT+0800 (China Standard Time)

@thibaudgg this fixed my issues as well. Kudos!

Should I close this issue then?

Joshua Kovach · Answer 12 · Sat May 03 2014 07:16:58 GMT+0800 (China Standard Time)

Since guard warns you if you're not using bundler, shouldn't this either detect and warn or use bundler if it's available?