github / github/app

Sessions dies after cancelling a response

Offen
#2,097 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Bugs
Vorherrschende Sprache
Keine Sprachdaten
Sterne
2.1k
Forks
153
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

After cancelling a response, or maybe after having a message queued and then cancelling the current response and the one from the queued message, the session stops responding. It just thinks forever with no output. Eventually a popup comes up suggesting to restart the session, but that doesn't work either. The only thing that works is quitting the app and reopening it, which takes clicking on it about 5 times and waiting 5 minutes. Also, in similar cases sometimes, messages get lost, and they show in the chat window, but the agent has no record of them.

---
| Field | Value |
| --- | --- |
| App version | 1.0.23 |
| OS | Windows 10.0.26310 |
| Theme | Noir Essence |
| Path | /chat |
| Tenure | Week 4 |

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start at the /chat entry point and reproduce the failure on Windows 10 after cancelling the current response and any queued response. Check the session's behavior when it remains stuck thinking, when restart is attempted, and when messages appear in the chat without reaching the agent; done means the session responds normally and queued messages are not lost.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Bereich
desktop
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Ruhig
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
42/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.