Repository navigation
fix: honest check cadence, and a stats snapshot that fits the 30-min cache - #3
Merged
Merged
Conversation
…cache - F3: "Checks run every 5 minutes" -> scheduled every 5 minutes; GitHub runs scheduled jobs late, sometimes hours apart (seen 21 Nov 2026). - T2: the 20 Nov snapshot failed because the job wanted data under 10 min old while /api/stats is cached up to 30 min (revalidate 1800); all five reads were 21-25 min old. A query string does not bypass the cache (checked 21 Nov: same STALE copy). Accept up to 35 min and record the real generatedAt, read 8 times, and try once more at 18:17 UTC if the morning run recorded nothing. A missed day is never filled in later. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…skip ci] [upptime]
…kip ci] [upptime]
Eras256
approved these changes
Nov 22, 2026
Eras256
left a comment
Member
There was a problem hiding this comment.
AI-assisted comment (Claude)
The workflow change (35-min freshness, 18:17 UTC retry, skip if today's snapshot exists) and the README wording look right. Could you drop the 17 history/*.yml files from this PR? They are Upptime's own response-time data; the bot rewrites them on main and they will conflict. Then it's ready.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Arregla el job diario de /stats, que el 20 nov no guardó instantánea, y deja de prometer chequeos "cada 5 minutos" que GitHub no cumple. Es la parte de este repo de la revisión del sitio del 21 nov (F3 y T2).
Qué incluye
.upptimerc.yml: "Checks are scheduled every 5 minutes; GitHub runs scheduled jobs late, sometimes hours apart."uptime.ymldel 21-nov a las 10:24, 11:31 y 18:11 UTC (según la revisión).stats-archive.yml: acepta datos de/api/statsde hasta 35 min (antes 10) y guarda sugeneratedAtreal; 8 lecturas en vez de 5; un segundo intento a las 18:17 UTC que solo corre si la mañana no guardó nada (si el archivo del día ya existe, sale sin tocar nada).Por qué 35 min y no un parámetro en la URL
/api/stats kept serving data older than 10 minutes: en 5 intentos los datos tenían 21-25 min.apps/web/app/api/stats/route.ts) tienerevalidate = 1800yCache-Control: s-maxage=1800, stale-while-revalidate=3600. O sea, 30 min es su ventana normal, no 5.?snapshot=<fecha>. Lo probé hoy y no funciona: con y sin parámetro, Vercel devolvió la misma copiaX-Vercel-Cache: STALE,age: 2603, el mismogeneratedAt. Por eso usé la otra opción.Pruebas
yaml.safe_load).workflow_dispatchdesde aquí sin efectos: hace commit enmaster). Se puede probar con "Run workflow" después del merge; si ya existe la instantánea del día, el paso nuevo debe salir con "Today's snapshot already exists".Relacionado
El texto de /stats ("si un día falla, el hueco queda a la vista") va en Eras256/nirium-core-private#241, y el de /developers sobre la caché de 30 min va en el PR de docs/developers de esa misma revisión.
No hay merge desde aquí.
🤖 Generated with Claude Code