-
Notifications
You must be signed in to change notification settings - Fork 38.7k
[qa] Don't set unknown rpcserialversion #9322
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
Conversation
|
It looks intentional and desirable to allow setting future serialisation versions. Especially something like 9999 to mean "use the very latest even if not the default". |
|
@luke-jr Makes sense, but I was assuming that's what the default was. |
|
ACK |
| if (GetArg("-rpcserialversion", DEFAULT_RPC_SERIALIZE_VERSION) < 0) | ||
| return InitError("rpcserialversion must be non-negative."); | ||
|
|
||
| if (GetArg("-rpcserialversion", DEFAULT_RPC_SERIALIZE_VERSION) > 1) |
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.
Maybe define a constant for the max valid RPC serialize version?
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.
Which would imply the default is not always the max. It is not clear from the comments if this is desired.
Edit: Anyway, fixing this nit is irrelevant for backport. Either we merge/backport this and bikeshed later or we close the pull based on luke-jr's rationale.
Github-Pull: bitcoin#9322 Rebased-From: fa615d3
When merged, this will merge #9292 as well.
I created a new pull, so 0.13.2 isn't blocked by this.