Skip to content

feat: Error Codes/Messaging #511

Closed

Description

@drewjenkins

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.

Activity

  1. devloper commented on Feb 24, 2025

    @devloper
    Contributor

    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.

  2. piotr-roslaniec commented on Mar 10, 2025

    @piotr-roslaniec
    Contributor

    Closed by #552

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

feature ✨New feature or requeststructure 📦structure refactors or changes

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions