-
Notifications
You must be signed in to change notification settings - Fork 34
Update abricate to fix inconsistent report contents #479
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
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. Please update the changelog before merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh wait I take that back – some tests fail due to the abricate update – file name clash because of the naming check within the module. I should have asked that before you merged the abricate update, but why don't we only symlink if the file name is different than the sample name, otherwise do nothing? Right now after the if ("${assembly}" == "${prefix}.fasta") an error is triggered.
|
Yeah I realised that behaviour would also break our desired behaviour (having to add a prefix) 😓 Suggestion here to only symlink when not the same: nf-core/modules#8555 |
|
I think that's working now @jasmezz |
|
Re-running CI checks once more: There is actually one pipeline-level nf-test snapshot that was affected by the update of abricate results. (The others not because they use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now. All tests passing except for 2 no-space-left-on-device errors (will probably be solved automatically once antismash update is in). But please update the changelog before merge!
|
Than kyou @jasmezz ! |
This ensures the sample IDs in the abricate run header matches our sample IDs, rather than the file name (which can be something different if no gunzipping has been performed on it)
PR checklist
nf-core pipelines lint).nextflow run . -profile test,docker --outdir <OUTDIR>).nextflow run . -profile debug,test,docker --outdir <OUTDIR>).docs/usage.mdis updated.docs/output.mdis updated.CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).