-
Help
DescriptionHi! I'm getting the error
from a target that dynamically branches over a list of input files, and splits it up into a possibly varying number of output files depending on the exact input file content. I've tried to reproduce the error in a minimal example, but I have not been succesful (i.e. the minimal example runs as expected), and I hypothesize that the problem is something a bit trivial on my side. Unfortunately, there is no workspace or traceback generated for the target branches for some reason, so it makes it a bit hard to debug - so if anyone has some intuition based on the specific error message, it would be greatly appreciated! This is what the (subsetted) output of tar_meta() looks like for each of the 10 failed input file/dynamic branches. and this is what the reporter-output looks like: Below is a simplified example analogous to capture the overall structure in the problematic part of my pipeline. Here, I have removed two outer tar_map layers (which is the test.muscle. parts of the original erroring branch names, using the dot as delimiter), to perhaps aid your intuition in what might be going wrong.
As you can see from running tar_read(replicate_of_erroring_target) below, this minimal example outputs exactly what I aim to get in my real pipeline. Any suggestions on how to continue debugging this error is also greatly appreciated. Finally, here is the sessionInfo extracted from the SLURM-controller worker output:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Hard to say, but you can get tracebacks with workspaces: https://books.ropensci.org/targets/debugging.html#workspaces Probably unrelated, but tar_target(directories, c("dir1", "dir2", "dir3")),
tar_target(
input_file_paths,
{
fs::dir_create(directories) # does not fail if the directory already exists
writeLines("abc", file.path(directories, "input_file.txt"))
file.path(directories, "input_file.txt")
},
pattern = map(directories)
) |
Beta Was this translation helpful? Give feedback.
Hmm - rolling back from the development version 1.9.1.9000 to 1.9.1 seems to have done the trick. Maybe it was a bit reckless to go straight for the development version when updating the package! Thanks for your help again!