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

Aperta
#39,714 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@juliusmarminge ci sta già lavorando.

Dal 20/11/2026.

  • #39784 di @juliusmarminge — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
git, typescript
Ambito
desktop, devtools

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
24.8k
Fork
6.4k
Merge medio
4h 29m
PR unite (30g)
488

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di pingdotgg/t3code

Tutte le issue di pingdotgg/t3code

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.