[general] (bug or feature?) tar_skip on parallel with retrieval = "worker" #180
Closed
CorradoLanera
started this conversation in
General
Replies: 1 comment
-
This is a consequence of how cancellation works. If you look at > cat(tar_manifest(x)$command)
{
targets::tar_cancel(TRUE)
1
}
> cat(tar_manifest(y)$command)
{
targets::tar_cancel(TRUE)
x + 1
} In other words, cancellation happens only after the target starts running. By contrast, the target loads dependencies before it runs, i.e. before cancellation has a chance to happen. If there is no existing value to load for the dependency, an error is thrown. To make sure a dependency value is always available to load, you can set |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Help
Description
If with parallel crew computing we set
retrieval = "worker"
option,tar_skip
signals an error if its parent was skipped as well (even if no dependencies are needed to evaluate the condition)reprex (and expected behavior)
Created on 2024-07-04 with reprex v2.1.0
Session info
Beta Was this translation helpful? Give feedback.
All reactions