Submodule checkpoints block follow-up messages and new threads on Windows

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

维护者通常 1 天内回复

@juliusmarminge 已经在做这个了。

开始于 2026年11月20日。

  • #39784 来自 @juliusmarminge —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
git, typescript
领域
desktop, devtools

调研方向

Start with the checkpoint lock code in apps/server/src/orchestration-v2/CheckpointService.ts around lines 230–299, then review PR #30829, which introduced recursive checkpoint capture for initialized submodules. Use the proposed Chromium checkout on Windows to reproduce the delay after a turn and when starting a second thread. Done means checkpoint capture no longer blocks follow-up turns or another thread sharing the checkout; an open linked PR #39784 is already working on the issue.

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

描述

via-triage
What happened

After Claude or Codex displays its reply, T3 Code can keep the thread busy for another couple of minutes. Follow-up messages wait. A second thread using the same checkout can also stay on “Starting…” until the first thread’s checkpoint finishes.

Diagnosis

PR #30829 made T3 capture checkpoints recursively in initialized Git submodules. The post-turn capture holds a workspace lock that a new turn in the same checkout also needs. That explains why the delay affects both the finished thread and a second thread waiting to start.

PR #30829 · Checkpoint lock code

Evidence

On the same Windows checkout, recorded T3 Code checkpoint times rose from a median of 22.7 seconds on November 16 (3 captures) to 156.9 seconds on November 18 (24 captures). One later server trace showed a 146.6-second checkpoint with 157 submodule captures and 1,487 Git subprocess launches.

Steps to reproduce

Proposed reproduction with public Chromium.

  1. On Windows, use fetch chromium from depot_tools to check out public Chromium and its dependencies. Chromium checkout instructions
  2. Open the resulting src directory as a local project in T3 Code.
  3. Send a short prompt such as “Reply with OK.” Once the reply appears, try sending a follow-up.
  4. While the first thread is still busy, send a prompt in a second thread using the same checkout. Check whether it stays on “Starting…” until the first thread becomes idle.
Version

T3 Code Nightly 0.1.11-nightly.20261120.4979 (59651c1)

Environment

Windows desktop with a local backend. Observed with Claude and Codex.

Evidence

Related issues

The older large-repository checkpoint timeout is tracked separately in #3646.

Fix applied or workaround

No response

Filed by

Codex, GPT-6.2 Sol.

主要语言
TypeScript
星标
24.8k
派生
6.4k
平均合并
4 小时 29 分钟
30 天内合并 PR
488

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

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

pingdotgg/t3code 的其他 Issue

查看 pingdotgg/t3code 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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