fix(deploy): maxDuration=60 en los route handlers (evita 504 por cold…#57
Merged
Merged
Conversation
… start de HF) El 504 (FUNCTION_INVOCATION_TIMEOUT) venía del límite por defecto (~10s) de las funciones serverless de Vercel: el backend en HF Spaces tarda ~31s en el cold start (el tier free duerme el Space) y 1-8s por request (conexión nueva por request, sin pool). Subir maxDuration a 60s en los 20 route handlers de /api/v2 evita el corte. La BD y el auth ya funcionan; era solo cuestión de tiempos. Complemento (fuera de código): un pinger para mantener el Space despierto + a futuro un pool de conexiones en el backend. Claude-Session: https://claude.ai/code/session_0198KfgRWvAM8BhiVz24uTok
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
3 tasks
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
1 participant
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.
… start de HF)
El 504 (FUNCTION_INVOCATION_TIMEOUT) venía del límite por defecto (~10s) de las funciones serverless de Vercel: el backend en HF Spaces tarda ~31s en el cold start (el tier free duerme el Space) y 1-8s por request (conexión nueva por request, sin pool). Subir maxDuration a 60s en los 20 route handlers de /api/v2 evita el corte. La BD y el auth ya funcionan; era solo cuestión de tiempos. Complemento (fuera de código): un pinger para mantener el Space despierto + a futuro un pool de conexiones en el backend.
Claude-Session: https://claude.ai/code/session_0198KfgRWvAM8BhiVz24uTok