This repository has been archived by the owner on Oct 19, 2024. It is now read-only.
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.
…ng in errors.
json example:
"{"jsonrpc":"2.0","id":268,"result":null,"error":{"code":-32000,"message":"tracing failed: fee cap less than block base fee: address 0x4a4BA8a759e7217a1ff38749Aa6E73564C1D8a01, gasFeeCap: 11470668621 baseFee: 11484931392"}}"
If the json response contains both result and errors, it's better to return errors instead of "response must be a success/error or notification object"
Also, after returning "de::Error::custom", in
An error should be returned instead of just printing the error, which would cause the request to wait indefinitely.
PR Checklist
[x ] Added Tests
[x ] Added Documentation
[x ] Breaking changes