oxidecomputer / oxidecomputer/crucible
How should `Upstairs` respond to `YouAreNoLongerActive`?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
See discussion here
Right now, we disable that specific client; however, the Upstairs as a whole remains active.
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
Start by reading the discussion linked from this issue, especially the referenced pull request comment, then inspect the handling of Upstairs and YouAreNoLongerActive. The work is complete when the intended response is agreed upon and the implementation matches that decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100