ros_comm
ros_comm copied to clipboard
ROS communications-related packages, including core client libraries (roscpp, rospy, roslisp) and graph introspection tools (rostopic, rosnode, rosservice, rosparam).
coverage [stores a tuple](https://github.com/nedbat/coveragepy/blob/ff59658edcc0fbc3dd7f247cd63ec6a44c019410/coverage/debug.py#L303) in `sys.modules` (which does not have `__name__`)
Fixes #2194 by adding an optional `timeout` parameter to `is_online()`. Defaults to `None` to preserve existing behaviour. The blocking code seems to come from deep within xmlrpclib, so the easiest...
### Issue I've been having issues getting a remote node to detect when master is down (detailed [here](https://answers.ros.org/question/389077/remote-node-doesnt-shut-down-when-connection-with-master-is-lost/)) which I've pinpointed down to the `rosgraph.is_master_alive()` call I'm using to check...
It appears at least this function rospy.loginfo has a memory leak, maybe others like logerror as well. If I comment it out, my memory stays flat. The application is just...
Solution for #2189. This fixes an issue where sometimes caches do not receive the first message on the subscribed topic, if the message arrives immediately after initialising the subscriber. This...
Sometimes when using multiple caches in the same node on the same topic, which is latched, the expected behaviour of the cache does not happen. What I expect to happen...
If ros_comm has been build in Debug-mode (which is catkins default), and one starts roscore, two rosout-process are launch, which taking up about 80% to 160% cpu load. The reason...
Return the exit code to the caller of a required process at least for a regular parent launch process, child and remote processes need looking at. May solve https://github.com/ros/ros_comm/issues/919
Testing on latest fuerte. When Publisher.unregister() is called, the following error starts popping up periodically (from another thread): {{{ [WARN] [WallTime: 1332168660.580924] Could not process inbound connection: ... }}} This...