Open jdlangs opened 9 months ago
@methylDragon Would you be willing to look into the behavior and figure out where the bug is? 🧇
It seems like passing launch_arguments
to IncludeLaunchDescription
in top.launch.py
might be part of the solution, but if I understand correctly that wouldn't explain why setting bottom2
only seems to have been recognized by bottom.launch.py
.
Bug report
Required Info:
Steps to reproduce issue
Build this package and run
ros2 launch launch_args_ex top.launch.py bottom1:=true bottom2:=true
top.launch.py
bottom.launch.py
Expected behavior
The
bottom1
andbottom2
arguments receive values passed from the command-line.Actual behavior
What's weird is if you don't set one of the args, it now sees that the other one was given:
Here's a full debug output as well: