NVIDIA-ISAAC-ROS / NVIDIA-ISAAC-ROS/isaac_ros_common
How to run Python nodes in debugger mode inside Isaac ROS dev container?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 317
- Forks
- 227
- PR merge metrics
- No merged PRs in 30d
Description
Hi Isaac ROS team,
I'm currently developing Python-based ROS 2 nodes inside the isaac_ros_dev-x86_64 container, using the run_dev.sh environment.
I'd like to debug my ROS 2 Python nodes using pdb or the Visual Studio Code Python debugger. However, I’ve had trouble getting debugger mode to work correctly from inside the container. I've tried:
- Adding
pdb.set_trace()in the node script: works, but not convenient for full debugging. - Launching
python3 -m debugpy --listen 5678 --wait-for-client my_node.pyand attaching from VS Code: partially works. - Using
launch.jsonin VS Code Remote Containers to run the node directly: fails withCould not find debugpy path.
Questions:
- What is the officially recommended way to enable Python debugger mode inside the Isaac ROS dev container?
- Is it possible to debug a ROS 2 Python node using VS Code
launch.jsondirectly in the container environment? - Are there specific environment variables or entrypoints I should use to properly initialize the ROS environment before launching the node via debugger?
Any guidance or example configurations would be greatly appreciated!
Thanks in advance.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the run_dev.sh environment and the reported VS Code launch.json and debugpy setup. Document the officially supported way to launch or attach to a Python ROS 2 node in the Isaac ROS dev container, including how the ROS environment is initialized and an example configuration if one is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, vscode
- Domain
- devtools, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100