Fix null pointer exception in getNodeError check for ExecutionRevertedError #2769
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.
Overview
This PR fix null pointer exception in getNodeError check for ExecutionRevertedError
Detailed summary
When using viem client with custom provider, i faced null pointer exception because the error walk check for ExecutionRevertedError in getNodeError didn't check for null cause in error returned from provider.
This PR added null check in ExecutionRevertedError walk check and test case for it.
PR-Codex overview
This PR focuses on fixing an undefined reference issue in the
getNodeError
function and adding a new test case for handling errors with a null cause.Detailed summary
getNodeError
by updating the type check to handlenull
andundefined
values.UnknownNodeError
to check error handling when the cause isnull
.