-
Notifications
You must be signed in to change notification settings - Fork 105
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
Avoid to raise error messages on iCub CAN-based robots unless they are real errors #661
Comments
I think it is important to avoid raising errors unless strictly, as otherwise we train the users to ignore the error messages, and probably the will ignore them even when they are critical and should be instead reported to https://github.com/robotology/icub-tech-support . To get an actionable definition of done, I think a reasonable target for 1.17/2020.08 is to have no error message on the iCubGenova01 on a run that is working as intended. |
A first step in this direction is #662 . |
I fully agree with this approach. |
Second related PR: #663 . |
Both PR have been merged 👍 |
On some robots (such as iCubGenova01) the default configuration files raise errors, even if the yarprobotinterface then works fine, see for example (I just collected these messages on the
iCubGenova01
):The text was updated successfully, but these errors were encountered: