Skip to content
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

Handle ZK network errors #36

Open
nuke-web3 opened this issue Feb 5, 2025 · 1 comment · Fixed by #39
Open

Handle ZK network errors #36

nuke-web3 opened this issue Feb 5, 2025 · 1 comment · Fixed by #39

Comments

@nuke-web3
Copy link
Member

I can't figure out just yet how to handle anyhow! errors returned by SP1 SDK in a more nuanced way, we allow retry for anything.

@nuke-web3
Copy link
Member Author

nuke-web3 commented Feb 5, 2025

In testing with a retry, we can get in a bad state:

  "status": "RETRYABLE_FAILURE",
  "errorMessage": "Retryring! Previous error: InternalError(\"status: Unavailable, message: "failed nonce verification: invalid nonce for sender 0xeb698d69e4a89a57c3acbc2be4c21ca7ed69845b expected 76, got 75", details: [], metadata: MetadataMap { headers: {Some other stuff & cookies} }\")"

Need to bisect to find why a nonce is needed here and why it's breaking as written now.

Note that this was for a failed job that bypassed simulation of a known broken proof, see #37

@nuke-web3 nuke-web3 changed the title Handle ZK network errrors Handle ZK network errors Feb 5, 2025
@nuke-web3 nuke-web3 reopened this Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant