mirror of
https://github.com/bitcoin/bitcoin.git
synced 2026-01-20 07:09:15 +01:00
Merge bitcoin/bitcoin#32821: rpc: Handle -named argument parsing where '=' character is used
f53dbbc505test: Add functional tests for named argument parsing (zaidmstrr)694f04e2bdrpc: Handle -named argument parsing where '=' character is used (zaidmstrr) Pull request description: Addresses [comment](https://github.com/bitcoin/bitcoin/pull/31375#discussion_r2091886628) and [this](https://github.com/bitcoin/bitcoin/pull/31375#discussion_r2092039999). The [PR #31375](https://github.com/bitcoin/bitcoin/pull/31375) got merged and enables `-named` by default in the `bitcoin rpc` interface; `bitcoin rpc` corresponds to `bitcoin-cli -named` as it's just a wrapper. Now, the problem arises when we try to parse the positional paramater which might contain "=" character. This splits the parameter into two parts first, before the "=" character, which treats this as the parameter name, but the other half is mostly passed as an empty string. Here, the first part of the string is an unknown parameter name; thus, an error is thrown. These types of errors are only applicable to those RPCs which might contain the `=` character as a parameter. Some examples are `finalizepsbt`, `decodepsbt`, `verifymessage` etc. This is the one example of the error in `finalizepsbt` RPC: ``` ./bitcoin-cli -named -regtest finalizepsbt cHNidP8BAJoCAAAAAqvNEjSrzRI0q80SNKvNEjSrzRI0q80SNKvNEjSrzRI0AAAAAAD9////NBLNqzQSzas0Es2rNBLNqzQSzas0Es2rNBLNqzQSzasBAAAAAP3///8CoIYBAAAAAAAWABQVQBGVs/sqFAmC8HZ8O+g1htqivkANAwAAAAAAFgAUir7MzgyzDnRMjdkVa7d+Dwr07jsAAAAAAAAAAAA= error code: -8 error message: Unknown named parameter cHNidP8BAJoCAAAAAqvNEjSrzRI0q80SNKvNEjSrzRI0q80SNKvNEjSrzRI0AAAAAAD9////NBLNqzQSzas0Es2rNBLNqzQSzas0Es2rNBLNqzQSzasBAAAAAP3///8CoIYBAAAAAAAWABQVQBGVs/sqFAmC8HZ8O+g1htqivkANAwAAAAAAFgAUir7MzgyzDnRMjdkVa7d+Dwr07jsAAAAAAAAAAAA ``` This PR fixes this by updating the `vRPCConvertParams` table that identifies parameters that need special handling in `-named` parameter mode. The parser now recognises these parameters and handles strings with "=" char correctly, preventing them from being incorrectly split as parameter assignments. ACKs for top commit: ryanofsky: Code review ACKf53dbbc505. Just applied comment & test suggestions since last review kannapoix: Code review ACK:f53dbbc505achow101: ACKf53dbbc505Tree-SHA512: 1b517144efeff45a4c4256c27a39ddf187f1d6189d133402a45171678214a10ff2925c31edcfd556d67f85bd26d42f63c528b941b68c9880eab443f2c883e681
This commit is contained in:
@@ -91,9 +91,8 @@ int main(int argc, char* argv[])
|
||||
// Since "bitcoin rpc" is a new interface that doesn't need to be
|
||||
// backward compatible, enable -named by default so it is convenient
|
||||
// for callers to use a mix of named and unnamed parameters. Callers
|
||||
// can override this by specifying -nonamed, but should not need to
|
||||
// unless they are passing string values containing '=' characters
|
||||
// as unnamed parameters.
|
||||
// can override this by specifying -nonamed, but it handles parameters
|
||||
// that contain '=' characters, so -nonamed should rarely be needed.
|
||||
args.emplace_back("-named");
|
||||
} else if (cmd.command == "wallet") {
|
||||
args.emplace_back("bitcoin-wallet");
|
||||
|
||||
Reference in New Issue
Block a user