oasisprotocol / oasisprotocol/oasis-core
Store last component startup error and show in status
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
We should store the last component startup error that is preventing the component from successfully initializing. This error should then be shown in the component status, also the one exposed through the bundle manager interface.
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
Trace the component startup and status paths, then locate the bundle manager interface that exposes component status. Confirm how startup failures are currently handled and identify where the latest error can be retained. Done means the last startup error appears in both component status and the bundle manager view.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100