Use a different instance name when using the fetch service
Metadata
Current evaluation
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.
Suggested action: needs triage
Reason: The issue is unlabelled with zero comments and no maintainer acknowledgement in 543 days, so it has not been triaged. The underlying concern appears partially addressed: commit e931a597 'wipe existing instances when using the fetch-service' and the current _get_instance_name() in services/provider.py already incorporate the work_dir inode and platform into the instance name, but there is no explicit fetch-service-specific naming suffix, so the request may still be valid. A maintainer should confirm whether the current naming scheme satisfies the goal before closing or implementing.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
26.0
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. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
15
Confidence:
75
Support Request:
0
|
close stale | Preserve default instance name when using fetch service commands by implementing separate instance naming. Open issue with zero comments and over two months of inactivity. Requires triage and assignment. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.