ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-04 11:55:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2933 from elmurci/remove_book_changes_known_issues_section

Browse Source 
fix: removes known issues sections, as bugs are now fixed
This commit is contained in:
Rome Reginelli
2025-01-08 11:36:31 -08:00
committed by GitHub
parent e55c7ed4ac bdfae80e0d
commit 332af39d77
1 changed files with 0 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_changes.md
View File

@@ -55,17 +55,6 @@ The request includes the following parameters:
| `ledger_hash` | [Hash][] | No | A 32-byte hex string for the ledger version to use. (See [Specifying Ledgers][]) |
| `ledger_index` | [Ledger Index][] | No | The [ledger index][] of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying Ledgers][]) |
{% admonition type="warning" name="Known Issues" %}
There are several known issue with this method in `rippled`.
- You must specify the `ledger_index` or `ledger_hash` explicitly instead of using a default or a shortcut string. ([Issue #5034](https://github.com/XRPLF/rippled/issues/5034))
- JSON-RPC API responses may be missing the `validated` field even when querying validated ledgers. ([#5035](https://github.com/XRPLF/rippled/issues/5035))
- When querying a recently-closed ledger, a successful response may sometimes return a Ledger Request Object instead of the intended data. ([#5033](https://github.com/XRPLF/rippled/issues/5033))
- When querying data from older ledgers, the server may take a long time (over 30 seconds) to respond. ([#5036](https://github.com/XRPLF/rippled/issues/5036))
These bugs do not apply to Clio servers.
{% /admonition %}
## Response Format
An example of a successful response: