fix(bot_state_machine): use namespace-relative lifecycle client names#13
Open
arresejo wants to merge 1 commit into
Open
fix(bot_state_machine): use namespace-relative lifecycle client names#13arresejo wants to merge 1 commit into
arresejo wants to merge 1 commit into
Conversation
create_comms() built transition_event/change_state/get_state names with a leading slash, making them absolute and bypassing the state machine's own namespace. With a robot_name set in robot_config.yaml, all get_state calls failed and every node stayed 'unknown', so bringup never ran. Relative names resolve inside the node's namespace and are identical to the previous behavior when no robot name is set (namespace '/').
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
create_comms() built transition_event/change_state/get_state names with a leading slash, making them absolute and bypassing the state machine's own namespace. With a robot_name set in robot_config.yaml, all get_state calls failed and every node stayed 'unknown', so bringup never ran.
Relative names resolve inside the node's namespace and are identical to the previous behavior when no robot name is set (namespace '/').