oasisprotocol / oasisprotocol/oasis-core
Node registration should succeed even on partial runtime failure
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Currently one runtime failing (typically cipher) in a multi-runtime setup, will cause the node to not submit a registration at all, even if the other runtimes are available. It may be worth having the node just omit the failing runtime(s) and submitting a registration anyway, as long as the node running in a degraded state is easy to diagnose.
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
No files, tests, or entry points are identified in the issue. Trace node registration and multi-runtime initialization first, then define how failed runtimes are omitted, how degraded operation is diagnosed, and how registration succeeds when at least one runtime remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100