Fix broken Semantic Scholar API #105
Open
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.
Description
Closes #104
This PR addresses the broken Semantic Scholar API link and improves the handling of unauthenticated requests to mitigate
429 Too Many Requestserrors.Changes
urllib3to handle transient failures (3 retries, 1s backoff).Context & Results
The current global rate limit for unauthenticated requests is 1000 requests per second. Since this is a shared global limit, requests are often rejected with 429s.
I tested this locally:
Recommendation
For consistent reliability, it is highly recommended to use an API key for authenticated requests (1 req/s) rather than relying on the unauthenticated global pool.
Discussion
I am open to suggestions regarding the retry configuration if others find more optimal settings.