Lifecycle node should publish a transition event when instantiated
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 805
- Forks
- 564
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 27
Description
- Operating System:
Ubuntu 20.04 - Installation type:
Binaries - Version or commit hash:
Galactic - DDS implementation:
Cyclone DDS
Steps to reproduce issue
- Launch a lifecycle node using a launch file in a terminal
- Subscribe to the transition event topic of the node in an other terminal
- Close the first terminal (the one with the launch file)
- Launch again the same lifecycle node
- Look at the transition event that were received
Expected behavior
When the node is instantiated it may be interesting to receive a transition event for the transition from 'nothing' to 'unconfigured' this way we could have a 'RegisterEventHandler' in a launch file to detect when a lifecycle node is instantiated.
Actual behavior
No transition event is received for the node reaching goal state "unconfigured" when the node is instantiated.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the lifecycle-node launch and transition-topic steps described in the issue, then trace the C++ lifecycle transition-event publication path. Confirm the current behavior when the node reaches "unconfigured" during instantiation. Done means a newly instantiated lifecycle node publishes the requested transition event and the behavior is covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100