issue #91: incorrect results when initial sync started not from scratch
Merged
issue #91: incorrect results when initial sync started not from scratch
mi_restart_sync
into
develop
The problem was with column hive_stat.block_num which is used only as a last synced block number, but it was set as a last block number known by hived
Merge request reports
Activity
added 1 commit
- c32a1c4f - issue #91 (closed): incorrect results when initial sync started not from scratch
added 1 commit
- 144c285a - issue #91 (closed): incorrect results when initial sync started not from scratch
mentioned in commit 8d06d8bc
Please register or sign in to reply