Unable to see node from ROS2 CLI about rclnet HOT 8 CLOSED

For what it's worth...this example does seem to work fine in linux. Only edits I made were async Task rather than async void because I needed something to await in Main.

I'm using .NET 8 though. If that matters.

from rclnet.

I have had problems similar to this when the executable is being run as root instead of a user. I'm not sure if there is a similar thing in Windows or not.

from rclnet.

Could you please try running the graph_monitor example first and then start your node and see if graph_monitor can receive node online events?

from rclnet.

Could you please try running the graph_monitor example first and then start your node and see if graph_monitor can receive node online events?

Will do this and report back! Also will try running as user instead.

from rclnet.

I have had problems similar to this when the executable is being run as root instead of a user. I'm not sure if there is a similar thing in Windows or not.

I am on windows and it appears there is a similar-ish behavior. When I build and run the project from Visual Studio 2022 in Windows then I am not able to see the node using ros2 node list in other terminals. If I manually run the build executable in a fresh command prompt then I am able to see it as normal. Any thoughts on this @noelex

from rclnet.

If I manually run the build executable in a fresh command prompt then I am able to see it as normal.

Looks like an environment issue. Does removing launchSettings.json and launching Visual Studio from a command prompt with setup.bat sourced work for you?

from rclnet.

I will try this and post an update shortly. Thanks for the support here!

from rclnet.

It looks like this is related to the env config in Visual Studio. It does not seem to cause any issues so I am happy to close this for now since that seems to be the root cause. Thanks everyone! @noelex great repo!

from rclnet.