[r3.4] rpc: fix null result unmarshalling in CallContext (#20393)#20521
Merged
Conversation
Cherry-pick of #20393 from main.
Giulio2002
approved these changes
Apr 13, 2026
Giulio2002
left a comment
Contributor
There was a problem hiding this comment.
LGTM — obvious nil-result unmarshalling fix with focused regression tests.
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
2 participants
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.
Cherry-pick of #20393 from main.
Fixes double indirection on interface{} preventing correct unmarshalling of JSON null responses. Mirrors go-ethereum PR #26723.