Fixed the issue where the node might get stuck in the l1 client shutdown function when the node is in engine sync mode during shutdown.
Rationale
When the node has not yet fully synchronized and was in engine sync mode, the GoOrUpdatePreFetchReceipts method is not executed. At this time, the done channel of the l1 client has no consumers. If the node is closed at this moment, it will get stuck at the l1 client close operation.
If I simply close the done channel, a panic: Log in goroutine after Test_xxx has completed issue will occur during e2e testing. I must ensure that the done channel is truly closed before the close method returns.
Example
none
Changes
Notable changes:
Add preFetchReceiptsClosedChan to ensure that everything is closed before returning from the Close function
Add isPreFetchReceiptsRunning to ensure that the node does not get stuck during shutdown when in Engine Sync mode.
Description
Fixed the issue where the node might get stuck in the l1 client shutdown function when the node is in engine sync mode during shutdown.
Rationale
When the node has not yet fully synchronized and was in engine sync mode, the
GoOrUpdatePreFetchReceiptsmethod is not executed. At this time, the done channel of the l1 client has no consumers. If the node is closed at this moment, it will get stuck at the l1 client close operation. If I simply close the done channel, apanic: Log in goroutine after Test_xxx has completedissue will occur during e2e testing. I must ensure that the done channel is truly closed before the close method returns.Example
none
Changes
Notable changes:
preFetchReceiptsClosedChanto ensure that everything is closed before returning from the Close functionisPreFetchReceiptsRunningto ensure that the node does not get stuck during shutdown when in Engine Sync mode.