ROB: Deal with wrong size for incremental PDF files #3495
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
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3495 +/- ##
=======================================
Coverage 97.09% 97.09%
=======================================
Files 56 56
Lines 9658 9664 +6
Branches 1748 1750 +2
=======================================
+ Hits 9377 9383 +6
Misses 168 168
Partials 113 113 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
stefan6419846
added a commit
that referenced
this pull request
Oct 19, 2025
## What's new ### Bug Fixes (BUG) - Fix handling of zero-length StreamObject (#3485) by @Likend ### Robustness (ROB) - Deal with wrong size for incremental PDF files (#3495) by @stefan6419846 - Improve handling for malformed cross-reference tables (#3483) by @stefan6419846 ### Developer Experience (DEV) - Use released Python 3.14 by @stefan6419846 - Use Mapping instead of dict in type hint of update_page_form_field_values (#3490) by @stefan6419846 [Full Changelog](6.1.1...6.1.2)
OpenNingia
pushed a commit
to OpenNingia/pypdf
that referenced
this pull request
Oct 23, 2025
OpenNingia
pushed a commit
to OpenNingia/pypdf
that referenced
this pull request
Oct 23, 2025
## What's new ### Bug Fixes (BUG) - Fix handling of zero-length StreamObject (py-pdf#3485) by @Likend ### Robustness (ROB) - Deal with wrong size for incremental PDF files (py-pdf#3495) by @stefan6419846 - Improve handling for malformed cross-reference tables (py-pdf#3483) by @stefan6419846 ### Developer Experience (DEV) - Use released Python 3.14 by @stefan6419846 - Use Mapping instead of dict in type hint of update_page_form_field_values (py-pdf#3490) by @stefan6419846 [Full Changelog](py-pdf/pypdf@6.1.1...6.1.2)
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.
There are incremental PDF files in the wild which define a too small
/Sizein the final part.I have initially seen this with an incremental PDF file where no object has been updated and the
/Sizeset to 1, although the previous/Sizewould be 24. During analysis, it turned out that loading the same PDF file in incremental mode would not fail, but with/Size 2(due to subtracting 1 in this path).I could not see any negative side effects when changing this for non-incremental writer mode in pypdf, thus the assertion appears to be too strict here. Instead, replace the assertion with a proper error/warning message and report proper errors on an index error when attempting to flatten the faulty PDF in incremental mode.