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

Add nullifier to CircuitErrorCode::BASE__INVALID_NULLIFIER_RANGE message #2114

Closed
LHerskind opened this issue Sep 8, 2023 · 1 comment
Closed
Assignees
Labels
T-fix Type: fix this. Not quite a bug.

Comments

@LHerskind
Copy link
Contributor

The CircuitErrorCode::BASE__INVALID_NULLIFIER_RANGE error tells me a lot of stuff, except what the nullifier actually is. Add this to make debugging easier.

@LHerskind LHerskind added the T-fix Type: fix this. Not quite a bug. label Sep 8, 2023
@LHerskind LHerskind self-assigned this Sep 8, 2023
@LHerskind LHerskind mentioned this issue Sep 8, 2023
4 tasks
PhilWindle pushed a commit that referenced this issue Sep 8, 2023
Fixes #2113 and #2114 

# Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if
the PR is ready to merge.
- [ ] If the pull request requires a cryptography review (e.g.
cryptographic algorithm implementations) I have added the 'crypto' tag.
- [ ] I have reviewed my diff in github, line by line and removed
unexpected formatting changes, testing logs, or commented-out code.
- [ ] Every change is related to the PR description.
- [ ] I have
[linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
this pull request to relevant issues (if any exist).
@LHerskind
Copy link
Contributor Author

Closed by #2115

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-fix Type: fix this. Not quite a bug.
Projects
Archived in project
Development

No branches or pull requests

1 participant