Skip to content
Snippets Groups Projects

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
Merged Marcin requested to merge mi_restart_sync into develop
Viewing commit 144c285a
Show latest version
1 file
+ 1
− 1
Compare changes
  • Side-by-side
  • Inline
  • 144c285a
    Marcin
    issue #91: incorrect results when initial sync started not from scratch · 144c285a
    Marcin authored 
    The problem was with column hive_stat.block_num which is used only as
a last synced block number, but it was set with a last block number
known by hived
hive/indexer/sync.py
+ 1
− 1
@@ -399,7 +399,7 @@ class Sync:
self._db.query("""UPDATE hive_state SET block_num = :block_num,
steem_per_mvest = :spm, usd_per_steem = :ups,
sbd_per_steem = :sps, dgpo = :dgpo""",
block_num=state['dgpo']['head_block_number'],
block_num=Blocks.head_num(),
spm=state['steem_per_mvest'],
ups=state['usd_per_steem'],
sps=state['sbd_per_steem'],