Cycle detection bug

[kevin-delmas]

The cycle detection seems to send false alarms, i.e. cycles that are not reachable for the identified transaction.
@Gaudeval Can you provide a MWE of that problem from the complex example on which the problem has been observed?

[Gaudeval]

There is a small example in the related branch. The issues seems to require a routing constraint to trigger (blockedBy in the example https://github.com/onera/pml-analyzer/tree/f83cce4e7c8bea75be3a6e7eea21606604e581b2/src/test/scala/onera/pmlanalyzer/pml/model/cycle)

A cycle is (correctly) detected between components which are not connected to the initiator, its target, or the blocking component.

I will add to the example to see if the issue also occurs with a more traditional cannotUseLink.

[Gaudeval]

I can confirm the issue also occurs with the cannotUseLink operator. So any routing constraint in the MWE will cause the unreachable cycle to be detected and reported.