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.
When executeTransaction is called and the transaction is invalid, it should not make state changes to the context and should not return any event.
Currently, state db and event queue does not support multiple snapshot. Therefore, if transaction becomes invalid by afterCommandExecute, it only rolls back to the state before calling command.execute.
Update event queue to maintain multiple snapshots
Update lisk-db to the version which supports multiple snapshot
Acceptance Criteria
Add unit test to check if all state is rollbacked if afterCommandExecute fails
Add unit test for event queue to check reverting to the older snapshot
Description
When
executeTransaction
is called and the transaction is invalid, it should not make state changes to the context and should not return any event.Currently, state db and event queue does not support multiple snapshot. Therefore, if transaction becomes invalid by
afterCommandExecute
, it only rolls back to the state before callingcommand.execute
.Acceptance Criteria
afterCommandExecute
failsAdditional Information
and all snapshot can be removed when using one of the snapshot
Related: LiskArchive/lisk-db#21
The text was updated successfully, but these errors were encountered: