Why is bundler so slow

Ah - now we can see how Bundler 1. If you paste one of those URLs into a browser you can see the dependencies for the specified gems encoded in some complex format that resembles JSON. Notice that the response includes the dependencies for each version of the gem, not just the latest version. You can also provide a list of comma separated gem names, such as what we see Bundler doing in the verbose output above:.

Now Bundler has all the dependency information it needs, so it continues by running the resolver algorithm and then outputs the gems that were included in my new bundle:. No, master only. Seems still reproducible. Sign up for free to join this conversation on GitHub.

Already have an account? Sign in to comment. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. At commit g00ccc5. I tried locking the version of activesupport to no avail. Here is a gist of the debug output I stopped during processing. I am no longer in this state so it would be difficult for me to provide more information at this time to warrant opening an issue. Because of the backtracking?

Any reference to similar NP-complete problems, or any extra information would be helpful! Skip to content. This repository has been archived by the owner.

It is now read-only. Star 4. Linked pull requests. Copy link. Bundler refuses to update Contributor Author. Otherwise, nil is returned. Here's a excerpt of the final lock: activemodel 3. Optimize conflict resolution to prevent "infinite loop" effect If you're not seeing the dots, please open a new issue and we'll try to investigate.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window.