You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could catch your retro example, but the general solution gets tricky because the message side of the mapping can accept patterns e.g:
[runtime]
[[task]]
[[[outputs]]]
x = foo .*
y = .* bar
Beyond exhaustively checking whether there is some message that could satisfy both it would be hard to defend against this.
Although it wasn't the intended usage, it could kinda be argued that it's valid for a single message to map onto multiple outputs e.g something like:
script = """ cylc message -- data x, y, z written"""[[[outputs]]]
x = data .*x.* written
y = data .*y.* written
z = data .*z.* written
Surprisingly, there don't presently appear to be any uses of custom outputs at our site, so no pre-existing use cases to constrain us. Could go either way.
While testing #6046 I noticed we can assign the same output message to different triggers:
This ⏫ does the right thing and completes both outputs, but I'm pretty sure it would be a mistake if found in the wild.
You might want to add the fix into #6046 @oliver-sanders ?
The text was updated successfully, but these errors were encountered: