Indirect Cycle Causes Conflict Graph to Hang Indefinitely about rez HOT 3 CLOSED

Thanks for reporting this @Pantsworth! Also, nice work on creating a small repro scenario!

If you think you know how to fix the problem, we'll definitely welcome a PR.

I'm curious, how often do you hit this bug?

from rez.

Thanks for the quick reply!

There's really just one specific case where we're seeing it, which is how we set up python and openssl.

In our setup, python requires openssl, but our most recent openssl package has !python-2 and !python-3.7 requirements, which was a workaround to keep our older python packages from resolving a too-new version of openssl, since they weren't pinned to a specific openssl version. Basically, python is foo in my example, and openssl is bar.

Those package requirements by themselves don't cause any issues with resolving, but if there's a conflict somewhere else during the process, Rez can get stuck trying to draw/print the resolve graph due to the cycle in openssl/python.

The fix I mentioned above should solve the issue - I think it's just the graphing step that's causing trouble here :)

from rez.

Thanks for the additional information! It's always nice to hear how our users use rez and and define their dependencies.

Like I said, feel free to create a PR. Bonus points if you also add a test!

from rez.