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
In #623, @tclose added a function that modifies its input as a reliable reproducer of a task whose input hash changes after execution, resulting in a deadlocked workflow as the task is complete but its results are no longer findable in the cache directory.
In a comment I proposed an addition to the pydra.mark module:
If someone has an unsafe function, they're going to need to either rewrite or wrap it themselves, or we can provide a standard tool with straightforward semantics:
In #623 you mentioned a check at the end of the task to see whether the task has altered its input hash. I think this is a good idea. Should that be included in this issue or in a separate one?
In #623, @tclose added a function that modifies its input as a reliable reproducer of a task whose input hash changes after execution, resulting in a deadlocked workflow as the task is complete but its results are no longer findable in the cache directory.
In a comment I proposed an addition to the
pydra.mark
module:If someone has an unsafe function, they're going to need to either rewrite or wrap it themselves, or we can provide a standard tool with straightforward semantics:
So we could write:
And if somebody has control over the function but is lazy or (more charitably) finds an explicit copy cluttering, they could write:
The text was updated successfully, but these errors were encountered: