-
Notifications
You must be signed in to change notification settings - Fork 682
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
fix(fault_injection): fix empty hardware_id #814
Conversation
Codecov Report
@@ Coverage Diff @@
## main #814 +/- ##
=====================================
Coverage 9.66% 9.66%
=====================================
Files 908 908
Lines 56560 56560
Branches 6830 6830
=====================================
Hits 5465 5465
Misses 46593 46593
Partials 4502 4502
*This pull request uses carry forward flags. Click here to find out more.
Continue to review full report at Codecov.
|
377b7ff
to
36a7a65
Compare
@h-ohta |
@KeisukeShima You should set at least |
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.
@kenji-miyake Thanks for your comment.
LGTM
Signed-off-by: h-ohta <hiroki.ota@tier4.jp>
36a7a65
to
0c48923
Compare
Signed-off-by: h-ohta <hiroki.ota@tier4.jp>
Signed-off-by: h-ohta <hiroki.ota@tier4.jp>
Signed-off-by: h-ohta <hiroki.ota@tier4.jp>
Signed-off-by: h-ohta <hiroki.ota@tier4.jp>
Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
Description
In fault_injection node, all diags had empty hardware_id.
This is because hardware_id was replaced with the following value in updateEventDiag().
autoware.universe/simulator/fault_injection/include/fault_injection/diagnostic_storage.hpp
Line 42 in 377b7ff
I fix it.
Review Procedure
Confirm some fault injection diag has
![image](https://user-images.githubusercontent.com/9547070/165254577-7857cd31-0ca0-4375-bd40-ef820e262322.png)
fault injection
as hardware_id like following image in rqt_robot_monitor.Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.
In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.
Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.
After all checkboxes are checked, anyone who has write access can merge the PR.