-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add RPCProvider unique ID to HealthChecker chain statuses #6266
Labels
Comments
friofry
added a commit
that referenced
this issue
Feb 25, 2025
… rps_limited_eth_client.go fixes #6266
friofry
added a commit
that referenced
this issue
Feb 25, 2025
* do not use circuit breaker if the circuit name is empty fixes #6266
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As @dlipicar suggested, it would be good to have a link between HealthChecker statuses and RPCProviders we store in networks.
HealthChecker aggregates RPC client states per chain and per provider. Currently, it stores a map of provider statuses with a circuitName key, which is not convenient for mapping status to actual RPC providers.
Ideally, the RPCProvider should have a unique ID. Currently it's Name + ChainID
The text was updated successfully, but these errors were encountered: