status-im/nimbus-eth1
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth1.git synced 2025-02-02 23:35:31 +00:00
Code Issues Projects Releases Wiki Activity

Fix block-number last saved block state (#2263)

Browse Source 
why:
  Typo. That worked the wrong way in the unit tests because the
  tests always store the last item separately with extended
  logging.

Co-authored-by: jordan <jordan@dry.pudding>
This commit is contained in:
Jordan Hrycaj 2024-05-31 10:43:31 +01:00 committed by GitHub
parent c339bf4a99
commit 483b2d8ef4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
nimbus/core/chain/persist_blocks.nim
View File

@ -170,14 +170,8 @@ proc persistBlocksImpl(c: ChainRef; headers: openArray[BlockHeader];
dbTx.commit()
# The `c.db.persistent()` call is ignored by the legacy DB which
# automatically saves persistently when reaching the zero level transaction.
#
# For the `Aristo` database, this code position is only reached if the
# the parent state of the first block (as registered in `headers[0]`) was
# the canonical state before updating. So this state will be saved with
# `persistent()` together with the respective block number.
c.db.persistent(headers[0].blockNumber - 1)
# Save and record the block number before the last saved block state.
c.db.persistent(headers[^1].blockNumber - 1)
if c.com.pruneHistory:
# There is a feature for test systems to regularly clean up older blocks