Try catch around cvtColor to avoid demosaicing src.empty() error #463
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
SteveMacenski
approved these changes
Sep 24, 2019
|
totally makes sense to me, I'll merge after CI |
|
Fastest PR -> merge I've seen in awhile :-) go circle CI |
|
Can this be backported to kinetic? I can make a new PR if that helps, it looks like the same change can be used as is. |
lucasw
added a commit
to lucasw/image_pipeline
that referenced
this pull request
Sep 23, 2020
JWhitleyWork
pushed a commit
that referenced
this pull request
Sep 23, 2020
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.
I've encountered a cvtColor opencv exception a few times, my camera driver is occasionally feeding bad images in but I'd rather the nodelets survive this than not handle the exception here.