You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A panic occurs due to cmtAPI being nil in the isNextProposer function during the ReplayBlocks process. This issue arises for any node that is behind the latest state and has the evm-build-optimistic option set to true.
Description and context
A panic occurs due to cmtAPI being nil in the
isNextProposer
function during the ReplayBlocks process. This issue arises for any node that is behind the latest state and has theevm-build-optimistic
option set to true.panic flow:
ReplayBlocksWithContext
-->FinalizeBlock
-->PostFinalize
how
cmtAPI
can be nil?cmtAPI
is set afternewCometNode
is called (ref. code)newCometNode
panic log:
Steps to reproduce
evm-build-optimistic
to trueExperienced behavior
A nil panic occurs during block synchronization and replay when the
evm-build-optimistic
option is enabled.Expected behavior
No nil panic should occur during block synchronization and replay, even when the
evm-build-optimistic
option is enabled.Solution recommendation
Implement a nil check similar to the approach used in Omni.
The text was updated successfully, but these errors were encountered: