Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] Rosmaster URI export does not work #676

Closed
2 of 4 tasks
ZygaOGC opened this issue Feb 21, 2022 · 3 comments
Closed
2 of 4 tasks

[bug] Rosmaster URI export does not work #676

ZygaOGC opened this issue Feb 21, 2022 · 3 comments
Labels
bug Something isn't working

Comments

@ZygaOGC
Copy link

ZygaOGC commented Feb 21, 2022

(Please add appropriate labels)

  • Windows: (Version)
  • Linux: (Ubuntu/20.04)
  • ROS 1: Dist
  • ROS 2: Dist

<0.8.0>

what is the bug

Can not launch debugging with a remote rosmaster.

Repro steps

  1. Export ROS_MASTER_URI variable in the pre-launch task.
  2. Launch debugging

expected behavior

Node under debugging should connect to the rosmaster available at exported URI

@ZygaOGC ZygaOGC added the bug Something isn't working label Feb 21, 2022
@ranchhandrobotics
Copy link

Unfortunately, VSCode itself does not propagate environment variables between tasks, so this is lost well before the ROS extension activates. Instead you should launch vscode from a pre-initialized environment, or ensure that you are using ros from a root install. Check out this video for more details: https://www.youtube.com/watch?v=N2vqBvPQdhE

@ooeygui
Copy link
Member

ooeygui commented Feb 21, 2022

I'm adding support for specifying a setup script by full path instead of just attempting to inferring. This resolves some issues where ROS isn't installed in a standard location.

@ooeygui
Copy link
Member

ooeygui commented Feb 27, 2022

Support for arbitrary script loading has been added in #678

@ooeygui ooeygui closed this as completed Feb 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants