oxidecomputer / oxidecomputer/propolis
Test versioning of migration information
Open
Nobody has claimed this yet.
migration
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
This includes:
- The protocol version itself
- Per-entity data structures for comparing/serializing state
- Instance specifications
Contributor guide
No contributing guide indexed for this repository
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 locating the migration protocol, per-entity state comparison and serialization code, and instance specification handling in the Rust codebase. Determine how protocol versions and these structures are represented, then add coverage for versioning, comparison/serialization, and instance specifications. Done means the migration information has tests covering all three listed areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100