David Sutherland

> Note, I don't know whether protobuf validates messages at the receiver end, if so we may need to use a new field to avoid conflict issues. I think it...

> Note, the Cylc 7 spawning behaviour can be achieved by adding submit dependencies between the parentless tasks e.g: > > ``` > @up => a > a[-PT1M]:submitted => a...

Restart/reload and remove are now handled.. Remove will cause the next occurrence to spawn, the argument being: - the non-sequential case would be spawned, so be consistent. - otherwise the...

I assume the docs are auto-generated from the config definition.. but I suppose I should build it with this branch to find out.

Think I've made the suggested changes .. however not sure why fast tests are failing

> > However there are a few functional test failures here > > Looks like it was the `ValueError` vs `KeyError` thing. Functional tests passing now 👍 Yeah, I had...

I'll add more tests. (note: any test with clocktriggers will now test this behavior implicitly (in w/e ways it does))

I've found some holes in the spawning of parentless tasks with unsatisfied sequential xtriggers (via Oliver's integration test, and replicated manually).. should be easy fix

Added the integration tests (thanks Oliver), and have gotten the existing scenarios/tests working after adding more spawning conditions and requirements. Will add more scenarios next.

hmm... all the TUI tests are failing...