oxidecomputer / oxidecomputer/propolis
destination could log device state payload if import fails
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
In debugging some recent issues with device emulation, I noticed that the device payload sent as a part of migration is not logged on the destination side if the import fails. We do have the payload from source logs, but it would be nice if, for debugging purposes, we also logged the payload that caused the failure in the destination logs.
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 tracing the device-state migration import path and the destination-side handling of failed imports. The change is complete when the payload that caused an import failure is included in destination logs, while preserving the existing source logging behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100