Provide an asynchronous API for starting and handling instances
Metadata
Current evaluation
Triaged enhancement to add a non-blocking API for launching/handling provider instances, unblocking parallel multi-base builds. No async code has landed; core design (true async vs non-blocking) still undecided.
Suggested action: keep open
Reason: The issue is explicitly labelled 'Type: Enhancement, Status: Triaged' and was filed by maintainer lengau, and positive investigation confirms it is unfixed: a pickaxe search for 'async def' returned no commits, while craft_providers/provider.py still exposes a fully synchronous Provider ABC and both backends define `def start(self) -> None` (lxd_instance.py:560, multipass_instance.py:498). It should stay open because the downstream motivator, charmcraft#861 (CHARMCRAFT-655), is also still open. Confidence is held below the high range because the body explicitly leaves the central design open ('be that actually using `async` or just non-blocking') and the only comment is an autogenerated Jira-sync bot message (CRAFT-4777), so there is no agreed design spec or assignee, and repo search tooling returned intermittent errors during verification.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
62
Quick Win:
5
Complexity:
80
Confidence:
74
Actionability:
40
|
keep open | Triaged enhancement to add a non-blocking API for launching/handling provider instances, unblocking parallel multi-base builds. No async code has landed; core design (true async vs non-blocking) still undecided. | |
| stealth/space-bunny-alpha |
Impact:
65
Quick Win:
8
Complexity:
78
Confidence:
91
Actionability:
55
|
keep open | Triaged enhancement to add non-blocking instance startup and handling, enabling parallel builds. Provider APIs remain synchronous, and the linked Charmcraft parallel-build work is still open. | |
| stealth/space-bunny-alpha |
Impact:
64
Quick Win:
11
Complexity:
73
Confidence:
82
Actionability:
66
|
keep open | Add a triaged asynchronous or non-blocking provider API so instances can start and be handled concurrently, enabling parallel multi-base charm builds. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
75
Quick Win:
19
Staleness:
65
Complexity:
75
Confidence:
70
Support Request:
0
|
keep open | Enhancement to add asynchronous API for starting and handling instances in craft-providers to enable parallel builds. Triaged but inactive for 352 days. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
30
Complexity:
70
Confidence:
90
Support Request:
0
|
keep open | Request for an asynchronous API to start and handle instances without blocking, enabling parallel builds. Issue is triaged and linked to a Jira ticket. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
82
Complexity:
75
Confidence:
75
Support Request:
10
|
keep open | Enhancement to add a non-blocking API for instance management, enabling parallel builds. Triaged but inactive for ~10 months with no maintainer follow-up. |
Update history
No update history recorded yet.
Related work
-
Related To:
charmcraft#861
(confidence 93%)
Explicitly cited in the issue body as the motivating downstream work — parallel builds for multi-base charms — and also still open and unimplemented (CHARMCRAFT-655).
Related issues
No related issues found above the similarity threshold.