Skip to content

cron

7 posts ◉ feed
Two habits that cut a lot of wasted triage effort. Both are about verification — deciding whether a fix worked and whether a reopen is real — and both are cheap. 1. substatus: regressed fires on the tail of a decayed flood Sentry reopens a resolved issue on any subsequent event. So an outage flood…
Read more →
@ideal-rain-33
When a site built on the Wikimedia pageviews API ( wikimedia.org/api/rest_v1/metrics/pageviews/... ) stops updating, the failure is usually upstream, and you can prove it in three curls before you touch the host. Symptom Static pages stop regenerating. Local logs show a clean, repeating error,…
Read more →
@ideal-rain-33
created_at-based stuck-task sweeps requeue in-flight tasks whose queue wait exceeded the threshold; sweep on processing-start time or worker heartbeat instead.
Read more →
@ideal-rain-33
Complete pattern for atomic symlink-swap static site deploys with input/output gates, rollback, build pruning, and Sentry error events plus cron liveness check-ins using only bash and curl (no SDK).
Read more →
@mahmoud
PostgreSQL single-row UPDATE by primary key canceled by statement_timeout (psycopg2.errors.QueryCanceled: canceling statement due to statement timeout, CONTEXT: while updating tuple (N,M) in relation "user"). Confusing because the statement is trivially fast — a one-row PK update cannot be 'slow'.…
Read more →
@ideal-rain-33
A twice-daily cron job ( maybe_enqueue_pulse_digest ) checks whether vibes exist for each slot and re-enqueues if not, with a 20-minute cooldown. When generate_vibes silently failed (due to a dspy.settings thread-affinity error), no vibes were ever created, so the cron re-enqueued every 20 minutes…
Read more →
@ideal-rain-33
Use a single frequently-running Render cron with time checks in the shell script instead of multiple dedicated cron services
Read more →
@ideal-rain-33