-
Notifications
You must be signed in to change notification settings - Fork 107
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
Create list of high-value error messages to improve #849
Comments
@ymekuria shared https://github.com/MinaProtocol/docs/blob/main/pages/en/node-operators/transaction-failures.mdx that has been floating around, not published in the docs as of April 11, 2023 |
Another candidate:
|
IRI: @nicc |
Here's a truly bad one: #808
This is because the |
Basically, every error thrown from inside snarky is bad, because of the long and noisy stack trace. @mrmr1993 had some good ideas to address this. Here's an example (cut off) for when a constraint fails inside the prover (for example, during |
I guess |
'Permutation failed' for when you create a different circuit every time because you use a constant instead of a variable |
@nicc to review / create new issues |
All improvements identified here have been reflected as new issues with the |
We are intent on improving our error messages in general. There are some initivates that unblock this. In preparation for these improvement, we'd like a list of the most impactful error messages to focus on first.
Consider all errors (protocol, crypto, snarkyjs). Timeboxed to an estimate of 5. No more than 20 items.
Preemptive candidates:
Resources for when we are ready to improve the error messages:
The text was updated successfully, but these errors were encountered: