Implemented
2
CONSUMER_STABILITY_DELAY of 5s is too low for network scanners
Source: paperless-ngx/paperless-ngx#13616 · opened by @janreinhardt
Description Default CONSUMER_STABILITY_DELAY of 5s is too low for network scanners; resulting failure is undiagnosable for users --- Description With a network scanner writing directly into the consume folder ("scan to network folder"), the default PAPERLESS_CONSUMER_STABILITY_DELAY of 5 seconds is not sufficient, and the resulting failure gives the user no indication of the actual cause. My scanner (HP OfficeJet Pro 9130e, scan to network folder) creates the target file immediately, but writes the actual content in bursts with pauses in between. Measured on a 6-page duplex scan: The longest pause during writing is 10.6 seconds, i.e. more than twice the default stability delay. The file therefore passes the stability check while it is still a 15-byte stub, and consumption starts on an incomplete file. Because the stub already contains a %PDF- header, it is detected as a PDF and passed to OCRmyPDF, which fails with: Two separate problems: 1. T…
No pledges yet. Be the first to back this.
Comments
Similar requests
Workaround for unreliable auto-rotation with scanners that embed /Rotate metadata
1 vote · 0 comments
[Feature] Optional removal of blank pages from the archive file (originals untouched)
1 vote · 0 comments
[Feature Request] expose django-allauth `SOCIALACCOUNT_REQUESTS_TIMEOUT` as a Paperless env var
2 votes · 0 comments
[Feature Request] Add a proxy env variable
1 vote · 0 comments
[Feature Request] Collate front/back image pairs into one document
1 vote · 0 comments
No comments yet.