oxidecomputer / oxidecomputer/steno
SEC seems to stop handling requests while inside SecStore
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 170
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
While working on oxidecomputer/omicron#6215, I ran into a bug (in my code) that caused the Nexus impl of SecStore to hang inside saga_update. While that was going on, requests to Nexus to list sagas hung. That was surprising. SecStore functions can be talking to storage over the network and the SEC should not become unresponsive while that's happening.
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 with the SecStore::saga_update entry point and the Nexus path for listing sagas. Reproduce a blocked storage call, then trace how SEC request handling is affected. Done means requests to list sagas remain responsive while SecStore operations are waiting on network storage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100