With Cylc 8.3.6, I noticed that if I have an n-window display >1
, and execute a suicide trigger pathway, the removed item still appears in the graph. With n=1, it is removed, but not at higher levels. I was wondering if this was expected. I’m guessing yes because at n=2, there would be a way to get to that removed task, but I wanted to confirm.
Yes, this is expected.
It is the result of the way that we compute the n-window around the n=0 window. While the task remains in the n=0 window, we know that it was “suicided”, once it drifts out of this window, we loose that information.
Closely related to this issue: n-window: exclude omitted branches · Issue #5799 · cylc/cylc-flow · GitHub