Eloy Briceno

Results 24 comments of Eloy Briceno

I tried out the PR but I'm still getting that the detachable joints are disappearing when I press reset and creates new entities. This is the output I get when...

Taking into account the proposal of extending the capabilities of timers and some concerns on this [PR](https://github.com/ros2/rclcpp/pull/2006#discussion_r973768620) regarding the use of the `reset` method. I wanted to show a simple...

> overall lgtm, sorry to be late to get back to this. > > @Voldivh are you still working on this? there are conflicts what needs to be addressed. Hey...

> @Voldivh thanks for taking care of this, there is build failure https://build.ros2.org/job/Rpr__rcl__ubuntu_jammy_amd64/350/console Yeah I noticed, however, I believe the error is coming from this [commit](https://github.com/ros2/rcl/commit/c43c7abb0a254f4b60c42c4c2993917eb08cb0ec) made into rolling. I'm...

Hey @fujitatomoya, I believe the CI build failed because of the branch for https://github.com/ros2/system_tests/pull/508 was outdated. I already sync it with the latest changes from rolling, I think it should...

@fujitatomoya well that didn't do the trick :c. I'm not sure on what to do next, this is the error we are getting https://ci.ros2.org/job/ci_linux/18944/console#:~:text=12%3A18%3A46%20%3D%3D%3E,with%20return%20code%20%271%27

> There's no package called system_tests, it is called test_rclcpp. That makes a lot of sense, is that something that is defined when running the CI or do I have...

> @Voldivh i think we need to rebase rclcpp, please check https://ci.ros2.org/job/ci_linux/18949/console. I agree, it should be fine now after [this commit](https://github.com/ros2/rclcpp/pull/2005/commits/9597b9359dc7e66030a3e8314a2dbae9f78aed8e).

> * Linux [![Build Status](https://camo.githubusercontent.com/037629ab8e2ea404d05270a80cfc0fdb4a867e3aec2cdd293536886beb98b153/687474703a2f2f63692e726f73322e6f72672f6275696c645374617475732f69636f6e3f6a6f623d63695f6c696e7578266275696c643d3138393536)](http://ci.ros2.org/job/ci_linux/18956/) > * Linux-aarch64 [![Build Status](https://camo.githubusercontent.com/ea793d85cad46302841c093d9782fb7f667613bca0650759024452c03850ae4d/687474703a2f2f63692e726f73322e6f72672f6275696c645374617475732f69636f6e3f6a6f623d63695f6c696e75782d61617263683634266275696c643d3133343839)](http://ci.ros2.org/job/ci_linux-aarch64/13489/) > * Windows [![Build Status](https://camo.githubusercontent.com/0dd69d78aeb8fe7b4b539413c845e5a8defe6d898c901f5911a32cb9827d0383/687474703a2f2f63692e726f73322e6f72672f6275696c645374617475732f69636f6e3f6a6f623d63695f77696e646f7773266275696c643d3139373039)](http://ci.ros2.org/job/ci_windows/19709/) I think we had the same issue as before but now with rclpy. I already...

An implementation example that solves this issue can be found in the following forks: - https://github.com/ros2/rcl/compare/rolling...Voldivh:rcl:voldivh/autostart - https://github.com/ros2/rclcpp/compare/rolling...Voldivh:rclcpp:voldivh/autostart The solution presented before modifies the `rcl_timer_init` arguments implementing an `autostart` flag....