-
Notifications
You must be signed in to change notification settings - Fork 621
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
Invalid error on missing include in nested workflow #1719
Comments
Hi, I also have this error with missing include and also when I make a mistake because of copy/pasting/deleting in the input section like such: input:
tuple path(reference) I thought I was losing my mind until I saw my mistake because I was sure I didn't use the same process twice. |
Thanks for reporting this issue. It was quite tricky but I've managed to add a much more sensible message:
|
Hey @pditommaso, I've updated nextflow to v20.10.0.5430 and I'm still getting an invalid error similar to @jeanmanguy. When I have this in my main script:
and inside the DESEQ2_DIFF module I have
You can see that the channel input structure is different than expected for the module, but I get the error:
Where I would expect an error about channel structure instead. When I change the expected inputs in DESEQ2_DIFF to
I no longer get the error, because the channel structure is compatible. |
Bug report
When a process has not been included in a nested workflow, the error message complains that the first process in the workflow has already been used, but says nothing about the missing process or import.
Expected behavior and actual behavior
Expected: An error message that
sleeper_2
has not been definedActual: Error message that the first process has already been used:
Process sleeper has been already used -- If you need to reuse the same component include it with a different name or include in a different workflow context
In my case, I had not included the required file in a many-process workflow, and it took quite some time to identify the problematic processes. Additionally, it doesn't appear the expression parsing / linking phase is blocking, and the workflow would sometimes begin executing before throwing the error.
Steps to reproduce the problem
main.nf
Program output
Environment
The text was updated successfully, but these errors were encountered: