You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and when I use the -n flag to do a dry run of the pipeline I get WorkflowError: Cannot parse runtime value into minutes for setting runtime resource: <TBD>. It makes sense that it wouldn't be able to calculate resource requirements without any inputs but it would be nice to be able to use -n in tandem with this way of defining resources.
Is this something you'd consider changing the behavior of (e.g. allow the resource spec to take a value like TBD for dryruns only) or is it something where I should just wrap the resource function with something to catch this and provide a default?
The text was updated successfully, but these errors were encountered:
### Description
This fixes the `WorkflowError`s that occur when the resource parsing
code tries to parse `TBDString`s during a dry run.
This should fix#2575 and
fix#2555.
### QC
* [x] The PR contains a test case for the changes or the changes are
already covered by an existing test case.
* [x] The documentation (`docs/`) is updated to reflect the changes or
this is not necessary (e.g. if the change does neither modify the
language nor the behavior or functionalities of Snakemake).
Co-authored-by: Johannes Köster <johannes.koester@tu-dortmund.de>
Snakemake version
8.0.1
Describe the bug
This is probably considered in the gray area between a bug and a feature but I have rules with resource specifications defined like this:
and when I use the
-n
flag to do a dry run of the pipeline I getWorkflowError: Cannot parse runtime value into minutes for setting runtime resource: <TBD>
. It makes sense that it wouldn't be able to calculate resource requirements without any inputs but it would be nice to be able to use-n
in tandem with this way of defining resources.Is this something you'd consider changing the behavior of (e.g. allow the resource spec to take a value like
TBD
for dryruns only) or is it something where I should just wrap the resource function with something to catch this and provide a default?The text was updated successfully, but these errors were encountered: