-
Notifications
You must be signed in to change notification settings - Fork 664
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
join doesn't match the same keys #3939
Comments
FWIW: I've noticed this behavior too using nextflow version 22.10.8 and have noticed that it happens sporadically. I've attempted to create a minimal reproducible example but have not succeeded in reproducing the behavior in a simple example nextflow script. |
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. |
For me what closed this is that one of the tuples was a nextflow.taskpath variable while the other was a java.string. What caused this is I had an upstream process where the tuple key was the same as its path: output: So I think it's worth trying to look if they are the same type of tuple with def classOfElements = YOURPROCESS_HERE.out.collect { list ->
|
@sbthandras are you saying the path element in that output tuple was a TaskPath? I wouldn't expect that based on how the task processor works, but if true it should probably be unwrapped under the hood |
Bug report
Expected behavior and actual behavior
Sometimes join function fails matching entries with same key values. Tricky bit is that this happens most of the time but not always.
Steps to reproduce the problem
You can checkout this commit and run the test command:
nextflow run main.nf -profile test,tools_mutect2_ms,docker
Program output
Complete log file: nextflow-join-bug.log
Error message:
Environment
GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
The text was updated successfully, but these errors were encountered: