Skip to content

Add more graceful error handling for common pathways #81

Closed
@tuxxy

Description

@tuxxy

For example, when trying to sign without registering, you get a big blob:

/Users/tux/code/cli/node_modules/@entropyxyz/sdk/dist/index.cjs:12218
    throw new Error(
          ^
Error: request failed 500, Internal Server Error fetch: http://3.84.209.123:3001/user/sign_tx FULLRESPONSE: Chain Fetch: Not Registering error: Register Onchain first
    at sendHttpPost (/Users/tux/code/cli/node_modules/@entropyxyz/sdk/dist/index.cjs:12218:11)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /Users/tux/code/cli/node_modules/@entropyxyz/sdk/dist/index.cjs:12769:26
    at async Promise.all (index 1)
    at async SignatureRequestManager.sign (/Users/tux/code/cli/node_modules/@entropyxyz/sdk/dist/index.cjs:12670:18)
    at async SignatureRequestManager.signWithAdaptersInOrder (/Users/tux/code/cli/node_modules/@entropyxyz/sdk/dist/index.cjs:12636:23)
    at async Entropy.signWithAdaptersInOrder (/Users/tux/code/cli/node_modules/@entropyxyz/sdk/dist/index.cjs:13186:12)
    at async Object.sign (/Users/tux/code/cli/src/flows/sign/index.ts:91:24)
    at async main (/Users/tux/code/cli/src/index.ts:89:30)
error Command failed with exit code 1.

We should identify these common UX errors and give more graceful error messages for them rather than erroring all ugly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions