Code · pingdotgg/t3code

fix(server): a failed local status read no longer leaves stale Changes totals

Publishing the remote counts after a failed local read cached them, so the
next poll saw unchanged counts and skipped the local read for good. Let the
failure propagate so nothing is published and the next poll retries.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2a04d5e1caJulius Marminge committed on 10/22/2026, 7:38:48 AMparentc807538

Checks

Some checks failed

CodeRabbitGitHub
Review completed
Successful
Vercel – t3code-marketingGitHub
Skipped - Not affected
Successful
Native fingerprint diffGitHub
Cancelled
CheckGitHub
Successful
Native fingerprint diffGitHub
Successful
RustGitHub
Skipped
Mobile Native Static AnalysisGitHub
Skipped
Test WebGitHub
Skipped
Release SmokeGitHub
Successful
TestGitHub
Successful
Build and TypecheckGitHub
Successful
Sync PR size label definitionsGitHub
Skipped
Label PR sizeGitHub
Successful
Label PR 23422GitHub
Successful
Deploy web previewGitHub
Skipped
EAS PreviewGitHub
Skipped
Macroscope - Effect Service ConventionsGitHub
Skipped
Test Server 3GitHub
Successful
Test Server 6GitHub
Successful
Test Server 7GitHub
Successful
Test Server 8GitHub
Successful
Test Server 5GitHub
Successful
Test Server 1GitHub
Successful
Test Server 4GitHub
Successful
LintGitHub
Successful
Test Server 2GitHub
Successful
ChangesGitHub
Successful
Prepare PR size configGitHub
Successful
Collect PR targetsGitHub
Successful
Macroscope - Approvability CheckGitHub
Neutral
Macroscope - Correctness CheckGitHub
Successful

2 files changedLine totals unavailable