[Feature]: Text-generation failure popups should name the attempted model and link to Settings
Nessuno ha ancora preso questa issue.
- Lingua principale
- TypeScript
- Stelle
- 23k
- Fork
- 5.9k
- Merge medio
- 11h 14m
- PR unite (30g)
- 357
Descrizione
Context
#12651 confirmed that one-shot text generation (commit messages, PR content, branch names, thread titles) can fail opaquely: the Commit popup showed an unrelated stderr notice while the real cause was an unconfigured/unsupported text-generation model. #12652 improves what the error says (it now surfaces the CLI's own stdout error), but the popup still leaves the user to figure out where the fix lives.
Proposal
When one-shot text generation fails, make the error actionable by surfacing what the server already knows and offering the fix in place:
- Name the attempted model and its origin. E.g. if
textGenerationModelSelectionis unset and a fallback was used, say so explicitly: "No text generation model was configured, so the provider default (claude-haiku-4-5) was used." That is server-known information —resolveTextGenerationProvider()knows whether it fell back and to which slug. - Include a button/link that opens Settings at the text-generation model section. One click from the Commit popup to the place where the model is configured.
- Same treatment for title/branch failures, which today can fail silently (#5359) — a consistent actionable-failure path would cover the whole family.
Why
The failure mode in #12651 would have been a two-click self-fix from the Commit dialog itself: popup names the fallback model → button opens Settings → user picks a model their backend allows. Instead it took a full diagnostic session (captured spawns, extracted bundle source) to discover that textGenerationModelSelection was unset and that the fallback slug was being rejected by the backend.
The information needed for this already exists at the failure site; this is purely about presenting it.
Impact
Quality-of-life enhancement on top of the #12651 fixes.
[!NOTE]
🤖 GLM 5.3 Flash on behalf of iliasgws
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Esamina il popup Commit e il percorso resolveTextGenerationProvider(), usando #12651 e #12652 per il comportamento di errore esistente. Il lavoro è completato quando gli errori di generazione in un’unica esecuzione identificano il modello tentato e l’origine, forniscono un link alla sezione dei modelli di generazione del testo in Settings e applicano lo stesso percorso azionabile agli errori del titolo e del branch.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- typescript
- Ambito
- backend, frontend
- Tipo di issue
- Funzionalità
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Attiva
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 55/100