[BugFix] openbb-fred: Fix 429 Error From FRED API & Implement Global Rate Limiter For Provider #7527
Merged
Merged
Conversation
DidierRLopes
approved these changes
Jun 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes HTTP 429 errors generated by the
openbb-fredendpoints from hitting more than two requests per second. FRED has changed the calculation for their rate limiting so that isper second, instead ofper minute. While the Fetchers fit into the 120/minute bucket, the new calculus engaged rate limits on most endpoints. The PR resolves the issue by implementing a global rate limiter and LRU cache to ensure the per-second limits are adhered to and that multiple requests for the same data do not generate new network calls.Current symptoms will be partial, incomplete, or empty data.
Before:

After:

Additional notes:
The newest version of
aiohttpbreaksvcrpy- kevin1024/vcrpy#996 - so the version has been temporarily pinned in thedevtoolsdefinition so thatdev_install.pyinstalls the right version for the CI tests.