Closed yashi closed 9 months ago
Which distro of ROS 2 are you running?
Humble.
Could you confirm that using iron
version of the agent this issue does not happens?
In my scenario, I can replicate your issue in humble
but if I just run the iron
agent, it does not happen.
If you confirm that, I will take a look at humble.
EDIT:
This seems to be an iron
<-> humble
incompatibility.
In my previous scenario, I had: micro-ROS humble + Agent Humble + RQT Iron and it failed.
If I move to micro-ROS humble + Agent Humble + RQT Humble it does not fail.
This makes sense since ros introspection messages may be incompatible and the micro-ROS Agent is failing at the graph management level. Could you ensure that your custom installation is a pure humble
distro?
You are right. My RQT was somehow built against iron
. I apologize and thank you for your time.
micro-ROS | Agent | RQT | |
---|---|---|---|
NG | Humble | Humble | v1.3.3 built against Iron |
OK | Humble | Humble | v1.3.3 built against Humble |
OK | Humble | Iron | v1.3.3 built against Iron |
Hi,
Does anyone successfully run rqt with micro-ros Agent?
On my PC, the agent dies when I run both rqt and micro-ROS. That is, the Agent doesn't die when there are only:
But as soon as I run the three, Agent, micro-ROS nodes, and rqt with the "Node Graph", Agent aborts with the following message:
Full backtrace is down below.
Issue template
Steps to reproduce the issue
Expected behavior
Agent doesn't die.
Actual behavior
Agent dies with SIGABRT.
Additional information
Backtrace