JEnoch
commented
4 months ago The warnings about liveliness tokens are a direct consequence of the create-2 process (i.e. spawn_model node) crash:
[create-2] [INFO] [1719424502.517446780] [spawn_model]: OK creation of entity.
[create-2] thread '<unnamed>' panicked at /build/rustc-Px5Ywq/rustc-1.75.0+dfsg0ubuntu1/library/std/src/thread/local.rs:246:26:
[create-2] cannot access a Thread Local Storage value during or after destruction: AccessError
[create-2] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[ERROR] [create-2]: process has died [pid 48936, exit code -6, cmd '/opt/ros/rolling/lib/ros_gz_sim/create -topic robot_description -name rox --ros-args -r __node:=spawn_model'].The node didn't perform a clean exit, removing all its pub/subs/clients/services before to stop. The Zenoh liveliness tokens are used for ROS graph discovery.
Please, reproduce the issue with the RUST_BACKTRACE=1 environment variable set for this process (or for the full host if simpler) and copy here the backtrace you get .
padhupradheep
I was trying to launch the gz simulation using the command:
ros2 launch rox_bringup bringup_sim_launch.py[jazzy-devel branch]if you want to use this, then you also need to export the gz resource path like this :
export GZ_SIM_RESOURCE_PATH=~/rolling_ws/src/rox/:~/rolling_ws/src/neo_gz_worlds/modelsand also clone the neo_gz_worlds
while doing so, the spawn
createnode fails for some reason. with the following error:Also on the teleop terminal, I can see the following piece of warning:
we don't see this while using other dds vendors.
Although we are able to move the robot like as usual, I thought, this might be something helpful to improve zenoh
Here is the full logs: