Use a different instance name when using the fetch service
Metadata
Current evaluation
A separate provider-instance name is requested for fetch-service runs so they do not destroy the normal build instance; the issue remains open, unlabelled, and without discussion.
Suggested action: needs triage
Reason: The body identifies a concrete failure mode—fetch-service runs destroy the normal provider instance—but does not specify the alternate name or provide a reproducer. The issue has no labels, comments, or maintainer response, and ProviderService.instance still computes one name with _get_instance_name before launching the environment, so it needs triage rather than closure.
Evaluated by: mr-cal-bot
Impact:
56
Quick Win:
19
Complexity:
45
Confidence:
87
Actionability:
61
Issue body
### What needs to get done
Use a different instance name when a command is using the fetch service
### Why it needs to get done
Lets us not destroy the normal instance name every time we try using the fetch service.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
56
Quick Win:
19
Complexity:
45
Confidence:
87
Actionability:
61
|
needs triage | A separate provider-instance name is requested for fetch-service runs so they do not destroy the normal build instance; the issue remains open, unlabelled, and without discussion. | |
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
20
Complexity:
25
Confidence:
70
Actionability:
65
|
needs triage | Issue requesting different instance name when using fetch service to avoid destroying normal instances. Unlabelled, no maintainer response. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
26
Staleness:
75
Complexity:
35
Confidence:
70
Support Request:
5
|
needs triage | Feature request to use a distinct provider instance name when the fetch service is enabled, preventing fetch-service runs from destroying the normal build instance. No maintainer response, labels, or linked PRs; last activity 465 days ago. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
80
Complexity:
20
Confidence:
90
Support Request:
0
|
needs triage | Technical request to use a different instance name with the fetch service to prevent overwriting the normal instance. Unlabeled, unassigned, and inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
85
Support Request:
10
|
needs triage | Enhancement request to use a separate instance name for the fetch service to preserve the main instance name. Unlabelled, no maintainer comments, inactive for over a year. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.