Stage cloud PDF sources before synchronous parsing - #11
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.
Seekable cloud PDF streams were passed directly to PdfPig, whose synchronous byte reads and random seeks can repeatedly fetch remote ranges during page batches. Stage those streams asynchronously to bounded temporary files before parsing; continue to reuse local file and memory sources by default.
Expose staging mode, copy-buffer size and temporary directory through FileContextOptions. Return pooled buffers, keep temporary sources private on Unix, and clean up files and inputs after completion, cancellation, size rejection and read failures. Release 1.0.14 through the existing main-branch Release workflow.
Validation: 33 focused PDF tests and all 183 tests passed; line coverage 95.65%; Release build, format verification and pack passed; no direct or transitive NuGet vulnerabilities. Regression inputs use real files behind an async-only seekable stream, including a large source and parser/rendering calls after staging.