Repository navigation
fix(ocr): allow queued jobs to wait thirty minutes - #46
Merged
Merged
Conversation
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.
Queued screenshots can expire before recognition starts when the single-worker service is busy. Extend the queue deadline from 10 to 30 minutes, retaining bounded expiration and the existing result delivery behavior.
The paired platform change (OWBastion/owbastion.com#382) extends stale recovery from 15 to 45 minutes. Deploy the platform change first, then deploy this OCRKit image so long-waiting jobs can still deliver results.
Validation: all 427 Python tests passed. Queue boundary coverage checks admission beyond the old deadline, recognition just before 30 minutes, and expiration at 30 minutes. Recognition throughput remains constrained by the host resources; no production deployment or retry has been performed.