Skip to content

Conversation

bentsherman
Copy link
Member

Close #5785

This PR fixes a false positive error with storeDir that causes it to be overly strict with value outputs.

Currently storeDir only works with value outputs of the form val(<name>), where <name> is defined as an input or in the script block. However, any value output should be allowed, because value outputs are always evaluated and do not depend on the storeDir or resume cache.

Test case:

process FOO {
    storeDir 'store'

    output:
    tuple val(task.process), val('grep'), path('version.txt')

    script:
    """
    grep --version | head -n 1 > version.txt
    """
}

workflow {
    FOO()
}

Currently, the two value outputs above will caused the task to not be stored. With this PR, the task is stored correctly.

@bentsherman bentsherman requested a review from jorgee September 16, 2025 14:39
Copy link

netlify bot commented Sep 16, 2025

Deploy Preview for nextflow-docs-staging canceled.

Name Link
🔨 Latest commit a349d53
🔍 Latest deploy log https://app.netlify.com/projects/nextflow-docs-staging/deploys/68c9769825e12000084fea59

@jorgee
Copy link
Contributor

jorgee commented Sep 17, 2025

It would be good to add the test case as integration test

@bentsherman
Copy link
Member Author

TODO: update dynamic-storedir.nf to include this case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

topic channel output breaks storeDir
2 participants