-
Notifications
You must be signed in to change notification settings - Fork 107
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
fix(diagnostics): Hex-encode debug format of commitments, nonces, and nullifiers #5960
Conversation
76c8377
to
432b680
Compare
Looks like crates.io is having some network or capacity issues, I'll retry those parts of CI later. (Or anyone can do it if I'm not around.) |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #5960 +/- ##
==========================================
- Coverage 78.11% 78.03% -0.09%
==========================================
Files 312 312
Lines 38936 38988 +52
==========================================
+ Hits 30414 30423 +9
- Misses 8522 8565 +43 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
@Mergifyio refresh |
Failed with bug #5958 in the merge queue: |
✅ Pull request refreshed |
It looks like this has a build conflict with some code in other PRs, I'll see what I can do to fix it. |
Motivation
Zebra's debug output shows block header commitments and nonces as an array of integers, rather than hexadecimal. This makes them very hard to debug.
This diagnostics bug is impacting RPC testing.
Most of the changes in this PR are in test code, or they are tiny changes to existing code.
Solution
HexDebug
type wrapper, which automatically makes the wrapped type encode as hex duringderive(Debug)
I also opened ticket ZcashFoundation/redjubjub#155 to make similar changes in
redjubjub
.Review
This is blocking RPC testing, it is important to review soon.
Reviewer Checklist