| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ / / |
|
| | |
| | |
| | |
| | | |
The RubyGems change just means setting remote! will always cause specs to be fetched remotely
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
Handle yanked gems
Close #4344
|
| | | | |
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add standalone flag to binstubs
Add `--standalone` flag to `binstubs`
Fix #4594
@RochesterinNYC @segiddins
|
| | | | |
|
| | |/
| |/| |
|
|\ \ \
| | | |
| | | |
| | | | |
Version 1.12.5
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Clean up worker threads once done with them
Right now, the thread pools created by CompactIndex are not cleaned up once they are done. I assume that over time, they would be garbage collected, but in the meantime there could be 200+ threads running. Many shared hosts have fork bomb protection set up which kills Bundler.
This patch will clean up the threads as soon as they are done, keeping the total number of active threads at any one time to a minimum.
Fixes https://github.com/bundler/bundler/issues/4367
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix the combination of gem :require and env or install_if
If you guard the installation of a gem with `env` or `install_if`, and that gem declaration has a `:require` option specified, it tried to require the gem even though it hadn't been installed. It looks like a spot was missed when the `env` command was added in the first place.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
[CLI] Only redirect to help when first two args are help and exec
Closes #4596.
\c @RochesterinNYC @b-ggs
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Clean up worker threads once done with them
Right now, the thread pools created by CompactIndex are not cleaned up once they are done. I assume that over time, they would be garbage collected, but in the meantime there could be 200+ threads running. Many shared hosts have fork bomb protection set up which kills Bundler.
This patch will clean up the threads as soon as they are done, keeping the total number of active threads at any one time to a minimum.
Fixes https://github.com/bundler/bundler/issues/4367
|
| | | | | |
|
| | |/ /
| |/| | |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
If you guard the installation of a gem with env or install_if, and that
gem declaration has a :require option specified, it tried to require
the gem even though it hadn't been installed. It looks like a spot was
missed when the env command was added in the first place.
|
| |/
|/| |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Use the full expanded path of passed `Gemfile` during `eval_gemfile`
- fixes #4584
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | |/
| |/|
| | | |
Version 1.12.4
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
[Index] Ensure nil and "ruby" platforms are treated identically
Fixes #4557.
@indirect @RochesterinNYC ideas on how to test this?
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
don't error on missing rubygem cred if custom host
only raise error asking user to set rubygem credentials during gem push
if `allowed_push_host` is not set.
Fixes https://github.com/bundler/bundler/issues/4437
Apologies if this is a half baked PR.
- I looked around to add tests for this, but there is little test coverage over this area I simply wasn't sure how to add a test around this particular change.
- I also wasn't sure where to put this in the `CHANGELOG` as the latest entry there is already released.
|
| | |
| | |
| | |
| | |
| | |
| | | |
[Git] Fix checking for equality when a version includes a -
Closes #4385.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Safely store concurrent compact index downloads
When bundler is run concurrently using the same bundle dir in $HOME,
the versions file can be updated from two processes at once. The
download has been changed to a temporary file, which is securely moved
into place over the original.
If retrying the update operation, the original file is no longer
immediately deleted and instead a full download is performed, later
overwriting the original file if successful.
If two processes are updating in parallel, this should ensure the
original file isn't corrupted and that both processes succeed.
- Fixes #4519
---
This would be useful on 1.12.x if possible, since the new caching behaviour with a shared home directory is causing the errors described in #4519.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
[Index] Ensure nil and "ruby" platforms are treated identically
Fixes #4557.
@indirect @RochesterinNYC ideas on how to test this?
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Cleans up unused Runtime#dependencies_for method
Hi!
I was checking out things in the code and couldn't find any existent usage of this method. I might be missing something but opening the PR just in case.
The method seems to be publicly accessible if someone goes `Bundler.load.dependencies_for(...)` e.g., but i am assuming that's not something "officially supported" anyways?
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
[Git] Fix checking for equality when a version includes a -
Closes #4385.
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Safely store concurrent compact index downloads
When bundler is run concurrently using the same bundle dir in $HOME,
the versions file can be updated from two processes at once. The
download has been changed to a temporary file, which is securely moved
into place over the original.
If retrying the update operation, the original file is no longer
immediately deleted and instead a full download is performed, later
overwriting the original file if successful.
If two processes are updating in parallel, this should ensure the
original file isn't corrupted and that both processes succeed.
- Fixes #4519
---
This would be useful on 1.12.x if possible, since the new caching behaviour with a shared home directory is causing the errors described in #4519.
|
| | |_|_|_|/
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When bundler is run concurrently using the same bundle dir in $HOME,
the versions file can be updated from two processes at once. The
download has been changed to a temporary file, which is securely moved
into place over the original.
If retrying the update operation, the original file is no longer
immediately deleted and instead a full download is performed, later
overwriting the original file if successful.
If two processes are updating in parallel, this should ensure the
original file isn't corrupted and that both processes succeed.
- Fixes #4519
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
don't error on missing rubygem cred if custom host
only raise error asking user to set rubygem credentials during gem push
if `allowed_push_host` is not set.
Fixes https://github.com/bundler/bundler/issues/4437
Apologies if this is a half baked PR.
- I looked around to add tests for this, but there is little test coverage over this area I simply wasn't sure how to add a test around this particular change.
- I also wasn't sure where to put this in the `CHANGELOG` as the latest entry there is already released.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
only raise error asking user to set rubygem credentials during gem push
if `allowed_push_host` is not set.
|
|\ \ \ \ \ \
| |_|_|_|/ /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
RochesterinNYC:only-show-potential-updates-on-same-platform, r=RochesterinNYC
Only show potential updates on same platform for `bundle outdated`
This fixes the following behavior:
Say you're using a gem `laduradura` on platform `java` with version `v1.0.1`. The latest `java` platform version of this gem is `v1.0.1` but the latest `ruby` platform version of this gem is `v1.0.2`. Running `bundle outdated` will currently tell you that you can update `laduradura` to `v1.0.2`.
This is a bad user experience as the user is given the suggestion to update `laduradura` to `v1.0.2`, despite this version being on a completely different platform than the one that the user is currently using `laduradura` on.
With this PR, `bundle outdated` will only report potential version updates to gems for the same platforms those gems are being used on.
- Fixes #4450
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- `bundle outdated` will now only show updates for a gem if there are
available updates for that gem on the same platform
- ex. gem `laduradura` is being used on ruby platform but updates are
available on gem `laduradura` for java platform = do not display
potential update versions for java
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
is an array of specs
|
|\ \ \ \ \ \
| | |_|_|_|/
| |/| | | |
| | | | | | |
Version 1.12.3
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
[CompactIndex] Fall back when the user's home directory is not writable
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
[Install] Don't set :no_install unecessarily
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
[CompactIndex] Fall back when the user's home directory is not writable
|
| | | | | | | |
|
|/ / / / / / |
|