feat: ✨ programmatically track provider errors in cache #1016
+136
−3
Conversation
This file contains 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
This change is meant to lay the skeleton for dynamically determining which order to rank providers for a given chain. This first PR is aimed at adding a key in the cache when errors occur. An exponential decay is used to store a count of the errors incurred by a given provider
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 change is meant to lay the groundwork for dynamically determining which order to rank providers for a given chain.
This first PR aims to add a key to the cache when an error occurs in a provider. This error count will be maintained using an exponential decay to maintain an average number of occurrences of an error per day. This error count can be used to rank providers