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.

Sign up for GitHub

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

Jump to bottom

Create "Checker Migrations" for invariants on runtime upgrades #463

Open
Garandor opened this issue Mar 25, 2022 · 1 comment
Open

Create "Checker Migrations" for invariants on runtime upgrades #463

Garandor opened this issue Mar 25, 2022 · 1 comment
Assignees
@flame4
Labels
A-calamari Area: Issues and PRs related to the Calamari Runtime A-ci Area: Continuous Integration A-runtime Area: Issues and PRs related to Runtimes C-enhancement Category: An issue proposing an enhancement or a PR with one C-good-first-issue Category: Good first issues P-low Priority: Low
Milestone
Future

Comments

@Garandor
Copy link
Contributor

The try-runtime feature allows to define "dry run" migrations that don't actually modify state, but can test pre- and post-runtime upgrade state for sanity, e.g.

  • Check that the validators() set is the same before as after the upgrade
  • Check that no account lost balance due to the upgrade
  • Check that no account was deleted/reaped due to the upgrade

These can be built as a compact "upgrade checker struct" and run as part of QA of every (runtime-upgrade) release, which can happen as part of a CI check when #457 is merged

The process is described in https://www.crowdcast.io/e/substrate-seminar/41 around 1:15:00
@Garandor Garandor added C-enhancement Category: An issue proposing an enhancement or a PR with one A-calamari Area: Issues and PRs related to the Calamari Runtime A-ci Area: Continuous Integration A-runtime Area: Issues and PRs related to Runtimes P-low Priority: Low labels Mar 25, 2022
@Garandor Garandor mentioned this issue Mar 25, 2022
Merged
13 tasks
@ghzlatarev
Copy link
Contributor

Duplicate of #236

@ghzlatarev ghzlatarev marked this as a duplicate of #236 Apr 7, 2022
@ghzlatarev ghzlatarev added this to the v3.4.0 milestone Jul 15, 2022
@ghzlatarev ghzlatarev added the C-good-first-issue Category: Good first issues label Jul 15, 2022
@flame4 flame4 mentioned this issue Aug 8, 2022
Merged
3 tasks
@Garandor Garandor modified the milestones: v3.4.0, v3.5.0 Sep 9, 2022
@Garandor Garandor modified the milestones: v3.5.0, Future Sep 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@flame4 flame4

Labels
A-calamari Area: Issues and PRs related to the Calamari Runtime A-ci Area: Continuous Integration A-runtime Area: Issues and PRs related to Runtimes C-enhancement Category: An issue proposing an enhancement or a PR with one C-good-first-issue Category: Good first issues P-low Priority: Low
Projects
None yet
Milestone
Future
Development

No branches or pull requests
3 participants
@Garandor @flame4 @ghzlatarev