-
Notifications
You must be signed in to change notification settings - Fork 22
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
adding nf-core/validation #285
Conversation
|
Some of the errors are due to the meta map in the input channel bein an ImmutableMap. This means that is a map which can’t be modified in place, because this can introduce some bugs due to nextflow process being run in parallel. This can be deactivated and go back to a normal and modifiable map, but I think it’s a good opportunity to update the code to avoid possible future problems with these map operations. For example, this error points that you can't
|
OMg this is awesome! Ever since that was brought up and Rob's talk I've been super paranoid about this! It's really cool nf-validation will help us find these places where we could be borking things :D |
It is probable that we have to unable the ImmutableMaps though, the new class has some errors when using |
Tested:
|
@louperelo could you and @mirpedrol look again, if all good we can merge into |
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 :)
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.
Just found a tiny typo. Otherwise all good.
Modified the necessary files to add nf-core/validation with the help of @mirpedrol
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).