You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there isn't a great error messaging system hooked up for consumers of the proving system. There is an error field returned, but it generally doesn't contain useful information.
If the prover knows the error, it would be helpful if it could return an error code so the UI is able to gracefully recover and display user-friendly messages. The UI may also be able to do things such as detect transient errors and offer the user to attempt proof generation again, or detect unhandled exceptions and offer greater options for feedback.
Agreed. In particular, we should check manifest failures on the client and the notary. Today we only check the manifest validation on the notary. Then we could have useful logs on the client.
We should also improve the logs for manifest failures to be more developer friendly.
Activity
devloper commentedon Feb 24, 2025
Agreed. In particular, we should check manifest failures on the client and the notary. Today we only check the manifest validation on the notary. Then we could have useful logs on the client.
We should also improve the logs for manifest failures to be more developer friendly.
piotr-roslaniec commentedon Mar 10, 2025
Closed by #552