-
Notifications
You must be signed in to change notification settings - Fork 935
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed flood of errors on startup for mesh_filter
#2550
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2550 +/- ##
==========================================
+ Coverage 60.19% 60.21% +0.02%
==========================================
Files 351 351
Lines 26492 26492
==========================================
+ Hits 15945 15950 +5
+ Misses 10547 10542 -5
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would there also be a way for it to not complain at all when it has not yet received data (as opposed to incorrect data)? (haven't looked at the underlying code)
I think you're describing exactly what I'm fixing. When it has not yet received a depth map, the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved provided you make the small change in the while loop
* fixed mesh_filter error spam on startup * infinite loop fix from Andy
* fixed mesh_filter error spam on startup * infinite loop fix from Andy
* fixed mesh_filter error spam on startup * infinite loop fix from Andy
Description
The mesh filter was producing a flood of errors when it started, which stopped after a subscriber connected to its output. This prevents these errors, and instead produces a trickle of debug messages. I cleaned up a few little things, too, while I was at it.
Checklist