Skip to content
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

Configuration check should not allow for duplicated "description" items #2738

Closed
lbeltrame opened this issue Apr 1, 2019 · 5 comments
Closed
Labels

Comments

@lbeltrame
Copy link
Contributor

I found out the hard way by mistakenly putting a number of samples with the same name: it caused many different files to be aligned with the same name, at least with the smallrnaseq pipeline, and of course all transaction checks screamed in my face.

@chapmanb
Copy link
Member

chapmanb commented Apr 2, 2019

Luca;
Sorry about the issues. The current YAML lint checks should identify this as an issue prior to running:

ValueError: Duplicate 'description' found in input sample configuration.
Required to be unique for a project: ['Test1']
Problem found in these samples: ['Test1', 'Test1']

Would you be able to post the problematic configuration so we can identify how it manages to get around these checks? Thanks much.

@lpantano
Copy link
Collaborator

lpantano commented Apr 2, 2019 via email

@lbeltrame
Copy link
Contributor Author

I already "fixed" it, but IIRC I had distinct samplename in the template, but identical description. Each of the duplicated description entry pointed to a different FASTA file. This caused all sorts of funny races during the run (smallrnaseq for the record).

@chapmanb
Copy link
Member

chapmanb commented Apr 3, 2019

Luca and Lorena;
Thanks for the details. We don't check currently for duplicates as part of the templating so this could definitely use some attention if we wanted to try and catch it there. Luca, I'm confused how you were able to kick off the actual run since bcbio should have complained about having duplicates. If you're able to provide an example of the configuration that caused the issues this could help in trying to isolate how best to fix beyond the templating improvements Lorena suggested.

@roryk roryk added the bug label Aug 10, 2019
@roryk
Copy link
Collaborator

roryk commented Aug 14, 2019

Hi Luca, I couldn't make this problem happen for the reasons Brad stated above-- do you have an example of the configuration that was running into this problem so I can look at it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants