oasisprotocol / oasisprotocol/oasis-core
Committee scheduler should schedule parallel compute committees
Open
Nobody has claimed this yet.
c:consensus/cometbft
c:registry
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
The committee scheduler should support scheduling parallel compute committees. The amount of parallelism could be a per-runtime parameter for now.
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
The payload names no file, test, or entry point. Start by locating the committee scheduler and the per-runtime configuration in the Go repository, then inspect existing scheduling tests if present. Done means parallel compute committees can be scheduled with a runtime-controlled parallelism value, with the behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100