Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Session Commits Persistence #89

Closed
miloszm opened this issue Oct 6, 2022 · 1 comment
Closed

Session Commits Persistence #89

miloszm opened this issue Oct 6, 2022 · 1 comment
Assignees
Labels
mark:next Strategic issues related to next versions of Testnet and mid/long term plans team:Core Low Level Core Development Team (Rust) type:feature implementing a new feature

Comments

@miloszm
Copy link
Contributor

miloszm commented Oct 6, 2022

Summary

馃挕 After system is restarted, we need to be able to find and restore session's commits that have been performed in the past.

Possible solution design or implementation

馃挕 TBD

Additional context

馃挕 The following minimal test T1 expressed as pseudocode should work:

start VM
deploy module M1 with initial state S1
start session S
assert state of M1 is S1
set state of M1 to S2
commit session S, obtain commit id CID1
drop session S
start session S
restore session to CID1
assert state of M1 is S2

Note that this issue is about session level persistence:

Session level persistence - session's commit method produces a session_commit_id which can be used at later time as argument to session's restore method. Note, that here we can distinguish: a) persistence of particular commits, under the assumption that the user stores commit ids, as well as b) persistence of commit ids themselves, under the assumption that the user does not store them.

@miloszm miloszm added mark:next Strategic issues related to next versions of Testnet and mid/long term plans team:Core Low Level Core Development Team (Rust) type:feature implementing a new feature labels Oct 6, 2022
@miloszm miloszm self-assigned this Oct 6, 2022
@ureeves
Copy link
Member

ureeves commented Oct 14, 2022

Closed by #98

@ureeves ureeves closed this as completed Oct 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mark:next Strategic issues related to next versions of Testnet and mid/long term plans team:Core Low Level Core Development Team (Rust) type:feature implementing a new feature
Projects
None yet
Development

No branches or pull requests

2 participants