Ryan
Ryan
Here is my use case: For [Custom Build Output](https://docs.docker.com/reference/cli/docker/image/build/#output) here, it is useful for me to take the build logs and test artifacts created during docker build and expose them...
@clalancette Unless you are strongly opposed, I'd like to deprecate some of these calls on rolling with `message(AUTHOR_WARNING ..)` and help submit PR's against the ROS core to remove these...
The plan sounds good.
Yes, that is what I had in mind.
Can we tag this as " good first issue" and hopefully someone new gets inspired to do the work?
> Shall, I commit the Tutorial first, followed by the improvements in the future commits. Also any recommendations on which ROS package example must I use to elaborate on this...
Looks like there's other resources from Autoware explaining similar things. https://autowarefoundation.github.io/autoware-documentation/main/support/troubleshooting/#died-process-issues
And, the CLI also supports it on `humble`: `ros2 topic pub /ap/cmd_vel geometry_msgs/msg/TwistStamped "{header: {frame_id: base_link}, twist: {linear: {x: .nan, y: .nan, z: .nan}, angular: {z: 0.01}}}"`
> Yeah, I think that is a reasonable thing to document; I'd enhance the table in https://docs.ros.org/en/humble/Concepts/Basic/About-Interfaces.html#field-types to add a "Note" column, or something like that. If you'd like to...