To be an official ROS Client Library we need to implement the complete ROS Slave API. This is a blocker for creating things like actions which leverage the API to double check things.
Please implement GetBusStats function as described in the API. Below is what has been done so far
http://wiki.ros.org/ROS/Slave_API
getBusStats(caller_id) is listed as not implemented here:
https://github.com/fetchrobotics/rosgo/blob/master/ros/node.go#L229
This causes issues for things like action servers which attempts to check which connections are publishing the action here (I believe):
https://github.com/ros/actionlib/blob/indigo-devel/src/actionlib/action_client.py#L589
As the Bus Stats are not published, the Ros Master cannot tell that this indeed the node with the publications (even though it does respond with the publications https://github.com/akio/rosgo/blob/e8dc1e3a310947bf298776545e7fe9ca1794fb2c/ros/node.go#L250)
To be an official ROS Client Library we need to implement the complete ROS Slave API. This is a blocker for creating things like actions which leverage the API to double check things.
Please implement
GetBusStatsfunction as described in the API. Below is what has been done so farhttp://wiki.ros.org/ROS/Slave_API
getBusStats(caller_id)is listed as not implemented here:https://github.com/fetchrobotics/rosgo/blob/master/ros/node.go#L229
This causes issues for things like action servers which attempts to check which connections are publishing the action here (I believe):
https://github.com/ros/actionlib/blob/indigo-devel/src/actionlib/action_client.py#L589
As the Bus Stats are not published, the Ros Master cannot tell that this indeed the node with the publications (even though it does respond with the publications https://github.com/akio/rosgo/blob/e8dc1e3a310947bf298776545e7fe9ca1794fb2c/ros/node.go#L250)