David Sutherland

Ping @syrusakbary (might be busy with [wasmerio](https://github.com/wasmerio) I suppose..)

@jkimbo - I know you haven't been involved with this one.. But no maintainers appear active here... Do you know what's happening with this project? it seems to be stagnant.....

> Did you mean to remove `cylc/flow/data_messages_pb2.py` ? It's not removed (nothing would work otherwise), I used the corresponding `protoc`: ``` $ protoc --version libprotoc 3.19.4 ``` It's just massively...

This will need to be rebased once #4901 goes in (or visa versa) (and protobuf module regenerated)

Investigating.. it appears the job still gets it: ``` { "name": "foo", "runtime": { "environment": {} }, "jobs": [ { "runtime": { "platform": "localhost", "script": "sleep 60", "initScript": "", "envScript":...

Ok I've fixed the problem.. I was using `get()` with ordered default dict, I changed to that as a workaround for some tests (so they might fail, and I'll just...

> Getting a KeyError on `tests/functional/retries/01-submission-retry.t` Sorted now.. It's because some submission failures happen before full job construction. (this is why I had changed it before, causing the field deletion...

> Some implementations of JSON writers/parsers might decide to preserve order, but it's completely chance if they do. So even if the Python json library writes them in order, the...

I suspect the python side is ordered according to the dict (`json` has a `sort_keys` option but we don't and shouldn't use it in this case), because the graphql tests...

> Just because we push them out in order doesn't mean they'll be read back in order, or preserve their order when operated on by JS. Yeah, but, before I...