-
Notifications
You must be signed in to change notification settings - Fork 21
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
Error logged when circular buffer is empty #328
Comments
hey @rixius, I'm happy to add this. And would be even happier if I could entice you to open a PR :) it's nice to have others looking at the codebase. Let me know if you don't have time and I can add it myself |
Sure, I will. I assumed that I require permissions first to push code to the repository and create a PR. |
You would make the changes to a personal fork, and then create a PR. Happy to help get you started! Here are the steps you would need to follow:
If any of that is confusing, or if you just want me to do it :) let me know! |
I think I'm getting there, need another try... |
no, no you did great! you can open it again. if you're worried about the tests failing, don't worry, i think those were not your issue |
Thanks for the fix! |
CoreViewerLink._update_viewer() causes MM to log lots of errors when the circular buffer is empty:
2024-03-14T11:12:27.488274 tid17768 [ERR,Core] Error occurred in device CMMCore::getLastImage: Circular buffer is empty.
Solution: I added
before the try-statement to suppress this.
(Note that the error is visible only when logging is enabled which I often do.)
The text was updated successfully, but these errors were encountered: