SSH key password prompt doesn't appear when cloning repositories
Metadata
Current evaluation
SSH key passphrase prompt is overwritten by the 'Pulling' progress spinner during Git clone with brief verbosity. Untriaged, no maintainer response, inactive for ~18 months. Only a bot Jira-sync comment exists.
Suggested action: needs triage
Reason: The issue has no labels, no assignee, and no maintainer response — only an automated Jira-sync bot comment (CRAFT-2496). It is a well-structured bug report with clear reproduction steps identifying the craft-cli printer/spinner as the likely culprit, but no maintainer has assessed, labelled, or prioritised it. The underlying spinner system in craft-cli still exists, so the bug may still be reproducible, but it needs a maintainer to confirm and scope a fix.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
18.0
Staleness:
78
Complexity:
55
Confidence:
72
Support Request:
5
|
needs triage | SSH key passphrase prompt is overwritten by the 'Pulling' progress spinner during Git clone with brief verbosity. Untriaged, no maintainer response, inactive for ~18 months. Only a bot Jira-sync comment exists. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
35
Confidence:
85
Support Request:
15
|
close stale | SSH key passphrase prompts are overwritten by build progress messages during Git cloning, particularly with brief verbosity. Issue is untriaged and inactive for over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
88
Complexity:
40
Confidence:
80
Support Request:
10
|
close stale | Bug report describing SSH passphrase prompts being overwritten during repository pulls. Unlabelled with no maintainer interaction for over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
40
Confidence:
75
Support Request:
5
|
needs triage | SSH key passphrase prompts vanish during snapcraft repository pulls, causing an endless progress loop. Frequently occurs with --verbosity=brief or higher. Open for over two years with an internal Jira ticket created but no assigned fix. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.