-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Invalid "success" response from book_changes (possible race condition) #5033
Comments
@mDuo13 thanks for flagging this issue. What is the correct expected response for this input?
The node is in the process of acquiring this ledger from one of its peers. Hence, the specified ledger_index is not too high |
Issue Description
When querying for a recent ledger by index, sometimes the result doesn't match the expected format.
Steps to Reproduce
Make WebSocket API requests such as the following, replacing the ledger index with the most recent one:
The problem is intermittent, so it may take some tries to reproduce. Be sure to keep updating the ledger index with the most recent one as new ledgers are closed.
Expected Result
The API should either return a response in the expected format or an error message.
Example valid response (with non-empty changes):
Example expected error response if the ledger index is too high:
Actual Result
In some cases the response claims to be a success but it contains the wrong data, apparently some sort of status update on the status of acquiring the requested ledger. Looks like a Ledger Request Object.
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 #4212 two years ago so the problems probably exist in older versions.
The s1.ripple.com cluster mostly goes to Clio servers; I haven't been able to reproduce on there.
The text was updated successfully, but these errors were encountered: