-
Notifications
You must be signed in to change notification settings - Fork 0
RPC Resolver: Healthcheck always on #78
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
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
PASS [ 44.721s] (3/3) lit_node::test toxiproxy::perf_tests::load_with_no_latency |
GTC6244
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. Have a question around why you re-added the deprecated value, but will approve anyway so you can merge without needing a re-review! ;-)
d212de3 to
4dcf20f
Compare
4dcf20f to
e86173e
Compare

What
This PR marks the
rpc_healthcheck_enabledflag as deprecated and removes its functionality from the RPC health check polling logic.Cleanup of this flag from the config will happen in a later PR
Why
The RPC health check functionality should always be enabled, making the toggle unnecessary. Removing the conditional check simplifies the code.
Risks