-
Notifications
You must be signed in to change notification settings - Fork 121
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(rpc): Make the verbosity argument optional in the getblock RPC #6092
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #6092 +/- ##
==========================================
+ Coverage 77.95% 78.07% +0.11%
==========================================
Files 304 304
Lines 39027 39035 +8
==========================================
+ Hits 30423 30475 +52
+ Misses 8604 8560 -44 |
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.
In the merge queue:
https://github.com/ZcashFoundation/zebra/actions/runs/4078692209/jobs/7029791337#step:8:290 |
@Mergifyio refresh |
This looks like it will be fixed by PR #6091, so I'll retry this PR. |
✅ Pull request refreshed |
Motivation
When
s-nomp
mines a block with Zebra, it double-checks that block was accepted by the node usinggetblock
. Currently, this fails with:This is a confusing message for users (and developers!), because the block is actually accepted in the chain.
Specifications
The default for
verbosity
is 1:https://zcash.github.io/rpc/getblock.html
Solution
verbosity
argument optional with a default of 1Review
This is not on the critical path because it's just annoying and confusing - it doesn't actually block testing progress.
Reviewer Checklist