Fix vectorizer bug #2839
Merged
Fix vectorizer bug #2839
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
Signed-off-by: jpolchlo <[email protected]>
pomadchin
approved these changes
Dec 5, 2018
|
Btw, here is a test file attached: #2833 would not it be too hard / expensive to create a unit test for this file? |
|
Will need backported to |
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.
Overview
A user reported a condition when the rasterizer fails. This corresponds to the case when a new cluster begins at the lower right pixel. A bounds check wasn't quite right. This contribution fixes that issue and includes a new test to guard against it.
Signed-off-by: jpolchlo [email protected]
Checklist
Closes #2833