geomad
geomad
I think that's done to be consistent with OpenEthereum that handled traces this way. Imo its not ideal though, geths behavior here is better. Would love to see a flag...
> can you try this branch out `flushing-blocks` Unfortunately no, since when I update https://github.com/ledgerwatch/erigon/issues/5482 reoccurs and erigon is not working
> can you try this branch out `flushing-blocks` Looks like nothing changed with this branch. ``` 20:46:12.000 GETH block 15598524 20:46:12.165 ERIGON block: 15598524 20:46:24.846 GETH block 15598525 20:46:37.556 GETH...
> times Looks like sometimes it does, although less than before, and some commit times have gone up quite a bit ``` [INFO] [09-24|01:53:39.650] [p2p] GoodPeers eth66=11 [INFO] [09-24|01:53:40.001] [txpool]...
It looks like on erigon 93add6cacf151fbaa5eff9a0d7854e86b64ff371 logs the blocks come in correctly, but every few blocks erigon "forgets" to notify the RPC Daemon, and all the calls point to the...
> run `./build/bin/integration state_stage --unwind=500 --datadir=your/datadir --chain=your-chain` that might be a work around to your problem ok, so that's weird, I updated erigon and started it again, to get the...
looks like it's broken again after a few hours running normally. ``` [INFO] [09-24|04:02:18.397] [5/7 Execution] Completed on block=15599202 [INFO] [09-24|04:02:30.847] Timings (slower than 50ms) Execution=5.606s IntermediateHashes=12.419s [INFO] [09-24|04:02:30.847] Tables...
> > (oh, I see you gave instructions on how to rewind above, but it wasn't needed with 2022.09.03) > > Yes, you need to unwind so erigon doesn't count...
> > > > (oh, I see you gave instructions on how to rewind above, but it wasn't needed with 2022.09.03) > > > > > > > > >...
> Note: I probably run an old version of `integration` since I didn't build it this time. Probably it doesn't matter but let me know if it does. I tried...