Sign up
View stargazers13Sign up

[codex] Prevent background Git fetches from leaking temp packs#3537

closed7
main
codex/fix-git-fetch-temp-pack-leaks
openedJun 23, 2026byJJulius Marminge
100+ files changed
View on GitHubTwo-way sync enabledPR last imported 3d ago
16 unresolved threads · Jump to file
Selected thread: apps/server/src/resourceTelemetry/Model.ts:396 — 🟡 **Medium** `resourceTelemetry/Model.ts:396` When an Electron metric arrives without a matching native sample, `mergeProcesses` inserts a synthetic process keyed by `metric.creationTimeMs` at line 387. A subsequent native sample for the same PID that passes the 2-second tolerance check (line 391-395) is then keyed by its own different `startTimeMs`. Because `processIdentityKey` (line 85-87) requires exact equality, the same live process is recorded as both an exit (old identity) and a start (new identity), which resets `firstSeenAt`/deltas and inflates the `processStarts`/`processExits` lifecycle counters. This happens whenever desktop telemetry arrives before the native monitor first observes the Electron process. <details> <summary>🚀 Reply "<strong>fix it for me</strong>" or copy this <strong>AI Prompt</strong> for your agent:</summary> ```text In file @apps/server/src/resourceTelemetry/Model.ts around line 396: When an Electron metric arrives without a matching native sample, `mergeProcesses` inserts a synthetic process keyed by `metric.creationTimeMs` at line 387. A subsequent native sample for the same PID that passes the 2-second tolerance check (line 391-395) is then keyed by its own different `startTimeMs`. Because `processIdentityKey` (line 85-87) requires exact equality, the same live process is recorded as both an exit (old identity) and a start (new identity), which resets `firstSeenAt`/deltas and inflates the `processStarts`/`processExits` lifecycle counters. This happens whenever desktop telemetry arrives before the native monitor first observes the Electron process. ``` </details>
0 / 100 viewed100 files changedLine totals unavailable

apps/server/src/diagnostics/ProcessDiagnostics.ts · File comment

M
macroscopeappBotJul 29, 2026

🟡 Medium

https://github.com/pingdotgg/t3code/blob/58340604f0b7967e7a5a3e532993f3443442d14e/apps/server/src/diagnostics/ProcessDiagnostics.ts#L1

The read function filters only the server PID out of snapshot.processes, so independent Electron roots and the resource-monitor process are returned as server child processes. This inflates processCount, totalRssBytes, and totalCpuPercent, and their depth is clamped to 0 via Math.max(0, entry.depth - 1) even though they are not descendants of the server. The filter at line 78 should restrict the list to the server/backend descendant tree rather than all telemetry processes.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:
text
1In file @apps/server/src/diagnostics/ProcessDiagnostics.ts around line 1:
2
3The `read` function filters only the server PID out of `snapshot.processes`, so independent Electron roots and the resource-monitor process are returned as server child processes. This inflates `processCount`, `totalRssBytes`, and `totalCpuPercent`, and their `depth` is clamped to `0` via `Math.max(0, entry.depth - 1)` even though they are not descendants of the server. The filter at line 78 should restrict the list to the server/backend descendant tree rather than all telemetry processes.