oxidecomputer / oxidecomputer/dice-util
Want a mechanism to prevent breaking a4x2 and voxel
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 3
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 16
Description
Changes to PlatformId serial number parsing or the programmatic API will have a significant chance of breaking simulation/emulation platforms. These platforrms should be tested with the changes before they are made. Ideally there would be a way to do this automatically, although I don't know how exactly. Over time we expect voxel to replace a4x2 and so we'd only have to test there.
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
The issue names PlatformId serial-number parsing, the programmatic API, and the a4x2 and voxel simulation/emulation platforms, but no files or tests. Start by locating those entry points and any existing platform coverage. Done means changes are automatically checked against the relevant platforms, with voxel eventually serving as the primary coverage target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100