/ask and /btw answers go blank while the dialog stays open
Nessuno ha ancora preso questa issue.
- Lingua principale
- Shell
- Stelle
- 11.2k
- Fork
- 1.9k
- Merge medio
- 14h 16m
- PR unite (30g)
- 6
Descrizione
Describe the bug
When I use /ask or its /btw alias, answer text appears and then disappears without me pressing Escape or otherwise dismissing the response. The answer box stays open but becomes blank.
This is different from the expected disappearance after explicitly closing the temporary answer panel.
Affected version
1.0.83-5
Steps to reproduce the behavior
- Run Copilot CLI in the VS Code integrated terminal on Windows.
- In an existing conversation, submit
/ask <a short text-only question>or/btw <a short text-only question>. - Allow the answer to render and leave the panel open without dismissing it.
- Observe that the answer text can disappear while the panel remains open.
This has happened repeatedly in this environment, but a deterministic minimal reproduction has not yet been isolated. It is not established whether a resumed conversation or a concurrently running main task is required.
Expected behavior
Once answer text is displayed, it should remain readable in the open panel until I explicitly dismiss it. Finishing the response should not erase already displayed text.
Additional context
- OS/architecture: Windows, x64.
- Terminal: VS Code integrated terminal.
- Related closed report: github/copilot-cli#3759 describes blank
/askresponses on resumed chats in version1.0.61. Linking as possibly related, not as a confirmed duplicate or regression.
Suspected cause, not confirmed: Completion handling may replace an already streamed answer with an empty value when the final answer payload is empty or missing. A component-level simulation reproduces that failure mode, but the final payload from an actual failing live query has not been captured.
Local workaround status: The symptom was observed before modifying the installation. A temporary local UI workaround was subsequently applied to retain displayed and buffered streamed text when the final answer is empty or missing, while still using a nonempty final answer when provided. Its effectiveness against the original live symptom has not yet been confirmed; it is not an upstream fix or proof of the suspected cause.
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
Inizia riproducendo /ask e /btw in un terminale integrato di Windows VS Code, includendo, se possibile, conversazioni riprese e attività concorrenti. Confronta il testo trasmesso visualizzato e memorizzato nel buffer con il payload della risposta finale; l’attività è completata quando la risposta rimane leggibile mentre il pannello resta aperto, anche quando il payload finale è vuoto o mancante.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- shell, vscode
- Ambito
- cli
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Attiva
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 42/100