oxidecomputer / oxidecomputer/propolis
want better debugging tools for inspecting migrating device payloads
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
In debugging recent issues with device emulation and live migrations, I often find myself staring at serialized device data payloads from logs and reconstructing state to answer questions I have. It might be nice to have some tools here to help answer questions like:
- is this device running?
- are there any pending interrupts?
- is this device in an obviously inconsistent state?
Answering such questions is clearly device-specific, but I could imagine writing something like a post-processing script to read logs and construct the data into a more human-readable format. @gjcolombo also floated the idea of having a protected server endpoint where we could query the device payload data, which would be a lot more work, but potentially very valuable.
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 no files, tests, or entry points. First clarify whether the goal is a post-processing script, a protected server endpoint, or both, then define the device-specific questions and a concrete completion criterion for inspecting serialized migration payloads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100