Sessions stuck permanently in "In use" state when not in use

未关闭
#4,845 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
shell
领域
cli

调研方向

首先重现报告的关闭场景,并检查 CLI 如何记录和重新加载会话的 "In Use" 状态。验证重新打开卡住的会话是否会改变该状态,然后确认因非正常关闭而遗留的会话不再保持隐藏,也不会触发错误的 "In Use" 警告。

由索引模型根据 Issue 内容生成。

描述

triage
Describe the bug

I have several sessions which were never marked no longer in use, and now do not show back up in the session list automatically. I have to /resume them every time, and accept a false warning that they're in use elsewhere. They've only ever been in use on one machine which shuts down regularly. This may be the cause of why the state was not cleaned up. However reopening these sessions does not reset the "In Use" flag, so the issue is permanent.

Affected version

GitHub Copilot CLI 1.0.84-6

Steps to reproduce the behavior

This is a guess

  1. Have a session
  2. Computer shuts down without cleanly terminating Agency
  3. Start agency, see session is still "In Use"
Expected behavior

Sessions should not be marked in use when they are not in use.

Additional context

No response

主要语言
Shell
星标
11.2k
派生
1.9k
平均合并
14 小时 16 分钟
30 天内合并 PR
6

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

github/copilot-cli 的其他 Issue

查看 github/copilot-cli 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。