| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |\
| |
| |
| | |
Test against latest Ruby & RG on travis
|
| | | |
|
| | | |
|
| |\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use new RSpec syntax in spec template
This little pull request, juste for use actual new syntax for begin an spec file.
```ruby
RSpec.describe "MyAwesomeSpec" do
end
```
instead
```ruby
describe "MyOldAwesomeSpec" do
end
```
link: https://github.com/rspec/rspec-rails/commit/ca0d249858903949052e06884e8e7f9d596cdc79
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
[CompactIndexClient] Synchronize access to the list of fetched endpoints
Should fix #5142.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This is a temporary measure until we can ensure everything is properly synchronized
|
| | | | |
|
| | | | |
|
| |/ / |
|
| | | |
|
| |\ \
| | |
| | |
| | | |
[Rakefile] Speed up rake spec:deps
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Dont build defintion with Gemfile.lock (if present) when resolving gems via inline gemfile
This fixes #5117
I am passing an option to `Installer` to not build a definition when resolving gems via inline gemfile.
Also, i notice: `Bundler.default_lockfile.exist? && !options["update"]...`. Is "update" suppose to be a string? I ask because i noticed that other options are being passed as symbols, so I'm not which i'm suppose to be using.
Thanks.
PS. Hopefully i have the bundler terminology correct 😄
|
| | | | |
|
| | | |
| | |
| | |
| | | |
installed on ruby < 2.0
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | | |
[CompactIndexClient] Fix warning
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
[CLI::Gem] Fail gracefully on an invalid constant name
Closes #5185.
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | | |
Replace fakeweb in the specs with artifice
Closes #5166
|
| | |/ / |
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Improve gem checksum mismatch error message
Improve gem checksum mismatch error message by telling users how to resolve it.
Old message:
```
The checksum for the downloaded `rack-1.0.0.gem` did not match the checksum given by the API. This means that the contents of the gem appear to be different from what was uploaded, and could be an indicator of a security issue.
(The expected SHA256 checksum was "abababababababababababababababababababababab", but the checksum for the downloaded gem was "BR6Oc6Gqnq93u1aIVX4m6DvTHaFgFxdYaLUfa4ekJKI=".)
Bundler cannot continue installing rack (1.0.0).
```
New message:
```
Bundler cannot continue installing rack (1.0.0).
The checksum for the downloaded `rack-1.0.0.gem` does not match the checksum given by the server. This means the contents of the downloaded gem is different from what was uploaded to the server, and could be a potential security issue.
To resolve this issue:
1. delete the downloaded gem located at: `full-path/gems/rack-1.0.0/rack-1.0.0.gem`
2. run `bundle install`
If you wish to continue installing the downloaded gem, and are certain it does not pose a security issue despite the mismatching checksum, do the following:
1. run `bundle config disable.checksum_validaiton true` to turn off checksum verification
2. run `bundle install`
(More info: The expected SHA256 checksum was "abababababababababababababababababababababab", but the checksum for the downloaded gem was "PbfaoemSetv76QdcxuoP0ggZ0TZhMELlMMWURJoX+dw=".)
```
Closes #5075
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Improve and fixed guide style code from outdated cmd
Hi,
I separate these part from this PR https://github.com/bundler/bundler/pull/5058.
Regards.
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
r=segiddins
Documentation and error improvements
This PR is just making a few small improvements to error messages, documentation and code indentation.
Let me know what you think.
Thanks!
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | |/
| |/| |
|
| |\ \ \
| |_|/
|/| |
| | | |
Fix x64_mingw_24. Typo in PR #5170
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fix outdated regression from cc355865
Refactoring of @lucasmazza fix w/ specs.
The only existing spec coverage was essentially integration level and
there was no way either @lucasmazza or myself could find a way to
simulate the bug context.
I extracted some of the code out of outdated into Definition and
SpecSet and added unit specs to those extracted bits.
Fixes #4979
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The only existing spec coverage was essentially integration level and
there was no way either @lucasmazza or myself could find a way to
simulate the bug context.
I extracted some of the code out of outdated into Definition and
SpecSet and added unit specs to those extracted bits.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Closes: #5173
Approved by: indirect
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Support :mri_24 platform
Current ruby trunk is versioned as "2.4.0".
% ruby -ve 'p RUBY_VERSION'
ruby 2.4.0dev (2016-11-15 trunk 56792) [x86_64-darwin15]
"2.4.0"
We'd like to run tests on some gems against ruby-trunk or 2.4 pre-releases, so here's a support for MRI 2.4.
(This is Ruby 2.4 version of #3865)
|
| |/ / / |
|
