If the ledger was not specified, the API returns an error such as the following:
{
"error": "invalidParams",
"error_code": 31,
"error_message": "Exactly one of ledger_hash and ledger_index can be set.",
"id": "book_changes_use_default",
"request": {
"command": "book_changes",
"id": "book_changes_use_default"
},
"status": "error",
"type": "response"
}
Environment
Tested using the xrplcluster.com servers running 2.2.0-rc1, but I think this API hasn't been changed much if at all since https://github.com/XRPLF/rippled/pull/4212 two years ago so the problems probably exist in older versions.
The s1.ripple.com cluster mostly goes to Clio servers, which don't have this bug.
Issue Description
The
book_changes
API method requires you to specify a ledger version, but doesn't follow the standard conventions for doing so:"ledger_index": "validated"
ledger_index
orledger_hash
it fails with an error instead of choosing a ledger by defaultrippled
, the default should be thecurrent
ledger.Steps to Reproduce
Same applies for
current
andclosed
ledger shortcuts.Choosing a ledger by default
Same as above, but the request is as follows:
Expected Result
Response uses the latest validated/current/closed ledger as specified, or uses an appropriate default.
Actual Result
If using a shortcut string, the API returns an error such as the following:
If the ledger was not specified, the API returns an error such as the following:
Environment
Tested using the xrplcluster.com servers running 2.2.0-rc1, but I think this API hasn't been changed much if at all since https://github.com/XRPLF/rippled/pull/4212 two years ago so the problems probably exist in older versions.
The s1.ripple.com cluster mostly goes to Clio servers, which don't have this bug.
See Also
5033
5035