New JournalDB doesn't seem to persist everything when importing a block
See original GitHub issueWith the new JournalDB
, when I import ropsten block 3072902 (via Chain.import_block()
), the block’s state_root doesn’t end up in the underlying DB, although it is present in the journal. That doesn’t happen when I use the old JournalDB
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Failing to store most recent snapshot #22463 - GitHub
I'm running an archive node: /usr/bin/geth --datadir=/data/geth/datadir --syncmode=full --gcmode=archive --cache=8192 --ipcdisable ...
Read more >Classic Persistence - Documentation - Akka
It is able to persist events to a journal and can react to them in a thread-safe manner. It can be used to...
Read more >Step 8: Export and validate journal data in a ledger
In this step, you export journal blocks from the vehicle-registration ledger into an Amazon S3 bucket. Then, you use the exported data to...
Read more >charm-ceph-osd - OpenDev: Free Software Needs Free Tools
:param save_location: path to save the settings to. :raises: IOError if anything goes wrong with writing. """ try: # Persist the settings for...
Read more >Frequently Asked Questions · OpenEthereum Documentation
Can I import accounts not created with OpenEthereum or Geth (e.g., MyEtherWallet)? ... Double-clicking the OpenEthereum icon doesn't do anything!?!
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yep, it seems to work!
@gsalgado can you confirm this works again on latest master so that we can close this?