Skip to content

[RBTSW-674] Create the node's /rosout publisher - #132

Open
AdamProchownik wants to merge 1 commit into
sequenceplanner:masterfrom
cocorobotics:bug/RBTSW-674_Fix_rosout_and_params_handling_in_event_reporter
Open

[RBTSW-674] Create the node's /rosout publisher#132
AdamProchownik wants to merge 1 commit into
sequenceplanner:masterfrom
cocorobotics:bug/RBTSW-674_Fix_rosout_and_params_handling_in_event_reporter

Conversation

@AdamProchownik

Copy link
Copy Markdown

rcl_node_init() does not create the per-node /rosout publisher; the client library has to call rcl_logging_rosout_init_publisher_for_node() itself, as rclcpp and rclpy both do. Without it rcl_logging_rosout_output_handler() finds no publisher registered for the node's logger name and drops every record, so r2r logs only ever reach the console.

rcl/logging_rosout.h was also not included by the bindgen wrapper, so the functions had no bindings at all.

rcl_node_init() does not create the per-node /rosout publisher; the client
library has to call rcl_logging_rosout_init_publisher_for_node() itself, as
rclcpp and rclpy both do. Without it rcl_logging_rosout_output_handler()
finds no publisher registered for the node's logger name and drops every
record, so r2r logs only ever reach the console.

rcl/logging_rosout.h was also not included by the bindgen wrapper, so the
functions had no bindings at all.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant