fix: Use Correct Fields while Logging Transaction Errors#101
Open
KartikSoneji wants to merge 1 commit into
Open
fix: Use Correct Fields while Logging Transaction Errors#101KartikSoneji wants to merge 1 commit into
KartikSoneji wants to merge 1 commit into
Conversation
|
@KartikSoneji is attempting to deploy a commit to the joshaavecom's projects Team on Vercel. A member of the Team first needs to authorize it. |
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
1 participant
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.
The string representation of transactions errors doesn't actually print the error, instead it includes the relayer id twice:
Relayer id 616a2f2e-d2a8-4a92-96a2-ba37fce63846 / address 0x111115763723b53395308ec4c9ab9d5fb0844cae - Send transaction error: 616a2f2e-d2a8-4a92-96a2-ba37fce63846This PR updates the error enums to use the correct tuple element index to print the actual error message.