Remove error from ZkLoginVerifyResult#25715
Merged
tpham-mysten merged 2 commits intomainfrom Mar 6, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
henryachen
reviewed
Mar 6, 2026
Collaborator
henryachen
left a comment
There was a problem hiding this comment.
@tpham-mysten sui-indexer-alt-e2e-tests::graphql_zklogin_tests are failing, looks like you need to update the tests to remove references to error
henryachen
reviewed
Mar 6, 2026
Contributor
Author
|
Thanks @henryachen, I have fixed the tests |
henryachen
approved these changes
Mar 6, 2026
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.
Description
Just return a regular error message if verification fails. GraphQL supports partial responses, so the fact that we produce an error in one sub-tree will not prevent other sub-trees from finishing resolving.
Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.