Some Protocols execute tools that emit log information to either STDOUT, STDERR, or both. The information in these streams can be critical for users to understand where their Tasks are going wrong in case of persistent failure.
We should capture these streams when compute services execute ProtocolDAGs, then preserve them as additional artifacts when submitting completed or failed ProtocolDAGResults back to the server. These log artifacts can be stored in the object store, with references in the state store.
We can then expose these artifacts via additional AlchemiscaleClient methods, such as:
get_task_stdout(task_sk) : return all stdout outputs from all ProtocolDAGResults associated with the given Task
get_task_stderr(task_sk) : return all stderr outputs from all ProtocolDAGResults associated with the given Task
dotsdl
commented
3 weeks ago
Some
Protocols execute tools that emit log information to either STDOUT, STDERR, or both. The information in these streams can be critical for users to understand where theirTasks are going wrong in case of persistent failure.We should capture these streams when compute services execute
ProtocolDAGs, then preserve them as additional artifacts when submitting completed or failedProtocolDAGResults back to the server. These log artifacts can be stored in the object store, with references in the state store.We can then expose these artifacts via additional
AlchemiscaleClientmethods, such as:get_task_stdout(task_sk): return all stdout outputs from allProtocolDAGResults associated with the givenTaskget_task_stderr(task_sk): return all stderr outputs from allProtocolDAGResults associated with the givenTask