CLI trigger does not check for existance of task being triggered

Cylc Cylc Support
1

Hi there, CLI triggering is very useful for debugging but we noticed that if the name of the task being triggered is misspelled, the command returns “command queued”, and the only clue that something is wrong is that it does not appear in tui.
It would be nice to have immediate feedback.
Ta,
Gaby

PS:
We do get an error message when // is missing, as in:

[turekg@fidjim05-sihpc: glo12_cylc] cylc trigger glo12_cylc/20241111/tecup_tair
InputError: IDs must be tasksg
2

Hi,

The typo will get spotted, it will be logged in the scheduler log (log/scheduler/log), however, at present, we are unable to return errors of this type to the client (i.e. the CLI).

The reason for this is that Cylc commands are asynchronous. I.E, when commands are received by the scheduler, they get stuck in a queue, the scheduler will process them when it gets the chance to. The client (i.e. the CLI) does not wait around for this to happen (otherwise the command could hang indefinitely) so can only report that the command has been queued, not the outcome of the operation.

This is the same for other Cylc commands. We have some ideas about improving this situation:

  • At 8.5.0 log warnings will be clearly reported in the GUI via a warning icon (not so helpful for CLI work). I’ll see if there’s an easy way to extend this to Tui.
  • In the future, we plan to develop a subscription pattern, where the CLI can track the command it issued and receive further updates from it after it was queued (no time estimate for this).
3

Thanx for the reply, all very informative