Fix sporadic OSC parsing failures #51
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This issue was triggered recently when processing this change file (dated 2019-10-29): https://planet.openstreetmap.org/replication/day/000/002/603.osc.gz Including this fix in a new release might prevent some headaches 😄 |
|
@amatissart for that somebody would need to a) merge the PR, b) create a new release. Very unlikely to happen without some major changes. |
|
Tests pass, small change, looks good. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Removing explicit dependency on xerces and using the JDK version fixes the issue that has gone unfixed in the apache version of xerces since 2007, even though a fix is available.
See https://bugs.openjdk.java.net/browse/JDK-8080085
File tickling the issue
634.osc.gz