fix: Wrap all RPC methods with rate-limit logic - #615
Open
p70436464-prog wants to merge 1 commit into
Open
Conversation
|
@p70436464-prog Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
1 participant
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.
Closes #510
Problem:
Previously, only an explicitly defined allow-list of
ASYNC_METHODS(such asgetAccount,getEvents,simulateTransaction, etc.) was wrapped with rate-limit backoff and error-handling logic insidecreateRpcServer. Any other SDK method callingSorobanRpc.Serverbypassed this logic silently.Solution:
Replaced the
ASYNC_METHODSallow-list with anEXCLUDED_METHODSblock-list (excluding only theconstructor). Now, all RPC capability functions accessed via the proxy are automatically wrapped with rate-limit resilience, backoff handling, and standardRpcServiceUnavailableErrormapping.