STRIP_SIZE messages #193
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Since a while I'm getting these messages in my logs:
It is one message per image to be converted to a PDF-page.
Do I have to do something?
Should I use the
--pillow-limit-break
parameter?Can I simply suppress these, and if so, how? I don't use
-v
so they should nt appear unless it's an error.Thank you for your report!
What logs are you seeing these messages in? Just on standard output when you run img2pdf?
I'm not sure why there is anything printed when img2pdf sets the tiff strip size. This is harmless and there should not be any warning about that.
Yes, I think stdout. It doesn't say.
I have a shell script which logs output and that script is called by a PHP-script, which in turn logs the output to a database.
I have queries that rely on the first line of the output, and that line have been 'taken over' by these PIL-messages.
I write my logging into a shell-script variable, which I echo at the end, after img2pdf. So .. img2pdf produces these messages and then, after the loop, I echo my log variable.
This is how my img2pdf command looks like:
The input can be 1 image, or 20+ images.
The system this is happening on:
Fedora Linux 38
,Linux 6.6.6-100.fc38.x86_64 on x86_64
withimg2pdf 0.4.4
.I don't understand how you get the output you describe with the command you are running. The messages you see are created by this line in the code:
So why are you getting these messages without running img2pdf with --verbose? Hrm....
I also got this error message on macOS Sonoma after a
brew upgrade
:Somewhere on Google I found user's using SUMO (https://github.com/eclipse-sumo/sumo/issues/13147) having the same problem. One suggestion was to copy
libtiff.6.dylib
tolibtiff.5.dylib
, which I did. That seems to have resolved the issue.