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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MetaData storage specification #42
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
I suggest modelling the existence of files using the domain of metadata
and manifest
rather than using -1
sentinels: DaveCTurner@937a7b8
This would also means you could remove steps
and limit the model size with a constraint like newMeta < 4
. (Also, this should really be a state constraint not an action constraint).
(edit: I suggested newMeta < 4 /\ newManifest < 4
but in fact the newMeta
constraint is enough)
@DaveCTurner thanks for your review! Modelling with domains looks much nicer. However, I'm not sure if we can avoid steps constraint. I've tried |
This is true, but if you remove |
@DaveCTurner thanks for your explanation, the reason why the model was running indefinitely is that I forgot to remove steps variable from the model and the number of states was infinite. Fixed by this commit d1346d7 . |
@DaveCTurner I've made a change to the specification by splitting deleteNew and deleteOld into separately deleting manifest and metadata files, which makes clearer in my opinion. Ready for the next pass. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR adds metadata storage specification to prove that the way our storage layer underlying Zen2 implementation works correctly.
This specification does no model multipath, only a single data path is modeled.