-
Notifications
You must be signed in to change notification settings - Fork 421
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
Bug introduced in 3.4.1
causes premature stop of the pipeline
#1622
Comments
I have same issue, too! |
Try reverting to Nextflow v24.04.4. It can be done like this:
The problem seems to first have appeared with NF 24.07.0-edge. |
Thanks so much to all!! Reverting the version doing : NXF_VER=24.04.4 nextflow run … Seems to work fine (at least the pipeline as started!) Thanks again to all, David |
It seems that the problem is about to be solved by this PR :-) |
Convert bcf_annotations.tbi from empty() to value channel to prevent stalling. nf-core#1622
Thank you, @asp8200 .... I've been trying to fix this for days.... and it was great to find your recommendation here...
did the trick. thanks |
@maxulysse : This issue also popped up when I tried to run
with NF v21.10.1. |
yes this works also for me |
Description of the bug
The pipeline prematurely stops with the error:
Missing process or function Channel.empty([[]])
The log file says:
Caused by: groovy.lang.MissingMethodException: No signature of method: java.lang.Object.Channel.empty() is applicable for argument types: (ArrayList) values: [[]]
It's hard to debug where it comes from but I confirm it was introduced in bfec02f
When I run the pipeline with the sha before than that it works fine.
Command used and terminal output
Relevant files
No response
System information
Nextflow version 24.07.0-edge
Ubuntu Server 22.04
local executor
Docker
The text was updated successfully, but these errors were encountered: