Use unbuffered transport for the Debug RPC API #3285
Merged
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
MartinquaXD
reviewed
Feb 20, 2025
MartinquaXD
approved these changes
Feb 20, 2025
m-lord-renkse
approved these changes
Feb 21, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Since Alchemy is used as one of the failover providers and it doesn't support buffered debug RPC API, it is important to use unbuffered transport when sending
debug_traceTransactioncalls. Otherwise, this leads to failed RPC calls.Changes
The easiest workaround is to use 2 separate transports for different purposes. The current approach is not really flexible since it is not configurable, but in order to keep it simple, this should be acceptable.