Closed robsyme closed 5 months ago
Which version of Nextflow are you using? There was a bug in Nextflow about this which was fixed in 23.04.4
23.10.1
I see the same empty "published"
list behaviour on 23.04.4
as well.
This is happening because the published files are symlinked by default. In this case, on a resume the source and target are considered the "same real path" so the publish event is not sent:
For now it can be fixed by using the copy
publish mode. In the long term, I guess the publish event should still be emitted in this case, but the issue is with nextflow rather than nf-prov
Ah, gotcha. Thanks for the clarification! Will close this out for now.
If a run has to be resumed, the nf-prov plugin omits published outputs from cached tasks.
Users will likely expect that a record of data provenance would not be sensitive to run-specific details such as whether a task was executed on a previous run or not.
This can be confirmed by running a dummy pipeline:
with configuration:
On the first run, the
manifest.json
contains (with some paths truncated):but if we run again with
-resume
, the published outputs are removed: