You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running a batch process to extract images, and am seeing MuPDF errors on the console. I tried to use fitz.TOOLS.mupdf_warnings() to catch these in logging, and while it does make a log entry, it returns no info:
WARNING:MuPDF Error: on page 1,
I see one key error on the console: MuPDF error: format error: object out of range (158 0 R); xref size 153 - and in other batches I get other various errors (ICC Color, bad xref, etc.). What I need is to catch the document in question so we can review it. Using fitz.TOOLS.mupdf_warnings() gives me all the errors/warnings including the ones it was able to get past or not consider an error to send to the console. I see no TOOLS.mupdf_errors() or anything that might elevate that to only show errors.
Is there a way to get the actual errors back to be logged? I've tried various ways to redirect the info to logs from stderr and nothing seems to work. The key here is to even find which doc in a batch is the problem child, and I am able to get a group of docs using fits.TOOLS.mupdf_warnings() but then have no idea which was the real problem doc from that group.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm running a batch process to extract images, and am seeing MuPDF errors on the console. I tried to use fitz.TOOLS.mupdf_warnings() to catch these in logging, and while it does make a log entry, it returns no info:
I see one key error on the console: MuPDF error: format error: object out of range (158 0 R); xref size 153 - and in other batches I get other various errors (ICC Color, bad xref, etc.). What I need is to catch the document in question so we can review it. Using fitz.TOOLS.mupdf_warnings() gives me all the errors/warnings including the ones it was able to get past or not consider an error to send to the console. I see no TOOLS.mupdf_errors() or anything that might elevate that to only show errors.
Is there a way to get the actual errors back to be logged? I've tried various ways to redirect the info to logs from stderr and nothing seems to work. The key here is to even find which doc in a batch is the problem child, and I am able to get a group of docs using fits.TOOLS.mupdf_warnings() but then have no idea which was the real problem doc from that group.
Beta Was this translation helpful? Give feedback.
All reactions