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
{{ message }}
Repository navigation
Pipeline uses cached process despite edited eval script #5470
Despite editing an eval script, a cached version of the process will be used under certain circumstances
Expected behavior and actual behavior
Expected: editing an eval script (e.g. from multiqc --version to multiqc --version | sed "s/version//" ) will be picked up as an edit and therefore a cached version won't be used.
Actual behaviour: it works correctly if resume = true is stated within the main workflow script. However if -resume is provided on command line, or resume = true is given in nextflow.config, then the cached version is used after a change to the eval script
Steps to reproduce the problem
Generate nextflow.config and main.nf from below example
Run the pipeline
Edit the eval statement to 'multiqc --version | sed "s/version//"'
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.
Activity
bentsherman commentedon Nov 5, 2024
Good point, the eval script was never added to the task hash
bentsherman commentedon Nov 14, 2024
@jorgee this one should be pretty easy if you'd like to try. Basically we need to add the eval outputs to the task hash here:
nextflow/modules/nextflow/src/main/groovy/nextflow/processor/TaskProcessor.groovy
Lines 2200 to 2205 in 8041a57
Something like this:
stale commentedon Apr 26, 2025
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.
BREAKING CHANGE: Improve eval output hash with semantic names instead…
BREAKING CHANGE: Improve eval output hash with semantic names instead…
BREAKING CHANGE: Improve eval output hash with semantic names instead…