-
-
Notifications
You must be signed in to change notification settings - Fork 2k
bundle exec rake and rspec updates gems #3142
Comments
@omegahm could you please try the 1.7.1 prerelease (run |
Sorry... missed your last sentence. We're looking into the stall (see #3141). |
Also applicable for newer Rubies. (Same error with |
@TimMoore I tried with 1.7.1 but after 10 minutes of nothing, I had to cancel it and go back to work 😄 |
We should have a new prerelease or a 1.7.1 final release tomorrow. Sorry for the wait! |
We're having this issue as well after upgrading to 1.7.0 when we try to use a rails console or run specs. I tried 1.7.1.pre.3 but it's still happening there as well. |
Please follow ISSUES and supply a reproduction case so I can make sure the problem is fixed. Thanks! |
@omegahm did you happen to have Spring running? |
Okay, @indirect, I got it now. I have a repro at https://github.com/jonhyman/bundler-3142. I created a Rails project with an out of date gem that is not pegged to a certain version. It looks like the bug is happening when I have a second
|
Perfect, thanks. I'll look at this soon. On Tue, Aug 19, 2014 at 3:03 PM, Jonathan Hyman notifications@github.com
|
Thanks for the repro case! I'm happy to report that this is fixed in 1.7.1.pre.3. I'll be releasing 1.7.1 final a little later today. |
We have a very weird problem.
When running
bundle exec rake 'hello'
(which fails) it updates all of my gems. The same is true forbundle exec rspec
, but not e.g.bundle exec echo 'hello'
.My (very truncated)
Gemfile
looks like this:This is occurring in Bundler v. 1.7.0. 1.6.4 works as expected. I couldn't try the prerelease, because it just stalled during
bundle exec rake 'hello'
.The text was updated successfully, but these errors were encountered: