jleony/nanoreth
1
0
Fork 0
mirror of https://github.com/hl-archive-node/nanoreth.git synced 2025-12-06 19:09:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: add warning regarding increment_block necessity on write_to_storage (#7816)

Browse Source
This commit is contained in:
joshieDo
2024-04-23 17:40:18 +01:00
committed by GitHub
parent ee1c811c43
commit ce1e401d21
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
crates/storage/provider/src/bundle_state/bundle_state_with_receipts.rs
View File

@ -316,7 +316,12 @@ impl BundleStateWithReceipts {
let mut bodies_cursor = tx.cursor_read::<tables::BlockBodyIndices>()?; let mut bodies_cursor = tx.cursor_read::<tables::BlockBodyIndices>()?;
let mut receipts_cursor = tx.cursor_write::<tables::Receipts>()?; let mut receipts_cursor = tx.cursor_write::<tables::Receipts>()?;
for (idx, receipts) in self.receipts.into_iter().enumerate() { // ATTENTION: Any potential future refactor or change to how this loop works should keep in
// mind that the static file producer must always call `increment_block` even if the block
// has no receipts. Keeping track of the exact block range of the segment is needed for
// consistency, querying and file range segmentation.
let blocks = self.receipts.into_iter().enumerate();
for (idx, receipts) in blocks {
let block_number = self.first_block + idx as u64; let block_number = self.first_block + idx as u64;
let first_tx_index = bodies_cursor let first_tx_index = bodies_cursor
.seek_exact(block_number)? .seek_exact(block_number)?