• Joshua Gutow's avatar
    op-node: Fix reset bug in batch queue (#3694) · a88ba67d
    Joshua Gutow authored
    The batch queue was using the previous origin when computing if
    the origin was behind or not. It would then immediately advance
    it's internal origin to the next origin (confusingly coming from
    the `prev` stage). It would take action on the current origin based
    on out of date data. Specifically, it would not save an origin that
    should have been saved into the l1Blocks array. This causes errors
    because the L1 Origin of the safe head would not be present when
    attempting to derive the next batch after a reset.
    a88ba67d
Name
Last commit
Last update
..
client Loading commit data...
cmd Loading commit data...
eth Loading commit data...
flags Loading commit data...
heartbeat Loading commit data...
metrics Loading commit data...
node Loading commit data...
p2p Loading commit data...
rollup Loading commit data...
sources Loading commit data...
testlog Loading commit data...
testutils Loading commit data...
version Loading commit data...
withdrawals Loading commit data...
.gitignore Loading commit data...
Dockerfile Loading commit data...
LICENSE Loading commit data...
Makefile Loading commit data...
README.md Loading commit data...
docker.go.work Loading commit data...
go.mod Loading commit data...
go.sum Loading commit data...
service.go Loading commit data...