-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
bundle install --local in test tries to contact remote #185
Comments
In your local setup, have you switched git to use If I restore this value to |
Oh! I think I understand the problem properly now. I was previously running 2.2.4, and seeing failures around this test, too, which confused me. I upgraded In the test, we're just running |
This is now fixed upstream I think! |
Wonderful! Thank you, @deivid-rodriguez. @marcotc, could you try this again at some point and see if your problem is resolved? |
While implementing #184, I noticed that
appraisal
tests (invokingrake
in this repository) were failing.At first they were failing with the issue addressed by #184, but after fixing that there's still one more test failing:
This errors happens only with newer versions of bundler.
After bisecting the bundler changes, I found that rubygems/rubygems@d8b59a1 introduces the behaviour makes this test fail (which was released with bundler 2.2.14).
It seems like
bundle install --local
wants to contactother-rubygems.org
, which doesn't seem right.When using a version of bundler from before rubygems/rubygems@d8b59a1, it does not try to contact the remote.
I wasn't able to decipher what part of rubygems/rubygems@d8b59a1 is the culprit, or if the issue is in appraisal or in bundler itself. I'm opening the issue here as this is manifested in one of the tests in the repository.
The text was updated successfully, but these errors were encountered: