methylDragon

Results 155 comments of methylDragon

* Linux [![Build Status](http://ci.ros2.org/buildStatus/icon?job=ci_linux&build=18477)](http://ci.ros2.org/job/ci_linux/18477/) * Linux-aarch64 [![Build Status](http://ci.ros2.org/buildStatus/icon?job=ci_linux-aarch64&build=13025)](http://ci.ros2.org/job/ci_linux-aarch64/13025/) * Windows [![Build Status](http://ci.ros2.org/buildStatus/icon?job=ci_windows&build=19193)](http://ci.ros2.org/job/ci_windows/19193/) * Windows Debug [![Build Status](http://ci.ros2.org/buildStatus/icon?job=ci_windows&build=19194)](http://ci.ros2.org/job/ci_windows/19194/) Run 2 [![Build Status](http://ci.ros2.org/buildStatus/icon?job=ci_windows&build=19195)](http://ci.ros2.org/job/ci_windows/19195/) Run 3 [![Build Status](http://ci.ros2.org/buildStatus/icon?job=ci_windows&build=19196)](http://ci.ros2.org/job/ci_windows/19196/) * RHEL [![Build Status](http://ci.ros2.org/buildStatus/icon?job=ci_linux-rhel&build=380)](https://ci.ros2.org/job/ci_linux-rhel/380/)

It looks like just linting issues @gbiggs https://ci.ros2.org/job/ci_packaging_linux/536/testReport/

@dbking77 could you fix those linting issues? :>

Just noting here that this is still pending the merge of: - https://github.com/ros2/rclcpp/pull/1874

@gbiggs My suspicion is these: ![image](https://user-images.githubusercontent.com/20265670/169372458-e291118e-5bc7-4626-ba62-1bddeb0562c0.png) Suggestion: Rebase the branch on `master`, which should remove a lot of the extra commits, it'll also fix the conflicts since the creation of...

Latest build * Linux [![Build Status](http://ci.ros2.org/buildStatus/icon?job=ci_linux&build=17611)](http://ci.ros2.org/job/ci_linux/17611/) * Linux-aarch64 [![Build Status](http://ci.ros2.org/buildStatus/icon?job=ci_linux-aarch64&build=12153)](http://ci.ros2.org/job/ci_linux-aarch64/12153/) * Windows [![Build Status](http://ci.ros2.org/buildStatus/icon?job=ci_windows&build=18181)](http://ci.ros2.org/job/ci_windows/18181/)

> @methylDragon thanks for the contribution. > > Could you explain the actual problem that you meet to address with this PR? I am not really following the what needs...

@ros-pull-request-builder retest this please

@clalancette > But this is a good question; it would be nice if this policy were encoded in the rcl layer, and then just inherited by the client libraries. @methylDragon...