fix(core): preserve OCR continuity for blank pages#135
Merged
Conversation
|
🎉 This PR is included in version 2.19.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Why
Ragmir previously treated empty Tesseract output as a missing page payload. A valid scanned PDF page with no recognizable text could therefore stop a complete reindex, a case that is especially visible when refreshing an existing project after an upgrade.
What changed
Upgrade continuity
Users upgrading an existing Ragmir project can run the normal upgrade diagnostic and reindex flow without excluding a document only because it contains a blank or image-only page. Source files remain untouched, the current atomic index-generation behavior is preserved, and this patch introduces no configuration or index-format migration.
Validation