oxidecomputer / oxidecomputer/quartz
figure out how to better check and deploy images ending in a hubris PR
Open
Nobody has claimed this yet.
build system
- Dominant language
- VHDL
- Stars
- 22
- Forks
- 2
- Avg merge
- 9h 38m
- Merged PRs (30d)
- 1
Description
A few desires:
- bitstream hash generated at build-time, passed to hubris. Since we're downloading artifacts, hash enforcement avoids corruption and other accidents.
- no manual renaming.
- timing checked and clearly reported.
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
No files, tests, or entry points are named. Start by tracing the existing image build and deployment flow and how it hands artifacts to Hubris. Done should include build-time bitstream hashes passed to Hubris, no manual renaming, and clear timing reports, with the expected behavior defined before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100