00
In productionProintermediateAI-assisted debugging
The AI's QoS fix is half right
Complete the QoS alignment the LLM started.
Pairs with Debugging ROS with AI in the loop in Use AI efficiently with ROS 2. Read the concept first, then diagnose it here.
Unlock this lab with ProOperator report
The subscriber still gets nothing after the AI changed only reliability.
Ubuntu 24.04, ROS 2 Jazzy, rclpy/rclcpp, an LLM coding assistant + MCP
System boundary
Trace only the relevant path.
- 01publisher durability→
- 02QoS match→
- 03subscriber durabilityOUT
02
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
Pass more than the visible symptom.
- Durability matches
- Latched data arrives
- Hidden regression behavior
- Root cause explanation