NVIDIA-ISAAC-ROS / NVIDIA-ISAAC-ROS/isaac_ros_nvblox

Caught exception in launch (see debug for traceback): __init__() got an unexpected keyword argument 'condition'

Open
#85 3 comments 0 reactions 1 assignee View on GitHub

@jaiveersinghNV is already working on this.

Since Dec 4, 2023.

needs info
Dominant language
C++
Stars
750
Forks
142
PR merge metrics
No merged PRs in 30d

Description

The work seems to be too interesting. I have downloaded the repository few months back and tested the isaac_ros_nvblox. I tested the tutorials in isaac sim simulator as well as using real sense camera for real-time. Everything worked well.
However there is new update in the package and dynamic tutorials were added. So I downloaded the isaac_ros_nvblox package and replaced with old package and build again for checking the tutorials. However I have issue with condition statement as below. Can you help me out in solving the issue. Is it because of the mismatch ros version or any other dependency issue.

Below is the log fie

1701221156.1139338 [INFO] [launch]: Default logging verbosity is set to INFO
1701221156.3357425 [ERROR] [launch]: Caught exception in launch (see debug for traceback): __init__() got an unexpected keyword argument 'condition'
1701221156.5786924 [INFO] [component_container_mt-1]: process started with pid [29559]
1701221156.5797582 [INFO] [component_container_mt-1]: sending signal 'SIGINT' to process[component_container_mt-1]
1701221156.6851957 [INFO] [component_container_mt-1]: process has finished cleanly [pid 29559]
1701221157.5612414 [WARNING] [launch_ros.actions.load_composable_nodes]: Abandoning wait for the 'shared_nvblox_container/_container/load_node' service response, due to shutdown.

This is the complete error

[INFO] [launch]: Default logging verbosity is set to INFO
[ERROR] [launch]: Caught exception in launch (see debug for traceback): __init__() got an unexpected keyword argument 'condition'
[INFO] [component_container_mt-1]: process started with pid [720]
[component_container_mt-1] [INFO] [1701222822.699096851] [shared_nvblox_container]: Load Library: /workspaces/isaac_ros-dev/install/realsense_splitter/lib/librealsense_splitter_component.so
[component_container_mt-1] [INFO] [1701222822.704229477] [shared_nvblox_container]: Found class: rclcpp_components::NodeFactoryTemplate<nvblox::RealsenseSplitterNode>
[component_container_mt-1] [INFO] [1701222822.704279312] [shared_nvblox_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nvblox::RealsenseSplitterNode>
[component_container_mt-1] [INFO] [1701222822.709484685] [camera.realsense_splitter_node]: Creating a RealsenseSplitterNode().
[INFO] [component_container_mt-1]: sending signal 'SIGINT' to process[component_container_mt-1]
[component_container_mt-1] [INFO] [1701222822.718272949] [rclcpp]: signal_handler(signum=2)
[INFO] [component_container_mt-1]: process has finished cleanly [pid 720]
[WARNING] [launch_ros.actions.load_composable_nodes]: Abandoning wait for the 'shared_nvblox_container/_container/load_node' service response, due to shutdown.
Future exception was never retrieved
future: <Future finished exception=InvalidHandle('cannot use Destroyable because destruction was requested')>
Traceback (most recent call last):
  File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/opt/ros/humble/install/lib/python3.8/site-packages/launch_ros/actions/load_composable_nodes.py", line 197, in _load_in_sequence
    self._load_node(next_load_node_request, context)
  File "/opt/ros/humble/install/lib/python3.8/site-packages/launch_ros/actions/load_composable_nodes.py", line 119, in _load_node
    while not self.__rclpy_load_node_client.wait_for_service(timeout_sec=1.0):
  File "/opt/ros/humble/install/lib/python3.8/site-packages/rclpy/client.py", line 180, in wait_for_service
    return self.service_is_ready()
  File "/opt/ros/humble/install/lib/python3.8/site-packages/rclpy/client.py", line 159, in service_is_ready
    with self.handle:
rclpy._rclpy_pybind11.InvalidHandle: cannot use Destroyable because destruction was requested

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.