oxidecomputer / oxidecomputer/opte
Write up debugging doc
Open
Nobody has claimed this yet.
mvp
- Dominant language
- Rust
- Stars
- 77
- Forks
- 11
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 8
Description
Write up a debugging doc that focuses on the steps to take when looking for potentially lost packets.
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
The issue names no documentation file, test, or entry point. First identify where project documentation belongs and which lost-packet debugging scenarios should be covered; done means a focused guide describing the investigation steps is added there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100