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
In testing of a Rosetta implementation on a blockchain that should contain reconciliation errors, the check command fails to find the errors unless --interesting-accounts is used. This seems to be caused by the reconciliation checks becoming overly delayed so as to never happen.
To Reproduce
Run rosetta-cli check --lookup-balance-by-block=false --interesting-accounts interesting.json and watch it find reconciliation errors.
Run rosetta-cli check --lookup-balance-by-block=false and let it spin forever and never find any reconciliation problems.
Expected behavior
I expect the same errors to be found, though perhaps in different amounts of time.
The text was updated successfully, but these errors were encountered:
Thanks for posting this issue @metajack! You found a very annoying bug that only affects check when --lookup-balance-by-block=false.
This issue can occur if an account (in this case, ones that have reconciliation issues) are skipped while check is catching up to tip and never show up in blocks again.
Describe the bug
In testing of a Rosetta implementation on a blockchain that should contain reconciliation errors, the check command fails to find the errors unless --interesting-accounts is used. This seems to be caused by the reconciliation checks becoming overly delayed so as to never happen.
To Reproduce
Run
rosetta-cli check --lookup-balance-by-block=false --interesting-accounts interesting.json
and watch it find reconciliation errors.Run
rosetta-cli check --lookup-balance-by-block=false
and let it spin forever and never find any reconciliation problems.Expected behavior
I expect the same errors to be found, though perhaps in different amounts of time.
The text was updated successfully, but these errors were encountered: