fix: truncate markdown image name context to prevent OS filename limit - #236
Open
gdccyuen wants to merge 1 commit into
Open
fix: truncate markdown image name context to prevent OS filename limit#236gdccyuen wants to merge 1 commit into
gdccyuen wants to merge 1 commit into
Conversation
When last_context (the preceding markdown text) is very long, the generated image filename exceeds the OS 255-byte limit and os.rename fails with OSError ENAMETOOLONG. Truncate to 60 chars after sanitization.
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.
What
When
last_context(the markdown text preceding an image) is very long, the generated image filename exceeds the OS 255-byte limit, causingos.renameto fail withOSError: [Errno 36] File name too long.Error
Fix
Truncate
image_name_contextto 60 characters after sanitization inbuild_markdown_image_name(). The context is cosmetic (used in the filename for debuggability), so truncation has no functional impact.Verification
Tested end-to-end with a 44-page PDF that triggered the original error — parsing succeeds after this fix.