go-ethereum/eth/catalyst
jwasinger 43832e65fd
eth/catalyst: abort dev mode block commit if shut down is triggered (#32166)
alternate approach to https://github.com/ethereum/go-ethereum/pull/31328
suggested by @MariusVanDerWijden . This prevents Geth from outputting a
lot of logs when trying to commit on-demand dev mode blocks while the
client is shutting down.

The issue is hard to reproduce, but I've seen it myself and it is
annoying when it happens. I think this is a reasonable simple solution,
and we can revisit if we find that the output is still too large (i.e.
there is a large delay between initiating shut down and the simulated
beacon receiving the signal, while in this loop).

Co-authored-by: Marius van der Wijden <m.vanderwijden@live.de>
2025-07-08 22:15:53 +09:00
..
api.go eth/catalyst: fix the log message in newPayloadV4 (#32125) 2025-07-01 15:04:05 +08:00
api_test.go eth/catalyst: in tests, manually sync txpool after initial chain insertion to prevent race between txpool head reset and promotion of txs that will be subsequently added (#31595) 2025-04-10 19:49:54 +08:00
queue.go cmd/geth: implement dev mode for post-merge (#27327) 2023-07-06 04:42:34 -04:00
simulated_beacon.go eth/catalyst: fix edge case in simulated backend (#31871) 2025-07-02 14:50:18 +09:00
simulated_beacon_api.go eth/catalyst: abort dev mode block commit if shut down is triggered (#32166) 2025-07-08 22:15:53 +09:00
simulated_beacon_test.go eth/catalyst: set FeeRecipient in dev mode (#31316) 2025-03-17 09:32:44 +01:00
tester.go cmd, eth/catalyst: exit geth only if exitWhenSynced is specified (#32149) 2025-07-08 15:51:08 +08:00
witness.go eth/catalyst: fix the log message in newPayloadV4 (#32125) 2025-07-01 15:04:05 +08:00