Jonathan

I encountered it while in a running container with the zed_wrapper in my ros workspace, not built during build phase step. I will have to test the BUILDKIT=0 workaround when...

I was able to test the buildkit=0 and that worked. Looking at buildkit documentation I was also able to change buildkits runtime to nvidia's so that seems more optimal for...

Isaac ros 3.0.0 is only supported on Jetpack 6.0 https://nvidia-isaac-ros.github.io/repositories_and_packages/isaac_ros_common/index.html#supported-platforms

Looking more closely looks like it isn't caused exclusively by calling a cpp action server and I've adjusted issue description and steps to reproduce

Looks like by doing something like [this](https://robotics.stackexchange.com/questions/98471/mistakes-using-service-and-client-in-same-node-ros2-python), can mitigate the issue, but feels really awkward. Here's a patch implementing this [example.txt](https://github.com/user-attachments/files/16203795/example.txt). Maybe this is just a fundamental limitation of nodes,...

Would it be reasonable to check before adding the node if it is already in executor. If already present not remove it after completion?

I understand it's not adding a duplicate. I was wondering if it would be appropriate to have the node not be removed from executor at the end if it was...

> i would add @aditya2592 as co-author, since this borrows the code from #1125. Done

Throwing this back to draft because it still doesn't fix all conditions where this breaks. If others have ideas on how to more reliably reproduce this that would be appreciated.

I was defining a python action client server pair in two seperate terminals, and the custom server also contained a python client to another cpp nav2 action. After calling the...