Skip to content
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

Merged
merged 3 commits into from
Feb 21, 2019

Conversation

mikaelarguedas
Copy link
Member

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

@mikaelarguedas mikaelarguedas added in progress Actively being worked on (Kanban column) in review Waiting for review (Kanban column) and removed in progress Actively being worked on (Kanban column) labels Feb 18, 2019
@ruffsl
Copy link
Member

ruffsl commented Feb 18, 2019

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

@mikaelarguedas
Copy link
Member Author

The test case may need to be updated though:

Good point 👍, test updated in e385cbd

Signed-off-by: Mikael Arguedas <mikael.arguedas@gmail.com>
Copy link
Member

@ruffsl ruffsl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jacobperron
Copy link
Member

jacobperron commented Feb 21, 2019

Ignore unrelated test failures in rclcpp_action and test_cli:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

Edit: Retriggering with ros2/ci#246 (which I think is required)

@jacobperron
Copy link
Member

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.
@ruffsl I think you can go ahead and merge this into your branch if you're happy with it.

@ruffsl ruffsl merged commit 4e7c398 into ros2:xml_profile Feb 21, 2019
@ruffsl ruffsl removed the in review Waiting for review (Kanban column) label Feb 21, 2019
@mikaelarguedas mikaelarguedas deleted the logging_xml_profile branch February 21, 2019 20:13
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.

None yet

3 participants