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 previously configured as a syncing node should not crash once reconfigured with generators.
Actual behavior
A node previously configured as a syncing node crashes once it is reconfigured with generators, reporting err=Execution context is already initialized with {context id} thrown from ABIHandler.initStateMachine()
Steps to reproduce
Launch two nodes, one generator and one syncing, after a certain amount of blocks, reconfigure syncing nodes with generators, relaunch the syncing node and after random block generation
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 previously configured as a syncing node should not crash once reconfigured with generators.
Actual behavior
A node previously configured as a syncing node crashes once it is reconfigured with generators, reporting
err=Execution context is already initialized with {context id}
thrown fromABIHandler.initStateMachine()
Steps to reproduce
Launch two nodes, one generator and one syncing, after a certain amount of blocks, reconfigure syncing nodes with generators, relaunch the syncing node and after random block generation
Which version(s) does this affect? (Environment, OS, etc...)
Lisk SDK
development
branch.The text was updated successfully, but these errors were encountered: