-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sc 68969 immutable stark error #477
Merged
Merged
Conversation
This file contains 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
This pull request has been linked to Shortcut Story #68969: Immutable - Magic rpcProvider interaction bug when calling Stark contract methods. |
bcleary06
approved these changes
Mar 20, 2023
Ariflo
approved these changes
Mar 20, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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.
📦 Why? (Required)
Immutable tested this line of code with 3 providers
await contract.connect(PROVIDER).isRegistered(userPublicStarkKey);
The error from Ethers using the Magic Provider was different than the Alchemy / JSON RPC Providers
This fix makes the error from the Magic Provider consistent with the other providers
Ethers expects a data key to be present in the RPC error - if data is present from bubbled up error, we now map this in the MagicRPCError - see here https://www.jsonrpc.org/specification#response_object
How was it tested? (Required)
How did you test/validate correctness of changes?
Screenshots (Optional)
Previous issue - inconsistent errors from Magic (top) and JSON RPC Provider / Alchemy provider (expected - middle, bottom)
success.magic.sdk.mov
3 consistent errors (after fixes) - Magic, JSON RPC, and Alchemy
Reviewer Notes (Optional)
For this to pass, the magic-sdk PR should be merged in first (type from magic-sdk now expects the data key)
PR Description Guide
Please only add one label:
patch
: Bug Fix?minor
: New Feature?major
: Breaking Change?skip-release
: It's unnecessary to publish this change.