Skip to content
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

chore(keystore): verbose error message when credential is not found #2943

Merged
merged 4 commits into from
Aug 7, 2024

Conversation

rymnc
Copy link
Contributor

@rymnc rymnc commented Jul 30, 2024

Description

This PR adds some verbose logging when a keystore has multiple credentials, but the rlnRelayCredIndex is not passed in to find the unique credential. The error log now has some indication of what should be done to fix it, rather than just saying credential not found.

Changes

  • logging change in waku_keystore.KeystoreCredentialNotFoundError

How to test

  1. Generate a keystore with multiple credentials by using rlnKeystoreGenerator multiple times for the same keystore
  2. Run wakunode2: ./build/wakunode2 --cluster-id:1 --rln-relay-cred-path:rlnKeystore.json --rln-relay-eth-client-address:https://eth-sepolia.g.alchemy.com/v2/<YOUR_API_KEY> --rln-relay-cred-password:password
  3. The following error log is shown:
image

@rymnc
Copy link
Contributor Author

rymnc commented Jul 30, 2024

thanks @romanzac for this report

@rymnc rymnc force-pushed the verbose-error-message branch from 18538c7 to b66f067 Compare July 30, 2024 10:13
Copy link

github-actions bot commented Jul 30, 2024

You can find the image built from this PR at

quay.io/wakuorg/nwaku-pr:2943

Built from 68ce8d5

Copy link
Collaborator

@Ivansete-status Ivansete-status left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for it! 💯

@rymnc
Copy link
Contributor Author

rymnc commented Aug 5, 2024

@Ivansete-status is this okay to merge? some filter related CI is failing

@Ivansete-status
Copy link
Collaborator

@Ivansete-status is this okay to merge? some filter related CI is failing

Sorry for delay. It is okay to merge

@Ivansete-status Ivansete-status merged commit 0f11ee1 into master Aug 7, 2024
9 of 11 checks passed
@Ivansete-status Ivansete-status deleted the verbose-error-message branch August 7, 2024 09:57
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.

3 participants