Handle libxml errors and warnings #350
Merged
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.
This PR improves how libxml errors are handled. Because there can be a lot of duplicate errrors I decided to count similar errors and show how often it occurred. The log output for multiple failure looks like this:
The problem with the handling before this is that nextcloud alwas logs the parameters of the function where an libxml error occurred. This meany in the above example the $html is logged a few hundred times.