Open sardChen opened 2 years ago
We discussed this issue internally a bit and came to the following conclusion: This is an expected error, we, we process a section of blocks and do the bloombits processing on that. If we see a reorg during that, it screws with us a bit and we have to stop and restart the bloombits processing.
We should re-architect the whole bloombits processing, as it is not really useful atm (might need to look how other clients are doing it)
Also @rjl493456442 we noticed in the log that the commit new mining work
is duplicated with always the same hash. The used version is pretty old, but it might be good to check that we don't replace a work package with the same work package (on empty blocks)
System information
Geth version: Geth-1.10.9-unstable/go1.13.8 OS & Version: ubuntu 20.04
Expected behaviour
Mining block & Synchronizing the block on the test network as normal
Actual behaviour
Consistently reporting Error:
Steps to reproduce the behaviour
Backtrace
When submitting logs: please submit them as text and not screenshots.