You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expect to see a list of transitions the node could go through.
Actual behavior
$ ros2 lifecycle get --transitions /lc_talker
unconfigured [1]
Traceback (most recent call last):
File "/opt/ros/crystal/bin/ros2", line 11, in <module>
load_entry_point('ros2cli==0.6.1', 'console_scripts', 'ros2')()
File "/opt/ros/crystal/lib/python3.6/site-packages/ros2cli/cli.py", line 69, in main
rc = extension.main(parser=parser, args=args)
File "/opt/ros/crystal/lib/python3.6/site-packages/ros2lifecycle/command/lifecycle.py", line 40, in main
return extension.main(args=args)
File "/opt/ros/crystal/lib/python3.6/site-packages/ros2lifecycle/verb/get.py", line 93, in main
.format_map(locals()))
AttributeError: 'TransitionDescription' object has no attribute 'label'
Additional information
The text was updated successfully, but these errors were encountered:
Fixesros2#114.
Due to the asynchronous nature of the LoadComposableNodes action, an event handler causes the launch configuration is popped if ComposableNodeContainer appears inside a group or include action.
It seems to me we can simply return the load node action, which will get executed after the ComposableNodeContainer action. The use of an event handler is vestigial of a refactoring done in ros2/launch_ros#16, and doesn't appear to be necessary.
Signed-off-by: Jacob Perron <jacob@openrobotics.org>
Bug report
Required Info:
Steps to reproduce issue
Expected behavior
I expect to see a list of transitions the node could go through.
Actual behavior
Additional information
The text was updated successfully, but these errors were encountered: