tilt

# Tilt ## First Action: Check for Errors Before investigating issues or verifying deployments, check resource health. Run **errors first**, separately from pending/in-progress — otherwise real failures get buried in 20+ pending lines: ```bash # 1. Errors only — surface the buildHistory[0].error so you see WHY, not just THAT tilt get uiresources -o json | jq -r '.items[] | select(.status.runtimeStatus == "error" or .status.updateStatus == "error") | "\(.metadata.name): runtime=\(.status.runtimeStatus) update=\(.status.updateStatus)\n reason: \((.status.buildHistory[0].error // "(no buildHistory error; check tilt logs)") | gsub("\n"; " ") | .[0:240])"' # 2. In-progress and pending — informational; an in-progress build may flip to error any moment tilt get uiresources -o json | jq -r '.items[] | select(.status.updateStatus == "in_progress" or .status.updateStatus == "pending" or .status.runtimeStatus == "pending") | "\(.metadata.name): runtime=\(.status.runtimeStatus) update=\(.status.updateStatus)"' # 3. Docker-compose container health — MISSED by the error filter above. # An `Up (unhealthy)` compose container keeps runtimeStatus=ok/update=ok, so # queries 1-2 never flag it; the red UI badge comes from healthStatus here. tilt get uiresources -o json | jq -r '.items[] | select(.status.composeResourceInfo.healthStatus == "unhealthy") | "\(.metadata.name): compose healthStatus=unhealthy (HEALTHCHECK failing — service may still be up)"' # 4. Quick status overview tilt ...