oxidecomputer / oxidecomputer/helios
specifying unknown build-image -F feature should lead to failure
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 481
- Forks
- 21
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 2
Description
I recently did a build where I specified -F dmar instead of -F mbist. The build happily succeeded; however, it'd be nice if it had failed so I had discovered this at build time and not much later.
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 at the build-image entry point and trace handling of the -F feature option. Check where feature names are validated, then exercise an unknown value such as dmar and confirm that the build fails instead of succeeding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100