Open YuxinShi0423 opened 1 year ago
Resume is expected to be true
, last
or the UUID of the prev execution e.g. 0e13f630-30f3-43e2-9306-fe8c88dfd791
.
The run name is not expected to be used for the resume.
Thanks! But then I think this article needs to be updated: https://www.nextflow.io/blog/2019/demystifying-nextflow-resume.html
You can use the resume command with either the session ID or the run name to recover a specific execution. For example:
$ nextflow run rnaseq-nf -resume mighty_boyd
Just came up against this issue as well. I've been using run names with -resume
myself for the entire time I've used Nextflow, and have told many hundreds of people to do the same 😆
Just had a quick play and run names seem to work fine up until at least version 22.10.1
. But they don't work with 22.10.6
.
Tagging @mribeirodantas, @bentsherman and @robsyme who were also involved in a thread about this on Slack just now. @robsyme even said he'd look into it 😉
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Still would like this please.
Bug report
When using
-resume
with run name as listed in .history file, it always use the latest session id instead.Expected behavior and actual behavior
Expecting the run name to be used when looking for the session to be resumed.
Steps to reproduce the problem
(See the history file attached below)
Program output
Example history file:
Environment
$SHELL --version
) zsh 5.8.1 (x86_64-apple-darwin21.0)Additional context
Might be related to https://github.com/nextflow-io/nextflow/blob/ff6afcbdc127700f89090205fede28322135ef56/modules/nextflow/src/main/groovy/nextflow/cli/Launcher.groovy#L215-L222 when parsing the resume arguments.