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
Bug Description
The OP_NODE_RPC_ADMIN_STATE flag is used to persist the sequencer state so that sequencer maintains its active state after unexpected restart. This behaviour seems to be broken.
Steps to Reproduce
Set OP_NODE_RPC_ADMIN_STATE to a persistent path
Make admin_startSequencer call to start the sequencer.
Observe that OP_NODE_RPC_ADMIN_STATE/state is updated with {"sequencerStarted":true}
Restart op-node
Observe that the op-node is started with sequencing disabled and that OP_NODE_RPC_ADMIN_STATE/state is updated to {"sequencerStarted":false}
Expected behavior
op-node should load and apply the state stored in OP_NODE_RPC_ADMIN_STATE after restarts
Environment Information:
op-node v1.9.5 (although i think this has been an issue since at least a few 1.9 releases back)
The text was updated successfully, but these errors were encountered:
Bug Description
The OP_NODE_RPC_ADMIN_STATE flag is used to persist the sequencer state so that sequencer maintains its active state after unexpected restart. This behaviour seems to be broken.
Steps to Reproduce
OP_NODE_RPC_ADMIN_STATE
to a persistent pathOP_NODE_RPC_ADMIN_STATE/state
is updated with{"sequencerStarted":true}
OP_NODE_RPC_ADMIN_STATE/state
is updated to{"sequencerStarted":false}
Expected behavior
op-node should load and apply the state stored in OP_NODE_RPC_ADMIN_STATE after restarts
Environment Information:
op-node v1.9.5 (although i think this has been an issue since at least a few 1.9 releases back)
The text was updated successfully, but these errors were encountered: