-
Notifications
You must be signed in to change notification settings - Fork 15
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
feat(iota-genesis-builder): snapshot test data setup #761
feat(iota-genesis-builder): snapshot test data setup #761
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.
lgtm
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.
Milestone diffs aren't updated and outputs/their headers aren't verified in any way, which is fine for our test case here, but could potentially lead to errors (total supply could overflow) when trying to analyze it with other tools. Just mentioning it here so you're aware
Yeah I've purposely ignored the milestone diffs for now as it didn't contribute to the test and the snapshot parser interface doesn't even allow it for now. I'll create a new issue. |
* initial add_snapshot_test_data setup * increment snapshot header output count * add new outputs to snapshot * change the header total supply * add some comments * rename and add comment * rename example
* initial add_snapshot_test_data setup * increment snapshot header output count * add new outputs to snapshot * change the header total supply * add some comments * rename and add comment * rename example
* initial add_snapshot_test_data setup * increment snapshot header output count * add new outputs to snapshot * change the header total supply * add some comments * rename and add comment * rename example
Fixes #760
The
dummy
module is just here to quickly verify that everything works, it will be removed in the next PR.Each subsequent PR for #611 should add a new module providing a
fn outputs() -> Vec<(OutputHeader, Output)>
.