Queued prompts occasionally remain stuck after the session becomes idle
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 52/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 領域
- cli
研究方向
先在互動式 Copilot CLI 工作階段中,於使用中的工作執行時按下 Ctrl+Q 來重現問題,接著檢查佇列管理器以及轉換至閒置工作階段的流程。確認工作階段變為閒置後,佇列中的提示會自動傳送,且佇列管理器會在需要時提供「Send now」的備援選項。
由索引模型根據 Issue 內容生成。
描述
Describe the bug
Queued prompts are not dequeued consistently. Occasionally, after pressing Ctrl+Q to enqueue a prompt while Copilot CLI is busy, the prompt remains listed under Queued (1) Ctrl+Q to manage even after the session becomes idle.
The queue manager allows the queued prompt to be edited or deleted, but it does not provide a "Send now" action, and the prompt never dispatches automatically. Deleting the queued prompt and submitting the same text manually works.
Affected version
1.0.83-3
Steps to reproduce the behavior
- Start an interactive Copilot CLI session and submit a prompt that keeps the session busy.
- While it is busy, type another prompt and press Ctrl+Q to enqueue it.
- Wait for the active work to finish and for the session to become idle.
- Observe that, intermittently, the status continues to show
Queued (1) Ctrl+Q to manageand the prompt is never sent. - Press Ctrl+Q to manage the queue. The prompt can be edited or deleted, but there is no option to send it immediately.
- Delete the queued prompt and submit the same text manually; it sends successfully.
This is intermittent and does not happen for every queued prompt.
Expected behavior
A queued prompt should automatically dispatch when the session becomes idle. The queue manager should also provide a "Send now" action as a fallback when automatic dequeueing does not occur.
Additional context
- Operating system: Windows
- Reproducibility: Intermittent
- UI remains responsive; queued prompts can still be edited or deleted.
- Manually resubmitting the same prompt succeeds.
- 主要語言
- Shell
- 星號
- 11.2k
- 分支
- 1.9k
- 平均合併
- 14 小時 16 分鐘
- 30 天內合併 PR
- 6
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
github/copilot-cli 的其他 Issue
-
triage
難度 2/5 1-3 小時 新手友好度 75/100
github/copilot-cli#4932 ·
-
triage
難度 2/5 1-3 小時 新手友好度 78/100
github/copilot-cli#4909 ·
-
triage
難度 2/5 1-3 小時 新手友好度 76/100
github/copilot-cli#4906 ·
-
triage
難度 2/5 1-3 小時 新手友好度 72/100
github/copilot-cli#4848 ·
-
area:agents area:mcp
難度 2/5 1-3 小時 新手友好度 72/100
github/copilot-cli#4729 ·
查看 github/copilot-cli 的全部 Issue
相似的 Issue
-
enhancement
難度 2/5 1-3 小時 新手友好度 65/100
-
tooling
難度 2/5 1-3 小時 新手友好度 75/100
-
難度 2/5 1-3 小時 新手友好度 70/100
openSUSE/python-rpm-macros#219 ·
-
難度 2/5 1-3 小時 新手友好度 70/100
YunoHost-Apps/adguardhome_ynh#258 ·
-
steam-short-session-tracker: incorrect registry backup path resets settings during automatic repair 未關閉
難度 2/5 1-3 小時 新手友好度 80/100
ValveSoftware/SteamOS#2829 ·