Fix: Resolve infinite scan loop caused by problematic files hanging the worker during thumbnail generation.#21
Merged
Conversation
…he worker during thumbnail generation.
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.
When a scan encountered a corrupt or unreadable file, the worker could hang for up to 6 minutes (60s thumbnail + 300s fitz timeout) before moving on. If the worker was killed during that window — by the OS, container, or uvicorn — the book record was never committed to the database. On the next startup scan, the same file would be encountered again with no record of the prior failure, causing the same hang, the same worker kill, and the same restart — indefinitely