Tim Pillinger

> * The "job #" box says "1 of 0" whereas it would say "1 of 1" for tasks run in "live" or "simulation" mode. > > * This maybe...

> I had configured the tasks to run in skip-mode and to generate the failed output using a broadcast. I then made another broadcast to change the skip-mode outputs and...

Poking @MetRonnie because Oliver Hath Approved!

> Latest commit seems to include some kind of squashed merge of master into this branch? Yes - I made the history horrible, and I think this is the best...

@MetRonnie & @oliver-sanders have a look at https://github.com/cylc/cylc-flow/pull/6039/commits/bc8d067b24f08770aaaf94eb0c420cd0c9e88fa5. I'm not convinced it's a good idea, but if you think it might be I'll add tests. But IMO mission creep.

> Getting a warning when setting the `skip` output on a task (that does not have any custom outputs defined) Fixed in https://github.com/cylc/cylc-flow/pull/6039/commits/8136da67a96538e79653852ceb3c8c1eff7c5638

Replicated.

> I think this diff means that polled log messages for task failure will go back to being duplicated. I think that you have a particular closed issue in mind,...

This does not apply to submit failure, because submit failure will always log a critical warning through the `jobs-submit` command. ``` WARNING - platform: mulberry - Could not connect to...

@oliver-sanders & @MetRonnie : Sorry, but I made a total hash of rebasing this and may have introduced some regressions. :( I _think_ that I've been through all your comments,...