David Matthews

> However, you raise an interesting point... which I take to mean we should consider allowing cylc play --flow=N to restart a stopped flow in a running workflow! (maybe I...

> This would be convenient during development, in the source directory, which typically involves a lot of repetition of `cylc install` then `cylc play my-long-workfow-id` and `cylc stop my-long-workflow-id`. #3896...

List available versions: - This wouldn't work for us because we install the Cylc environments into a directory containing lots of other things. - For Cylc 8 it's environments rather...

> automatically invoke cylc-7.9.5 if cylc review is called in a Cylc 8 environment? Fixed in #4655. However a new enhancement was raised: make the prefix and the name of...

I've discussed this with @oliver-sanders and we'd like to propose not supporting `--flow=none` (can't really think of a good use-case). I've also thought of some other considerations so here's an...

Note that the same happens with a Cylc 7 workflow if you run it in a sub-directory of `cylc-run` - the issue is the directory hierarchy

The current behaviour is deliberate - ssh could fail for other reasons so we don't remove the contact file unless we can connect to the server to check whether the...

> Cylc 8 issue - #4513 #4513 is really a different issue (polling doing the wrong thing). This issue is about polling happening on the wrong platform. I've confirmed that...

``` [[graph]] R1 = "prep => foo" P1 = "foo" R1/$ = "foo => clean" ``` Not sure I like this. One of the key features of Cylc is the...

> you might have chimed in back on https://github.com/cylc/cylc-flow/issues/4903!! Sorry! > But inter-cycle triggers would make that even worse (the offset would break pre-initial ignore). Yuck - hadn't thought of...