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

Aberta
#39,714 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@juliusmarminge já está trabalhando nisso.

Desde 20/11/2026.

  • #39784 de @juliusmarminge — aberto

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
30/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Stack de tecnologia
git, typescript
Domínio
desktop, devtools

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
24.8k
Forks
6.4k
Merge médio
4h 29min
PRs com merge (30d)
488

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de pingdotgg/t3code

Todas as issues de pingdotgg/t3code

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.