paritytech / paritytech/try-runtime-cli
Bisect non-idempotent migrations
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Instead of just storing the final hash, we can store storage root hashes after each run migration to figure out which one is not idempotent.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the migration runner and the existing code that stores the final hash. Determine where each migration run completes and how storage roots can be recorded per run, then check how the collected roots would identify a non-idempotent migration. Done means the behavior is covered by the project's relevant migration or try-runtime tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100