Fix B28: Retry on RPC failures instead of panicking #135
+504
−10
Conversation
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
3 participants
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.
#100 the node was crashing whenever the RPC call to get the leader for a slot failed.
this could happen due to network hiccups or temporary RPC provider issues.
added exponential backoff retry logic (10 attempts, max 4.5s) that only panics
if all retries fail. This way we tolerate transient failures while still
maintaining validation integrity.
also refactored to use an interface for the RPC client, which makes testing
easier. Added unit tests with mocks and integration tests to verify the
retry behavior works correctly.