David Sutherland

> > So I think we need a JSON structure like this to preserve order: > > ```json > > [ > > { > > "key": "FOO", > >...

Have changed it to: ``` [ { "FOO": "42" }, { "BAR": "answer" } ] ``` and added outputs.

> > Any reason for the `"key"` `"value"`? > > It would make it easier to use in the Vue component. So you don't have to iterate the dict? Ok...

Fixed .. however, like the execution timeout, the string values are converted on config parse: ``` execution retry delays = PT15S, PT10M, PT1H, PT3H submission retry delays = PT2M ```...

I've "stringif"d the float lists, and the numerical types already have a `str` method to convert into appropriate list: graphql output ``` { "name": "foo", "runtime": { "environment": [ {...

Amongst other things, the latest commit fixes the incorrect displayed format: **before** ``` $ cylc broadcast linear -n FAM -s 'execution retry delays=PT35S, PT60S, PT130M' Broadcast set: + [*/FAM] execution...

hmm... > Error: Codecov: Failed to properly upload: The process '/home/runner/work/_actions/codecov/codecov-action/v3/dist/codecov' failed with exit code 255 for both "failed" tests (2nd attempt) .. the actual tests passed (and coverage) ah......

wouldn't it be the case of keeping them active so they stay in N=0?

With the example, does the 2nd flow get merged into the first flow?  It ends, after release; ``` (flow) sutherlander@cortex:cylc-flow$ cylc release --flow=2 fhold/run1//1/b Done ``` (confirmed working) ```...

I'm annoyed I didn't review this one earlier.. A welcome feature for NIWA Ops. (have cheekily added this to the 8.4.0 milestone)