Skip to content
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

Fix RocksDBStore.IterateIndexes() #4000

Open
greymistcube opened this issue Nov 28, 2024 · 0 comments
Open

Fix RocksDBStore.IterateIndexes() #4000

greymistcube opened this issue Nov 28, 2024 · 0 comments

Comments

@greymistcube
Copy link
Contributor

The internal logic of IterateIndexes() is bugged, which is why #3999 uses a different implementation to bypass the bugged behavior of IterateIndexes(). In particular, chainInfo.Item2 should be the number of Blocks associated with a chain id, not the Tip.Index (which differs by 1). I am not sure as to how this hasn't been causing more serious problems (at least seemingly) so far, but upon inspection, it's been confirmed that the internal database already has been corrupted. After #3999, it should become rather trivial to fix this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant