Fix #481: add retry logic to pubchem fetching function #1113
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.
The nightly test runs would often fail at least one test that fetched data from a Pubchem network service. The failures happened because sometimes the remote server would respond with an error (probably because it's getting hit with too many requests). The problem was reported years ago in issue #481.
This PR should address this problem. I added a simple retry mechanism to the function
geometry_from_pubchem()
in the filesrc/openfermion/chem/pubchem.py
. It now catches exceptions and retries the network call up to three times with a delay between each attempt. I also updated the corresponding tests insrc/openfermion/chem/pubchem_test.py
to mock the network calls and verify the new retry logic.