Hilary James Oliver
Hilary James Oliver
Log attempts to spawn at invalid cycle points. This make it easier to understand the examples of #4514, pending decisions on what to do about that issue. These changes partially...
Following on from @dpmatthews [4 days ago](https://github.com/cylc/cylc-flow/issues/4728#issuecomment-1065278990) > `cylc stop currently` supports `--flow=INT` which means "Stop flow number INT from spawning more tasks". > I don't really like this for...
The `cylc remove` command currently: - (only) removes task proxies from the `n=0` pool - does not causing spawning downstream of the removed task - use cases: - remove incomplete...
Consider `cylc set-outputs` in light of final agreed behaviour of `cylc trigger` as per #4686 with respect to flows in particular. The command causes spawning downstream of specified task outputs....
At INFO level, we should just log the timestamped (optionally: #3646) sequence of events in the simplest way possible, unless something goes wrong. There's too much usually-irrelevant crap in there....
For generic event handlers, the `handler events` list (in task config) is not checked for validity. We should have a list of all valid event names held in one place,...
There are some functional tests that purport to test this, but they require job runner `at`, so perhaps no one is running them at the moment. ```console $ git grep...
If `cylc clean` can't clean a remote job platform used (or attempted) by the target workflow, it should continue on and clean other job platforms, ~~and locally~~, rather than abort...
**User feature request:** If I'm in a source directory `~/cylc-src/foo` (say), `cylc install` defaults to installing a new copy of `foo` as `foo/runN`. If I'm still in `~/cylc-src/foo` could `cylc...
These changes close #4935 If `cylc clean` fails to clean a remote platform, continue on to other remote platforms but do not clean locally. @oliver-sanders - you've suggested going further...