Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using
n
equal to the maximum requests/second (NCBI: 3 downloads/sec regularly, 10 with API KEY), we seem to get several failures per run that are resolved by retries -- best if retries is 3 or greater. I can only think that maybe we're retrying in the same second and exceeding the maximum requests?Here I've added a 1 second delay before retrying. An alternative (or in addition?) would be to add a fraction of a second delay in the main loop, which would stagger the initial requests? I'm honestly not sure how much that would help, as the failures are not generally at the beginning of the run, but rather spread across it randomly (and not always the same files).