-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add logging permission profile #80
Conversation
Ah man... its like ROS1 all over again. Why is everything is needing to publish to root level topics and parameters by default. The test case may need to be updated though: https://github.com/ros2/sros2/pull/72/files#diff-9534083787043b52ef6d287331dfc69bR53 |
Good point 👍, test updated in e385cbd |
Signed-off-by: Mikael Arguedas <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Ignore unrelated test failures in Edit: Retriggering with ros2/ci#246 (which I think is required) |
Looks like the changes in ros2/ci#246 need to be rebased on master, I'll just wait until it is merged before triggering CI. |
This PR targets #72, not master
Since ros2/rcl#350 all node need publish access to
/rosout
by default.I called it logging in case we have other related default logging topics in the future.
@ruffsl FYI