-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
RPCS: Failed to marshal reply: rpcversion '' is invalid #1711
Comments
I think this is a regression due to the recently merged JSON-RPC Batch implementation. cc: @jakesyl We should try to include a fix in 0.22.0 (#1706) - should be quite simple to implement from the look of it. @jcvernaleo |
I was under the impression that the rpcversion was supposed to be there. @jakesyl care to look at this? |
I'm seeing this error too with 0.22 beta... (makes sense, because it's still open) Changing this line to |
I still get this error, but it's easy to fix with this commit nikicat@eaac8c9 |
Seeing this error when calling
getinfo
using https://github.com/petertodd/python-bitcoinlib:I'm using the master@2d7825c. I believe it happens because btcd expects
jsonrpc
field to be providedbtcd/btcjson/jsonrpc.go
Lines 96 to 101 in 2d7825c
when processing RPC requests:
btcd/rpcserver.go
Lines 4152 to 4155 in 2d7825c
However, bitcoinlib does not send it
https://github.com/petertodd/python-bitcoinlib/blob/0ea83c4fd499c63823754627c69ebdd79dc0d62c/bitcoin/rpc.py#L217-L220
What is the "ground truth" for the rpc spec? is the field expected to be set by clients?
The text was updated successfully, but these errors were encountered: