-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not find bundler #369
Comments
What happens if you run this?
|
Also, this seems related: guard/guard-bundler#32 So you are probably using Notice that your
while your (And that's why you get the error: bundler isn't installed in that last location). Try this workaround here: guard/guard-bundler#32 (comment) |
ths @e2 now i don't use --path on bundle > 1.12.x command
test
|
I'm wondering what the solution should be. And where it should be implemented. If it's just Guard::RSpec you need, you can probably just change guard :rspec, cmd: 'bundle exec rspec' to guard :rspec, cmd: 'rspec' Because, if you run Guard with The other option is to use the short Hope that helps. |
I ran into this as well, and after some investigation I saw that in rspec_process line 70, a bundler method with_clean_env is being used. Looking at that in bundler, I saw a notice about clean_env being deprecated in favor of original_env. And changing the line solved this problem for me. So line 70 in rspec_process.rb becomes:
Unsure if there are any wider implications, or if bundler should fix the original method. But this worked as a workaround for me. |
Yes, I suspected something like this. I didn't know about original_env - but it seems like it actually does To be on the safe side, I'd suggest a Guard::RSpec configuration
This is because since you can pass any command to Guard::RSpec to run E.g. some users may prefer to run RSpec without bundler at all (for If someone can create a PR for this, I'd be happy to merge it. On Tue, May 24, 2016 at 03:11:19PM -0700, Andy Camp wrote:
|
Fix released in 4.2.7. (Thanks to @soberstadt !) |
Is 4.2.7 really correct @e2? The latest version of this gem is 4.7.1, and 4.2.7 was released in February. Maybe you meant to release as 4.7.2, but this failed? |
Yes, I think there might have been a mix up. You made the tag: https://github.com/guard/guard-rspec/releases/tag/v4.7.2 but it hasn't made it to rubygems yet. |
@benlangfeld , @soberstadt - yes, gem push seemed to have failed :( Credential issues likely. Fixed. |
Thanks @e2! |
Software
bundle exec gem list|grep guard
bundle exec guard -d
gem env
The text was updated successfully, but these errors were encountered: