-
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
Update comments in LedgerHistory::fixIndex (Version: 1.10) #4572
Comments
Your commit link is broken. Can you open a PR? |
ckeshava
added a commit
to ckeshava/rippled
that referenced
this issue
Jun 14, 2023
7 tasks
(I edited ckeshava's post to fix the commit link.) |
ckeshava
added a commit
to ckeshava/rippled
that referenced
this issue
Sep 22, 2023
`LedgerHistory::fixIndex` returns `false` if a repair was performed. Fix XRPLF#4572
ckeshava
added a commit
to ckeshava/rippled
that referenced
this issue
Sep 25, 2023
`LedgerHistory::fixIndex` returns `false` if a repair was performed. Fix XRPLF#4572
sophiax851
pushed a commit
to sophiax851/rippled
that referenced
this issue
Jun 12, 2024
`LedgerHistory::fixIndex` returns `false` if a repair was performed. Fix XRPLF#4572
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
The
LedgerHistory::fixIndex
function returnsfalse
if a repair is performed. This is reflected in its usage here and hereThe existing comment appears to contradict the return value of the function.
Here is a commit to this effect.
Steps to Reproduce
This is an update to a comment in the codebase
@thejohnfreeman Does this look okay?
The text was updated successfully, but these errors were encountered: