Aborted downloads make future prophane executions impossible
Expected Behavior
Prophane should offer an easy way to unlock the download directory.
Current Behavior
Users have to execute snakemake -s {prophane_executeable_dir}/Snakefile_db_setup.smk --configfile {prophane_database_dir}/db_setup_config.yaml --unlock
, which requires highly specific snakemake knowledge and can therefore not be expected. When passing --unlock
to prophane run (or prepare-dbs), only the job-directory is unlocked and not the database directory.
Error message:
Error: Directory cannot be locked. Please make sure that no other Snakemake process is trying to create the same files in the following directory:
/path_to/prophane_dbs
If you are sure that no other instances of snakemake are running on this directory, the remaining lock was likely caused by a kill signal or a power loss. It can be removed with the --unlock argument.
Possible Solution
Add option to CLI for unlocking db-dir.
Steps to Reproduce
- Start a job requiring a db that is not downloaded yet
- abort the job while the download is running
- Start the job again -> error.