The following is a way to determine where in the codebase
bundler is stalling when fetching from external sources (rubygems.org, github.com, etc.). Use this as a way to determine where in the codebase
bundler is stalling when it is happening without stopping the process or requiring modifications to the source directly.
- Download the
bundler_trap.rb script and put is somewhere easily accessible (I use the home directory in my examples).
- Run bundler using the following command:
ruby -I~ -rbundler_trap bin/bundle update
- You will have to repeat step to until you get to a situation where
bundler has stalled. When it does, send the
INFO signal to the process (
CMD+t on OSX, and on Linux, it should be
kill -sINFO pid, but you might have to use a different signal).