Repository navigation
Tras un deploy con migración, 503 reintentable en vez de 500 (#134) - #135
Merged
Merged
Conversation
…ndose» en vez de 500 o de perder campos (#134) Tras desplegar la v9 (#131) el preview dio 500 en toda lectura ~5 min y un bloqueante abierto en esa ventana perdió su plazo: el Worker nuevo mandaba SQL con columnas que el Store viejo no tenía. Ahora cada write/batch lleva SCHEMA_VERSION y el Store la compara antes de tocar nada.
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.
Cierra #134.
Qué pasaba: al desplegar #132 el preview respondió 500 en toda lectura durante ~5 min (medido 22:40:55 → 22:45:49 -05,
no such column: default_choiceenwrangler tail), y un bloqueante abierto en esa ventana perdió su plazo en silencio.Arreglo: el Worker manda
SCHEMA_VERSIONen cadawrite/batch; unStoremás viejo no ejecuta nada y respondeunavailable(503, «el servidor se está actualizando»). El CLI ya reintenta 5xx enwait/watch. Vale desde el próximo deploy con migración: este mismo deploy no agrega columnas.Gates locales: typecheck 0 · test 0 (3 nuevos).