fix(web3): try next web3 node on response error#1998
Merged
Conversation
laruh
suggested changes
Oct 26, 2023
laruh
left a comment
There was a problem hiding this comment.
Thanks for the fixes!
I have one note and question.
Note:
Your changes are well structured and look good to me. I just noticed that we have redundant cloning in previously merged code part.
Unnecessary clones for serialized_request, we can remove it.
// here in non wasm target
let mut req = http::Request::new(serialized_request.clone().into_bytes());
// and here in `send_request` wasm impl
match send_request_once(serialized_request.clone(), &node.uri
8 tasks
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
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.
No description provided.