-
Notifications
You must be signed in to change notification settings - Fork 97
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
[jsk_fetch_startup] Publish diagnostics for important topics and nodes #1481
Conversation
wait for upstream release ?? |
51d90ec
to
89fccf1
Compare
Sorry, I force-pushed commits because knorth55#222 is force-pushed. |
We do not need to wait for upstream release. In fetch PC, we use jsk_robot/jsk_fetch_robot/jsk_fetch.rosinstall.melodic Lines 31 to 34 in 3d65836
In this branch, |
Cherry-pick knorth55#240 to publish diagnostics for more topics. |
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.
please resolve confllicts and pass CI
…ding edgetpu image topics
69b7cee
to
efaca8e
Compare
I force-pushed commits and resolved coflicts. However, the kinetic test fails. This is because
|
All tests have passed by adding |
please add following code to
the list of packages is taken from https://github.com/jsk-ros-pkg/jsk_robot/runs/7748594263?check_suite_focus=true and inteintinally removed gazebo packages, because it is not necessary for real application.
|
Thank you very much for your advice. |
This is refined version of #1460
Copied from knorth55#222
This depends on jsk-ros-pkg/jsk_common#1727
I want fetch to indicate that topic has not come or node does not exist.
For example, I want to check existence of
/audio
or/insta360
, whose publisher does not publish/diagnostics
.What I did in this PR is as follows: