This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
RPC: Improve error messages for decoding errors #28530
Merged
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.
Problem
Error messages for decoding failures in RPC responses aren't very clear. For example, an invalid base64 encoded message passed to
getFeeForMessage
could return "InvalidLength" as an error message and it's not clear that this is related to invalid base64 encoding or some other invalid length in deserialization or message sanitization.Summary of Changes
Fixes #