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
Looking for thoughts on saving logs for all executions of a task. i.e. if a task fails and gets run again, both logs would be saved. This could be accomplished with an encoded timestamp. The benefit would be that it could be determined without checking the disk:
Looking for thoughts on saving logs for all executions of a task. i.e. if a task fails and gets run again, both logs would be saved. This could be accomplished with an encoded timestamp. The benefit would be that it could be determined without checking the disk:
Alternatively, the disk could be checked for existing logs, and auto-increment :
But, I think the second option is more confusing. Imagine you had a task named:
copy_fastq_1
, now the logs folder looks like this:The text was updated successfully, but these errors were encountered: