Removing a "rank=same" constraint in the graph fixed the problem in practice for me, and also in the upstream steps to reproduce.
I encourage anyone stumbling on the same bug to at least add a comment here so that upstream author get to know that the bug affects users in real-world use and so needs to be fixed.
Removing a "rank=same" constraint in the graph fixed the problem in practice for me, and also in the upstream steps to reproduce.
I encourage anyone stumbling on the same bug to at least add a comment here so that upstream author get to know that the bug affects users in real-world use and so needs to be fixed.