The ACE Checker report not generated for common images epub file #192
Comments
coolharisha
changed the title
|
Thanks for the report. Does the error happen systematically with this EPUB sample and with the same file (common.jpg)? If the content is copyrighted, you could possibly send it to me privately via email (I will delete it as soon as the bug is identified), or I could also possibly sign an NDA. |
|
Yes. The image "common.jpg" has been used in many instances in different html files. The common image has been used around 102 instances inside the ePub. Please see the log. if this is OK to solve the issue. if ePub is required, i will check with the customer and get back to you. I assume that, the common image seems to be verifying multiple times inside the image folder in order to generate a report. But the only one common image exist in the folder, It failed to create a report. D:\Rajeshkumar\Works\Test\Ace>ace -o report --verbose D:\Rajeshkumar\Works\Test\Ace\ISBN_EPUB.epub Thanks in advance. Looking forward to receiving your thoughts. |
|
OK thanks, I will try to reproduce locally and will keep you informed! |
|
Unfortunately I couldn’t reproduce (with an EPUB containing 100 files referencing the same 10 MB image). I can dig deeper, but having access to your sample file would help a lot if you can ask your customer! 😄 |
|
@rdeltour Sorry for convenient, I have created mock-up ePub file for testing purpose. Please share your private mail id to [email protected]. i will share the ePub through your mail id. |
|
Hi We have the same issue on severals epub files. We can finally have the report if we launch two times the control on the same output directory, with "-f" argument. |
Addresses #192 but we still need to find out why the image fails to copy in the first place.
Addresses #192 but we still need to find out why the image fails to copy in the first place.
Addresses #192 but we still need to find out why the image fails to copy in the first place.
|
Looking at the commit history related to this issue, I am under the impression that this issue has been addressed and can therefore now be closed. It that correct? |
Please provide the following details if possible or relevant:
ace -vcommand).node -vcommand).info: Closing logs.
Re-run Ace using the --verbose option to enable full debug logging.] if the issue is a bug when running Ace: the error message as produced in the log file (you can enable debug logging with the
--verboseoption).The text was updated successfully, but these errors were encountered: