Skip to content

fix: improve error messages for public key fetch failures#382

Open
gaffar273 wants to merge 1 commit intozama-ai:mainfrom
gaffar273:fix/improve-error-messages
Open

fix: improve error messages for public key fetch failures#382
gaffar273 wants to merge 1 commit intozama-ai:mainfrom
gaffar273:fix/improve-error-messages

Conversation

@gaffar273
Copy link

  • Replace misleading 'Impossible to fetch public key: wrong relayer url.' message

  • Use context-specific messages for different error scenarios

  • network.ts: 'Failed to fetch or deserialize public key'

  • RelayerV2PublicKey.ts: 'Failed to initialize public key from relayer response'

  • TFHECrs.ts: 'Failed to fetch or deserialize CRS from URL'

  • TFHEPublicKey.ts: 'Failed to fetch or deserialize public key from URL'

  • Use TFHEPublicKeyError instead of generic Error in TFHEPublicKey.ts

  • Preserve original error in cause for debugging

- Replace misleading 'Impossible to fetch public key: wrong relayer url.' message

- Use context-specific messages for different error scenarios

- network.ts: 'Failed to fetch or deserialize public key'

- RelayerV2PublicKey.ts: 'Failed to initialize public key from relayer response'

- TFHECrs.ts: 'Failed to fetch or deserialize CRS from URL'

- TFHEPublicKey.ts: 'Failed to fetch or deserialize public key from URL'

- Use TFHEPublicKeyError instead of generic Error in TFHEPublicKey.ts

- Preserve original error in cause for debugging
@cla-bot
Copy link

cla-bot bot commented Dec 31, 2025

Thank you for your pull request. We require contributors to sign our Contributor License Agreement / Terms and Conditions, and we don't seem to have the users @gaffar273 on file. In order for us to review and merge your code, please sign:

  • For individual contribution: our CLA
  • for Bounty submission, if you are an individual: our T&C
  • for Bounty submission, if you are a company: our T&C
    to get yourself added.

If you already signed one of this document, just wait to be added to the bot config.

@gaffar273 gaffar273 closed this Dec 31, 2025
@gaffar273 gaffar273 reopened this Dec 31, 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 this pull request may close these issues.

1 participant