You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
The internal logic of
IterateIndexes()
is bugged, which is why #3999 uses a different implementation to bypass the bugged behavior ofIterateIndexes()
. In particular,chainInfo.Item2
should be the number ofBlock
s associated with a chain id, not theTip.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.The text was updated successfully, but these errors were encountered: