oxidecomputer / oxidecomputer/crucible
crucible-agent needs to do more at the same time
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
Right now, the worker loop in crucible agent is single threaded.
Creating a region from a clone source can take a while, and this can backup
other agent commands that could be independent. Figure out a way to
make the agent do multiple things at once to prevent a large clone operation
from making a backlog of other commands.
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 the worker loop in crucible-agent and tracing how commands involving a clone source are handled. Determine how independent agent commands can run concurrently without a long clone operation creating a backlog. Done means the agent supports multiple in-flight operations while preserving correct command behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100