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
Is your feature request related to a problem? Please describe.
Currently logs (STDOUT/STDERR) of cwl-tes are parsed only after job completion, causing TES task IDs to be inaccessible until after a run completed. This has several severe disadvantages, such as:
User are unable to track the progress of individual tasks; the task_log array field in the run_log object remains empty
Ignorance of task IDs can lead to "zombie" runs that stay indefinitely in incomplete states, such as UNKNOWN or RUNNING
Cancelling a workflow run cannot be propagated to the task level, leading to a waste of resources
Describe the solution you'd like
Parse cwl-tes run logs in real-time, publish task state changes to the broker and handle them in the event listener/manager.
Describe alternatives you've considered
Parsing logs and polling TES status changes (as done by cwl-tes) are temporary solutions only. See #57 and #58 for more viable solutions with regard to polling and log parsing, respectively.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently logs (STDOUT/STDERR) of
cwl-tes
are parsed only after job completion, causing TES task IDs to be inaccessible until after a run completed. This has several severe disadvantages, such as:task_log
array field in therun_log
object remains emptyUNKNOWN
orRUNNING
Describe the solution you'd like
Parse
cwl-tes
run logs in real-time, publish task state changes to the broker and handle them in the event listener/manager.Describe alternatives you've considered
Parsing logs and polling TES status changes (as done by
cwl-tes
) are temporary solutions only. See #57 and #58 for more viable solutions with regard to polling and log parsing, respectively.Additional context
N/A
The text was updated successfully, but these errors were encountered: