Repository navigation
Share conversion deadlines across dispatch and workers - #17
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Peer attempts previously received fresh timeouts even after request setup or a slow primary had consumed the route budget, leaving too little time to persist outcomes. Share each 300-second invocation budget across dispatch/failover and database calls, reserve recording/signing time, and forward an optional authenticated absolute deadline through wake-up and backend processing.
Workers check the remaining budget around conversion, PDF/archive stages, OCR and Storage I/O. Propagate request context into existing upload/read workers, shrink subprocess/network timeouts, and return explicit 504 deadline errors rather than partial success. Legacy callers/backends remain compatible; durable job lifetime, retries/leases, concurrency, SQL, retention and full-output contracts stay unchanged. Native parsers and lock waits remain cooperatively checked rather than forcibly interrupted.
Local tests: 270 frontend, 160 normal/PDF, 104 archive and 11 focused OCR/capacity checks passed, along with lint, production build and dictionary/SQL/blog consistency. Covers slow failover, transport/body budgets, old-backend behavior, auth precedence, concurrent isolation, slow reads/writes, no partial PDF/ZIP success, OCR timeout and image cleanup. All seven CI jobs passed before/after merge, including full Linux OCR.
Released at
9131a2ac6163f22b630b008b40accb482ed3e0b3: all six Vercel production statuses succeeded, and every N/O/Z worker reported the exact revision and readiness. Thirty auth/deadline/legacy protocol checks, eight workbook/ZIP equivalence probes, four post-release Storage conversion/download/recovery jobs and 20 HTTP/redirect checks passed. Multi-stage acceptance includes actual OCR, image-ZIP/project merge and scanned-PDF merge. Six generated Storage jobs across pre/post/multi-stage probes follow existing retention; cleanup was not manually invoked. All pools were 2/2 ready. See docs/LLMISER_SHARED_DEADLINES.md for evidence and cooperative-cancellation/capacity limits.