oxidecomputer / oxidecomputer/omicron
need tooling for summarizing saga status
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
I debugged a saga hang today and it's annoyingly hard to figure out what's going on. With #1532 we have the whole DAG (including action names) in the database. We could do a lot to show you where it's hung.
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 issue #1532 and examining the saga DAG data described as being stored in the database, including action names. Determine what status information the proposed tooling should expose and how a user would identify where a saga is hung; the issue is complete when that scope and its expected output are defined and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100