In productionProintermediateLaunch scope
The launch file places a node in the wrong namespace
Restore one robot's diagnostics without changing fleet-wide topic names.
Pairs with Nodes, names, and namespaces in ROS 2 Systems Debugging. Read the concept first, then diagnose it here.
Unlock this lab with ProOperator report
`/robot_2/diagnostics` is silent while `/diagnostics` receives duplicate publishers.
Ubuntu 24.04, ROS 2 Jazzy, Python and C++ nodes, browser telemetry workspace
System boundary
Trace only the relevant path.
launch GroupActiondiagnostics node/robot_2/diagnostics
How this lab works
You diagnose it — no command list.
Open the repair workspace and gather your own evidence in a real terminal. No diagnostic commands are handed to you — finding the fault is the exercise. Stuck? Progressive hints unlock inside the workspace.
Verification
Your repair must pass more than the visible symptom.
- Namespaced topic detected
- Global duplicate removed
- Hidden regression behavior
- Root cause explanation