-
Notifications
You must be signed in to change notification settings - Fork 6
Network resiliency #197
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
Network resiliency #197
Conversation
|
|
(the linting is complaining about the changelog, but it's a line that will change anyway once we have the release name) |
|
Oo, one of my favourites is Scyther! |
DLBPointon
left a comment
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
Beyond the name change, everything else looks good.
|
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.2.1. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
Closes #196
A mixed bag pull-request. My first motivation was to put in a fix for #196. The script
bin/generate_config.pyalready had some code to cope with network errors (wait and retry) but it was only 1 API call. I've now put this into a function and made all API calls use it.Then, since we need to a release, I've started the process of bumping the version number up, updating the changelog, etc.
@DLBPointon : do you have a Pokemon name to suggest ? :)
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).