This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2k
bundle exec updating Gemfile.lock #3298
Comments
Very strange, what's the diff in Gemfile.lock when you run bundle exec? |
git diff
diff --git a/Gemfile.lock b/Gemfile.lock
index de47712..1c0cf74 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -41,15 +41,15 @@ GEM
rack
awesome_print (1.2.0)
- aws-sdk (1.59.0)
- aws-sdk-v1 (= 1.59.0)
- aws-sdk-v1 (1.59.0)
+ aws-sdk (1.59.1)
+ aws-sdk-v1 (= 1.59.1)
+ aws-sdk-v1 (1.59.1)
json (~> 1.4)
nokogiri (>= 1.4.4)
builder (3.2.2)
celluloid (0.16.0)
timers (~> 4.0.0)
- celluloid-eventsource (0.2.0)
+ celluloid-eventsource (0.2.1)
celluloid-io (~> 0.15.0)
http_parser.rb (~> 0.6.0)
celluloid-io (0.15.0) |
This may be related to #3175. @Tonkpils would you be able to try it out with the code on this branch? https://github.com/TimMoore/bundler/tree/issue-3175-unlocked-sources |
Sure @TimMoore I'll post back with the results |
@TimMoore that branch seems to have fixed the issue. I was able to reproduce the issue with bundler 1.7.9 doing a |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A couple of issues have been happening since 1.7.8. This is one of them I've run into.
The following commands were run back to back
Here's the output of
bundle env
The text was updated successfully, but these errors were encountered: