You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Start the ros talker node using rosrun my_robot_pkg talker.py inside the system terminal.
Start the ros listener node using rosrun my_robot_pkg listener.py inside the system terminal.
Add the ROS attach option to your launch.json file.
Try to attach to the ROS python node using python->listener.py.
additional info
This behaviour is present both in the stable python debugger as well as the new insiders python debugger. The vscode OUTPUT window doesn't display any error or warning message.
The text was updated successfully, but these errors were encountered:
@rickstaa Sorry for the long overdue. Is it still reproducible? I tried the following combination and I can attach and debug the Python node with your example.
Platform: Ubuntu 18.04
# output from `code --list-extensions --show-versions`
ms-iot.vscode-ros@0.6.3
ms-python.python@2020.5.80290
ms-vscode.cpptools@0.28.0
Hi, I have encountered the same situation, it cannot attach to the listener or talker node.
How did you solve it ? just by updating the vscode version?
Here is my vscode version infos:
Version: 1.67.2
Commit: c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
Date: 2022-05-17T18:23:40.286Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Linux x64 5.4.0-113-generic snap
general information
OS version: Ubuntu 18.04
Plugin version: 0.6.2
what is the bug
When trying to attach to a python ROS node nothing happens.
expected behaviour
The vscode ROS extension successfully attaches to the running python ROS node.
steps to reproduce
rosrun my_robot_pkg talker.py
inside the system terminal.rosrun my_robot_pkg listener.py
inside the system terminal.additional info
This behaviour is present both in the stable python debugger as well as the new insiders python debugger. The vscode OUTPUT window doesn't display any error or warning message.
The text was updated successfully, but these errors were encountered: