In reply to @oliver-sanders2:matrix.org
Interestingly I haven't seen an intercycle dependency edge the wrong way around yet.

I'm guessing there's a single interface in the code somewhere which has the pair the wrong way around. I might have messed it up with the UID work.

Fixed:
https://github.com/cylc/cylc-flow/pull/5149

it was a simple wrong way round.. However only for edges created by following the parent path (upstream), hence why you never saw intercycle dependencies the wrong way (since they are probably defined forward in time usually (always?), and the edge already exists from following the child path)

Fixed:
https://github.com/cylc/cylc-flow/pull/5149

it was a simple wrong way round.. However only for edges created by following the parent path (upstream), hence why you never saw intercycle dependencies the wrong way (since they are probably defined forward in time usually (always?), and the edge already exists from following the child (downstream) path)

Been trying to get an idea of the job for updating graphene/graphql-core ... and whether to strip it back so we can avoid graphgl-ws (and even graphql-tornado) dependency, or whether we try to support those projects ourselves..

The new graphql-core/graphene versions don't use those rx observables ... graphql-ws is quite small, and relies on these..

I didn't want to build more stuff relying on the old versions, but because of the potentially large time sink involved .. I think I'll have to build the cylc-flow graphql subscriptions based on what we are currently using .. then move on to the upgrade

The UIS stop extension:
https://github.com/cylc/cylc-uiserver/blob/da038f00a1c9d6fb6bbf5b2a156bbc4fc7b299a7/cylc/uiserver/app.py#L516-L524

Runs when stopping (keyboard interrupt) the hubless server (cylc gui), however, it isn't run when stopping the server via the hub..

From it's contents I assume it should be run with both forms of stop

Put up and issue for CLI via Hub/proxy and/or UIS:
https://github.com/cylc/cylc-flow/issues/5235

Easiest part done (making the API info available), need to create a client and config entry for http on the cylc-flow end now

Put up and issue for CLI via Hub/proxy and/or UIS:
https://github.com/cylc/cylc-flow/issues/5235

Still some peripheral work to do, but, first part done (making the API info available)..
Now need to create a client and config entry for http on the cylc-flow end now. Initially queries/mutations only, but will aim to have websockets working (which should give Oliver something to play with on the TUI front, until we have GraphQL subscriptions at the Scheduler)

Put up and issue for CLI via Hub/proxy and/or UIS:
https://github.com/cylc/cylc-flow/issues/5235

Still some peripheral work to do, but, first part done (making the API info available)..
Now need to create a client and config entry for http on the cylc-flow end. Initially queries/mutations only, but will aim to have websockets working (which should give Oliver something to play with on the TUI front, until we have GraphQL subscriptions at the Scheduler)

going via the UIS:

(uiserver) sutherlander@graphic-vbox:~$ cylc ping --debug linear
2022-12-07T21:18:59+13:00 DEBUG - Loading site/user config
    files
2022-12-07T21:18:59+13:00 DEBUG - Reading file
    /home/sutherlander/.cylc/flow/8.1.0.dev/global.cylc
2022-12-07T21:18:59+13:00 DEBUG - http:send {'command':
    'graphql', 'args': {'request_string': '\nquery ($wFlows: [ID]) {\n
    workflows(ids: $wFlows) {\n    id\n    name\n    port\n    pubPort\n
    }\n}\n', 'variables': {'wFlows': ['linear/run1']}}, 'meta': {'prog': 'ping',
    'host': 'graphic-vbox', 'comms_method': 'http'}}
2022-12-07T21:18:59+13:00 DEBUG - http:recv {'data':
    {'workflows': [{'id': '~sutherlander/linear/run1', 'name': 'linear/run1',
    'port': 43072, 'pubPort': 43070}]}}
linear/run1 running on graphic-vbox:43072 43070