"v" would dereference beyond the string length, and "v10" would show as '1'
Turn both of these cases into a blank, like anything else unexpected currently is.
"v" would dereference beyond the string length, and "v10" would show as '1'
Turn both of these cases into a blank, like anything else unexpected currently is.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For detailed information about the code coverage, see the test coverage report.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | sipa, hernanmarino, alfonsoromanz, achow101 |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
I don't think supporting a malicious server reply in bitcoin-cli is a use case to support. I think just using .at(1) would be fine as well, presumably resulting in a non-UB crash, similar to when the server replies with the wrong type?
Maybe, but this seems cleaner anyway since it also addresses far-future "v10" or such. Any reason to prefer an exception over this?
utACK c3e632b44153e314ef946f342c68c2758b1cbc4d.
I wouldn't call it a bugfix, but it does seem slightly better.
utACK c3e632b44153e314ef946f342c68c2758b1cbc4d
ACK c3e632b44153e314ef946f342c68c2758b1cbc4d
ACK c3e632b44153e314ef946f342c68c2758b1cbc4d