Christophe Bedard

Oh I see! I did obviously have VS 2019 installed when I tested the link for #2123. We need a proper solution then.

> * [Building-ROS-2-with-Tracing-Instrumentation](https://docs.ros.org/en/rolling/How-To-Guides/Building-ROS-2-with-Tracing-Instrumentation.html) (merge with: [ros2_trace_and_analyze](https://ros-realtime.github.io/Guides/ros2_tracing_trace_and_analyze.html)) I wouldn't merge these two. Keeping the "Building ROS 2 with Tracing Instrumentation" as a standalone guide allows us to link to _just that_...

@nightduck I think you mentioned during a RTWG meeting a few weeks ago that you were working on porting/moving the "How to use ros2_tracing to trace and analyze an application"...

> but we're not submitting a pull request until we've finished other modifications we're making. The "How to use ros2_tracing to trace and analyze an application" tutorial doesn't really need...

@nightduck do you want to do it, or should I?

RHEL 9 has LTTng 2.12, so we might have to wait until all Linux platforms have >=2.13.

ROS 2 Foxy is not supported anymore. You should try with a supported distro: https://docs.ros.org/en/rolling/Releases.html#list-of-distributions

Since most `topic_tools` nodes share the same base node class (which has an input topic and output topic) and support providing input/output topic names as parameters through the CLI (e.g.,...

You're right, `mux` does subscribe to multiple input topics. Changing `ToolBaseNode` to support N input topics and M output topics is worth a try. Since `ToolBaseNode` currently only creates an...

This might be related to #377