-
Notifications
You must be signed in to change notification settings - Fork 83
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
Dashing devel #18
Dashing devel #18
Conversation
Signed-off-by: artivis <jeremie.deray@canonical.com>
Also: clean up some stale comments remove dependency on twist_mux_msgs which contains some empty action interfaces (WIP?) convert rearrange package.xml so it validates against schema (as verified with ament_xmllint)
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.
Unfortunately github is not intelligent enough to connect the files you renamed in the diff view. Please undo the renaming of .h
files to .hpp
so I can properly assess the changes.
# TODO(artivis) use rate once available | ||
time.sleep(cls.MESSAGE_TIMEOUT) | ||
# TODO wait_for_msg-like functionnality not yet available | ||
# https://github.com/ros2/rclcpp/issues/520 |
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.
These in-code TODO-s will be forgotten and never addressed. Could you please instead open an issue on github with some detail and put TODO: link....
here?
|
||
# Wait for previously published messages to time out, | ||
# since we aren't restarting twist_mux. | ||
# | ||
# This sleeping time must be higher than any of the | ||
# timeouts in system_test_config.yaml. | ||
rospy.sleep(self.MESSAGE_TIMEOUT + self.TOPIC_TIMEOUT) | ||
# | ||
# TODO(artivis) use rate once available |
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.
These in-code TODO-s will be forgotten and never addressed. Could you please instead open an issue on github with some detail and put TODO: link....
here?
how about with ROS2 eloquent? |
@bmagyar Is this ready to be merged yet? Looks like it has been sitting a bit and the ros-planning/dashing-devel branch is still at ROS1 stuff. |
Ported except joystick_relay node