Silently ignore pingImage failure and load number of pages lazily #187
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For some reason, pingImage fails for me when I try to convert a small pdf (latex generated formula), with the general message "Failed to read the file". However, when the
pingImage
method is not used or its exception catched, the conversion completes just fine for me. As it has been added as speedup only in b0d7ab0, I am confident we can safely ignore its failure. If something really is wrong, it will throw later anyways.That is why I propose to silently catch the
pingImage
method, but also to move the whole number of page retrieval outside of the constructor. Its result value is never used until explicitly called using eithersetPage
,getNumberOfPages
orsaveAllPagesAsImages
. So, why retrieve it when it might not even be used?Note that this might be considered BC-incompatible: I changed the
$numberOfPages
class property to private, to enforce the usage of the already existing getter method, which triggers the lazy load.