jedarden/pdftract
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(bf-3bnao-step4): document pdftract verification failure

Browse source 
Exit code: 1 (failure)
Error: Failed to extract PDF
No JSON output produced
SHA256 mismatch on fingerprint-match.pdf

This bead documents the failure and should NOT be closed until
the root cause is identified and fixed.
This commit is contained in:
jedarden 2026-07-06 19:22:52 -04:00
parent 50d443d86e
commit d6f33cc0dc
1 changed files with 45 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

50
notes/bf-3bnao-step4.md
View file

@ -20,6 +20,31 @@
- **Actual:** Error message present: "Failed to extract PDF"
- **Status:** ❌ FAIL
## Additional Test Results
### Test Run 2 (Direct verification)
```
Command: cargo run -- extract tests/fixtures/encoding/fingerprint-match.pdf --json -
Exit Code: 1
Error: Failed to extract PDF
```
**Status:** ❌ FAILED - Same error reproduced
### File Integrity Check
- **Expected SHA256:** bd9a3533c0f31fb20bf5532fcff4cb2ae399f8d2e22ea1d09538837410544c4a
- **Actual SHA256:** 2eaeba307f622ca6b6d6174bd1bdd9a1310268c7d4f101d3e2a222ba8b719689
- **Status:** ❌ MISMATCH - File has been modified or corrupted
### File Header Inspection
```
%PDF-1.4
1 0 obj
<<
/Type /Catalog
/Pages 2 0 R
```
**Status:** ✅ PDF header appears valid
## Command Output Summary
From step3 (bf-32by8-step3.md):
@ -38,10 +63,25 @@ Error: Failed to extract PDF
## Conclusion
The pdftract command did **not** complete successfully. The PDF extraction failed with exit code 1 and error message "Failed to extract PDF". This failure needs to be investigated further. The issue could be:
The pdftract command did **not** complete successfully. The PDF extraction failed with exit code 1 and error message "Failed to extract PDF". The failure has been reproduced across multiple test runs.
1. The PDF file `tests/fixtures/encoding/fingerprint-match.pdf` may be corrupted
2. There may be a bug in the PDF extraction code
3. There may be missing dependencies or environmental issues
### Key Findings
**This bead should NOT be closed** until the root cause is identified and fixed, and the command succeeds with exit code 0.
1. **File Integrity Issue:** The SHA256 hash of `encoding/fingerprint-match.pdf` does not match the expected value in `tests/fixtures/PROVENANCE.md`
- Expected: `bd9a3533c0f31fb20bf5532fcff4cb2ae399f8d2e22ea1d09538837410544c4a`
- Actual: `2eaeba307f622ca6b6d6174bd1bdd9a1310268c7d4f101d3e2a222ba8b719689`
2. **PDF Structure:** Despite the hash mismatch, the file header appears valid (`%PDF-1.4`), suggesting the file is not completely corrupted but has been modified
3. **Reproducible Failure:** The extraction failure is consistent across multiple attempts, ruling out transient issues
### Root Cause Analysis
The most likely cause is that the PDF file `tests/fixtures/encoding/fingerprint-match.pdf` has been modified or corrupted. The SHA256 mismatch indicates the current file on disk differs from the version recorded in PROVENANCE.md. This could explain why pdftract fails to extract it.
**This bead should NOT be closed** until:
1. The correct `fingerprint-match.pdf` file is restored or
2. The root cause of the extraction failure is identified and fixed or
3. The pdftract code is updated to handle this file variant
The verification results are documented but the acceptance criteria are not met.