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
It happens because the channel implementation (under the hood) has a val property which blocks until the channel value is available. But that won't happen until the script is executed, so it creates a deadlock. It probably only happens if the process has one output, with multiple outputs it might not be an issue.
We are working on some long-term language improvements that should address errors like this. For now it's just a pitfall you'll need to avoid
Bug report
Nextflow seems to hang if you pass
P.out.val
from a processP
that does not have anemit: val
directive.Expected behavior and actual behavior
I would expect an error. Instead (at least the local executor) seems to hang .
Steps to reproduce the problem
the following script
hangs indefinitely:
If you change the last line to have
PROCESS_A.out.[any-other-string]
it crashes as expected (and if you properly addemit: val
toPROCESS_A
it works).(I discovered this in a process that generates a validation set - it's not an outlandish identifier, ha)
Program output
Environment
Additional context
The text was updated successfully, but these errors were encountered: