8c9a940159
Implements Phase 6.9.5: atomic file writes and concurrent access safety for multiple pdftract processes sharing the same cache directory. ## Changes - Add `multi_process.rs` module with atomic write/read primitives - Atomic write protocol: temp file + fsync + rename - Reader protocol with corruption handling (deletes corrupt entries) - Startup cleanup of stale temp files (> 1 hour old) - fsync control via PDFTRACT_CACHE_NO_FSYNC env var - No distributed locks - tolerates duplicated work on first-miss races ## Module structure - `Writer`: Atomic cache entry writes via temp + rename - `Reader`: Safe reads with decompression and corruption detection - `cleanup_stale_temp_files()`: Startup cleanup for crash-recovered temp files ## Acceptance criteria met - [x] Concurrent extractors on same fingerprint: both succeed; no deadlock - [x] Reader sees fully-decompressable entry always (never torn write) - [x] 8 concurrent writers writing 8 different keys: all materialize correctly - [x] Corrupt entry on disk: treated as miss; entry deleted - [x] Stale temp file > 1 hour old: cleaned up at startup - [x] Stress test: 4 processes × 100 iterations → no errors ## Tests - 18 tests in `multi_process.rs` - 92 total cache module tests pass Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| examples | ||
| proptest-regressions/parser/lexer | ||
| src | ||
| tests | ||
| __test__.pdf | ||
| Cargo.toml | ||
| pdftract-core.cdx.json | ||
| README.md | ||
pdftract-core
The core Rust library for PDF text extraction. This crate provides the parsing, layout analysis, font encoding recovery, and text extraction primitives used by the CLI (pdftract-cli) and Python bindings (pdftract-py).
Cargo.lock Policy
This workspace checks in Cargo.lock at the repository root. This is unconventional for library crates—the Cargo Book historically suggested that only binary crates should check in lockfiles, allowing library consumers to resolve their own dependency versions.
pdftract departs from this convention for release reproducibility:
-
SLSA Level 3 provenance requires that every milestone tag produces byte-identical artifacts across builds. Without a checked-in lockfile, two runs of
cargo buildon the same commit can resolve different transitive dependency versions, producing different binary hashes. -
Multi-output artifacts—this workspace produces Rust crates (
pdftract-core,pdftract-cli), Python wheels (pdftract-py), and Docker images. All must be built from the same dependency tree. -
Supply-chain security—the lockfile pins checksums for all transitive dependencies, enabling
cargo auditto detect yanked or compromised crates. -
Downstream consumers can still ignore the lockfile if needed. Cargo allows
cargo build --frozenwith a local lockfile override, or consumers can vendor the crate with their own dependency resolution.
The tradeoff—occasional merge conflicts when PRs update overlapping dependencies—is worth the guarantee of reproducible releases. See CONTRIBUTING.md for the lockfile-update workflow.
Modules
parser: PDF spec parsing (xref, trailer, object streams, indirect references)font: Font encoding recovery, glyph name lookup, fingerprintinglayout: Page layout analysis, region segmentation, reading orderextract: Text extraction with provenance (bounding boxes, confidence scores)ocr: Tesseract integration for raster pages
Usage
use pdftract_core::{extract_text, ExtractOptions};
let options = ExtractOptions::default();
let result = extract_text("document.pdf", &options)?;
println!("{}", result.text);