Closed bleything closed 11 years ago
Good, it's not just me.
There is a magic "even more verbose" option! Run DEBUG_RESOLVER=1 bundle install
to see exactly what is happening inside the resolver. Chances are that this will help you figure out exactly where it is getting stuck. If there is a way to keep the resolver from going off into the weeds, that's where the key will lie.
This looks odd ―
Fetching from: http://rubygems.org/api/v1/dependencies?gems=memcache-client,tzinfo?gems=memcache-client,tzinfo
Specifically the ?gems=memcache-client,tzinfo?gems=memcache-client,tzinfo
veewee seems to have conflicting requirements on its own, so a simpler way to see this is:
git clone https://github.com/jedi4ever/veewee
cd veewee
git checkout 764f56ba
DEBUG_RESOLVER=1 bundle install
(if you're using RVM, its rvmrc wants a 1.9.2 ruby. Yes, veewee needs to fix its requirements, but Bundler shouldn't hang trying to resolve bad ones :-) )
What do you mean by "hang"? Does it stop trying to resolve? Or does it take a long time to resolve? There are known cases where resolving can take a very long time if the graph is extremely complicated.
Thanks André; I meant "hang" in that I gave up after five minutes (without the extra logging); it quickly pinned one CPU of my core i7 box. Doesn't seem to be leaking memory or doing any I/O (no surprise there). Turning the extra logging on produced 14Mb of output in the first 10 seconds, which is why I didn't post it; I did look through it a little, only to see that it seemed to be cycling through acceptable vagrant versions.
Looking more closely, it is permuting acceptable versions of several gems, and if I let it run (without logging), it does eventually finish successfully (after 6 minutes 31 seconds).
I'm guessing that Ben's original problem above is the result of the difficult search to satisfy veewee, complicated by the other dependencies in his Gemfile. I set up his gemfile (with Bundler 1.1.3) and let it run; it still hasn't finished after 15 hours.
Triaging this: just tried to reproduce the steps above, current bundler 1.3.0 seems to resolve dependencies (installed vagrant 1.0.6). I think this can be closed.
Great, thanks for reporting back!
Hello friends! I've got what I think is a bug, and Evan asked me to open a ticket. Consider this gemfile:
bundle install
will work fine here. But now addgem 'veewee'
and try again. With bundler 1.0.22, I get no feedback, and if I Ctrl-C, I see this:There are hundreds more lines like that. With bundler 1.1.1, I can use --verbose, and I see this:
... it hangs at that last line for longer than I have patience to wait.