oxidecomputer / oxidecomputer/omicron
omdb: Saga state tracking
Open
@jmpesp is already working on this.
Since Oct 5, 2023.
Debugging
development
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
During a debug session on 9/28, we jumped into a cockroachdb shell to manually query for saga state.
Of note:
- What sagas are running?
- What sagas failed?
- For sagas that failed, what were they? Where did they fail? What resources were they acting on?
This information would be a great candidate for an omdb query command -- if we could grab this info without using cockroach sql, we would.
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.
Assessment
This issue has not been assessed yet.