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
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
A node that is synchronizing should not generate blocks.
Actual behavior
A node that is synchronizing is generating blocks, causing conflicts in ABIClients.initStateMachine.
Steps to reproduce
Run multiple nodes, let their respective chain grow, terminate them and relaunch with fixedPeers or seedPeers configured, reaching a scenario where one of the nodes will eventually starts syncing, debug logs will log [err=Cannot read properties of undefined (reading 'moduleStore')] or Execution context {some id} already initialized.
Which version(s) does this affect? (Environment, OS, etc...)
Lisk SDK development branch.
The text was updated successfully, but these errors were encountered:
Expected behavior
A node that is synchronizing should not generate blocks.
Actual behavior
A node that is synchronizing is generating blocks, causing conflicts in
ABIClients.initStateMachine
.Steps to reproduce
Run multiple nodes, let their respective chain grow, terminate them and relaunch with
fixedPeers
orseedPeers
configured, reaching a scenario where one of the nodes will eventually starts syncing, debug logs will log[err=Cannot read properties of undefined (reading 'moduleStore')] or Execution context {some id} already initialized
.Which version(s) does this affect? (Environment, OS, etc...)
Lisk SDK
development
branch.The text was updated successfully, but these errors were encountered: