-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove toList() channel operation from inside onComplete block #3304
base: dev
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this fix 🙂 The nf-core subworkflow should be fixed in the modules repo and then updated here, otherwise the changes look good
nf_core/pipeline-template/subworkflows/nf-core/utils_nfcore_pipeline/main.nf
Outdated
Show resolved
Hide resolved
nf_core/pipeline-template/subworkflows/local/utils_nfcore_pipeline_pipeline/main.nf
Outdated
Show resolved
Hide resolved
9f74724
to
e1f07d5
Compare
This PR resolves an important bug in the nf-core template, whereby all workflows will hang if the --email parameter is supplied. The onComplete block will hang if there are any (queue) channel operations inside the block. All values in the onComplete block must be resolved to single values or value channels _before_ the onComplete block starts. The async channels are not available inside onComplete, so calling the toList() operation will hang forever as the async queue channel will never be completed.
e1f07d5
to
abb0fa2
Compare
Needs nf-core/modules#7129 |
…annel-operations-from-oncomplete
Maybe we can drop the changes to nf_core/pipeline-template/subworkflows/nf-core/utils_nfcore_pipeline/main.nf to keep this PR focused. |
…s_nfcore_pipeline/main.nf
I thought both changes were tied together. But we can also update the subworkflow on a different PR 👍 |
This PR resolves an important bug in the nf-core template, whereby all workflows will hang if the --email parameter is supplied.
The onComplete block will hang if there are any (queue) channel operations inside the block. All values in the onComplete block must be resolved to single values or value channels before the onComplete block starts.
The async channels are not available inside onComplete, so calling the toList() operation will hang forever as the async queue channel will never be completed.
PR checklist
CHANGELOG.md
is updateddocs
is updated