| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
The Process method is not available before then
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With bundler 1.11.2, the process name for rake tasks looked like this:
$ bundle exec rake foo:bar
$ ps ux | grep rake
user 1758 62.2 2.4 385816 202032 pts/3 Sl+ 16:16 0:04 ruby /usr/bin/rake foo:bar
On bundler 1.12.0, the process name changed:
$ bundle exec rake foo:bar
$ ps ux | grep rake
user 1758 62.2 2.4 385816 202032 pts/3 Sl+ 16:16 0:04 /usr/bin/rake
The change in behaviour is caused by bundler 1.12 using `load` (instead of `exec`) where
possible, and manually using `$0=` to set the command name. Unfortunately, that also alters
the process title visible with ps, and using Process.setproctitle can help reverse that
|
|\
| |
| |
| |
| |
| | |
[Setup] Only add bundler to the load path if we havent trampolined
@indirect this should fix the stack overflow bug!
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Allow installing / updating when everything necessary is available locally
This should ideally have some tests, but right now it's behind a feature flag
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Unlock sources when a local override leads to changes
Closes #4838.
Requires tests
|
| | | |
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
[Install] Print errors at the end of installation instead of inline
This needs test coverage
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | | |
Add manpage for bundle-binstubs
This PR is intended to resolve https://github.com/bundler/bundler/issues/4000.
|
|/ / |
|
|\ \
| |/
|/|
| | |
Clean up spec output on Travis
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| | |
Allow signed tags on rake release
Removing `--annotate` option does not change default behaviour
Since git 2.9.0 its possible to configure signed tag with
`tag.forceSignAnnotated` to true
Cheers
|
| |
| |
| |
| |
| |
| |
| | |
Removing `--annotate` option does not change default behaviour
Since git 2.9.0 its possible to configure signed tag with
`tag.forceSignAnnotated` to true
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
WIP: add command to check dynamic library linkage
This new command, linkage, checks for broken dynamic library links in C extensions.
I'd heard there was some interest in adding this functionality, so I thought I'd submit a preliminary PR for discussion. In my experience, broken dylib linkage is a common issue with C extensions, so I think having a good way to diagnose it would be valuable.
This command scans all of the specifications in the bundle for .bundle files in C extensions. If any of the dynamic libraries linked against no longer exist, bundler will report a message to the console and exit non-0.
TODOs:
* Add support for non-Darwin OSs
* Improve tests
A few questions:
* Is there a good way to mock functionality in the tests? Doing it in the standard rspec way isn't working since `bundle :command` runs in a subprocess. I'd like to be able to stub out stuff that actually checks dylibs and the like.
* Is making this a new command the right approach? I assumed this wouldn't be ideal to include in, say, `check` because it would slow it down.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This will eventually support other tests, so the dylib test needs to be
able to to meaningfully return an empty result
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This new command, doctor, checks for common problems.
Currently, it looks for broken dynamic library links in C
extensions.
It scans all of the specifications in the bundle for .bundle files in C
extensions. If any of the dynamic libraries linked against no longer
exist, bundler will report a message to the console.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove Bundler::Environment
Pretty straightforward refactoring
|
| | | | |
|
| | | | |
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove expect_err from the specs & print all output on a spec failure
This now also appends all executed commands to failed examples, meaning we don't have to scroll up to see the output from a failing test:
```
Failures:
1) The library itself does not contain any warnings
Failure/Error:
sys_exec!("ruby -w -I.") do |input, _, _|
lib_files.each do |f|
input.puts "require '#{f}'"
end
input.puts "abort 'fdsfds'"
end
RuntimeError:
Invoking sys_exec!("ruby -w -I.") failed:
fdsfds
Commands:
$ ruby -w -I.
fdsfds
# $? => 1
# ./spec/quality_spec.rb:205:in `block (3 levels) in <top (required)>'
# ./spec/quality_spec.rb:196:in `chdir'
# ./spec/quality_spec.rb:196:in `block (2 levels) in <top (required)>'
```
|
| | | | |
|
| | | | |
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | | |
[Graph] Remove monkey-patching of Gem::Dependency
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|