Broadcast: GraphQLLocatedError 'DurationFloat' object has no attribute 'startswith'

[ColemanTom]

Description

When broadcasting to set the execution time limit I'm seeing the error ERROR: [{'error': {'message': "'DurationFloat' object has no attribute 'startswith'", 'traceback': ["graphql.error.located_error.GraphQLLocatedError: 'DurationFloat' object has no attribute 'startswith'\n"]}}]. This may be related to #6333 and #6222
This happens if you have two or more namespaces and are using a ISO duration item.

Reproducible Example

$ cylc broadcast -s 'execution time limit=PT1M' -n root -n root access_g4_rewind
ERROR: [{'error': {'message': "'DurationFloat' object has no attribute 'startswith'", 'traceback': ["graphql.error.located_error.GraphQLLocatedError: 'DurationFloat' object has no attribute 'startswith'\n"]}}]

The namespaces can be the same, it doesn't matter. If you have one namespace, there are no issues, 2+ it fails.

Expected Behaviour

No failure

[oliver-sanders]

@ColemanTom, the issue here appears to be the duplicate -n root option. When I remove this, the command succeeds:

$ cylc broadcast -s 'execution time limit=PT1M' -n root -n root generic         
ERROR: [{'error': {'message': "'DurationFloat' object has no attribute 'startswith'", 'traceback': ["graphql.error.located_error.GraphQLLocatedError: 'DurationFloat' object has no attribute 'startswith'\n"]}}]
$ cylc broadcast -s 'execution time limit=PT1M' -n root generic
Broadcast set:
+ [*/root] execution time limit=PT1M

[ColemanTom]

The duplicate is for demonstration. You can do any combination of things, just 2+ namespaces setting at least execution time limit, causes this failure.

[oliver-sanders]

Should be fixed by #6335. If you are able to test this it would help us get it in sooner.

[ColemanTom]

As I said, the root duplication was me demonstrating without knowing any namespaces. Here is a simple example.

$ cat flow.cylc
[scheduling]
    initial cycle point = 21200101T0000Z
    final cycle point = 21200101T0000Z
    [[graph]]
        PT6H = """
                @wall_clock => start & end
        """
[runtime]
    [[start,end]]
        script = true

$ cylc broadcast -s 'execution time limit=PT9M' -n start -n end basic
ERROR: [{'error': {'message': "'DurationFloat' object has no attribute 'startswith'", 'traceback': ["graphql.error.located_error.GraphQLLocatedError: 'DurationFloat' object has no attribute 'startswith'\n"]}}]

It is nothing to do with duplicate namespaces. Cylc (or something) must be resolving the PT9M to be a DurationFloat, which breaks GraphQL.

[ColemanTom]

I have run with your change, and same error by the way.

[oliver-sanders]

I have run with your change, and same error by the way.

I tried with your example above. Could you post some details of how you reproduced this on the PR so I can investigate, thanks.

Note, you will need to restart your workflows with the patched version because it's a server-side fix not a client-side one.

[ColemanTom]

Ah, I missed updating broadcast.py yesterday. I had only updated broadcast_mgr.py. With your new broadcast.py in there too, the error has disappeared, whether the namespaces mentioned are duplicate or not.

$ CYLC_VERSION=8.3.3 cylc broadcast -s 'execution time limit=PT9M' -n start -n end basic
Broadcast set:
+ [*/end] execution time limit=PT9M
+ [*/start] execution time limit=PT9M
$ CYLC_VERSION=8.3.3 cylc broadcast -s 'execution time limit=PT9M' -n start -n start basic
Broadcast set:
+ [*/start] execution time limit=PT9M

So, this looks like it can be closed when #6335 is merged in.

[oliver-sanders]

Thanks for confirming.

[oliver-sanders]

Closed by #6335 (Cylc 8.3.4)