Hi Paul, On Wed, Mar 9, 2022 at 8:02 PM Paul Kocialkowski <paul.kocialkowski@xxxxxxxxxxx> wrote: > > While bridge/panel detection was initially relying on the usual > port/ports-based of graph detection, it was recently changed to > perform the lookup on any child node that is not port/ports > instead when such a node is available, with no fallback on the > usual way. > > This results in breaking detection when a child node is present > but does not contain any panel or bridge node, even when the > usual port/ports-based of graph is there. Can you add that pipeline example on the commit message, it gives more information on specific use cases why the existing code breaks. Thanks, Jagan.
