# Next Client Library WG Meeting: Friday 6th December 2024 8AM PT

**URL:** <https://discourse.openrobotics.org/t/next-client-library-wg-meeting-friday-6th-december-2024-8am-pt/40954>\
**Category:** ROS General\
**Tags:** ros2, wg-client-libraries\
**Created:** [December 4, 2024, 6:12pm UTC](https://discourse.openrobotics.org/t/next-client-library-wg-meeting-friday-6th-december-2024-8am-pt/40954 "2024-12-04T18:12:58Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![alsora](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/alsora/32/2514_2.png) [@alsora](https://discourse.openrobotics.org/u/alsora)\
**Post date:** [December 6, 2024, 5:09pm UTC](https://discourse.openrobotics.org/t/next-client-library-wg-meeting-friday-6th-december-2024-8am-pt/40954/2 "2024-12-06T17:09:27Z")

</div>

Meeting minutes

I’m setting up a shared page that will be used to collect all meeting minutes from now on.

## Attendees

- Alberto Soragna
- Janosh Machowinski
- Francisco Martin Rico
- Peter Ndiba

## Discussions

- Reviewed Working group charter document: [client-library-wg-charter - Google Docs](https://docs.google.com/document/d/1IGKXJra1e4QYWgcKcrS5V-v1yeDB5Lr_Pxge4WMLfZM/edit?usp=sharing)

- [fix: Expose timers used by rclcpp::Waitables by jmachowinski · Pull Request #2699 · ros2/rclcpp · GitHub](https://github.com/ros2/rclcpp/pull/2699) this PR follows up on what we discussed in the previous meeting. We need a way to grab the timers out of a waitable in order to add them to an executor.

- [fix(rcl\_action): Allow to pass the timer to action during initialization by jmachowinski · Pull Request #1201 · ros2/rcl · GitHub](https://github.com/ros2/rcl/pull/1201) this is a pre-requisite to the above PR. It allows the client library (rclcpp) to create a timer and pass it to the action server rather than have the action server create the timers internally in rcl (which makes it hard to access them from the executor)

- Discussed a bug: creating clocks via their constructor, rahter than via a ROS node, will not connect them to a ROS source, so they won’t follow the ROS time. This can be a source of hard to debug problems. We still should allow to create MONOTONIC or SYSTEM clocks without a node.

- [https://github.com/ros2/rclcpp/pull/2691](https://github.com/ros2/rclcpp/pull/2691) This PR fixes a bug / bad design related to the above problem.

- [Waitset not triggering timer when initialized in lifecycle node · Issue #2652 · ros2/rclcpp · GitHub](https://github.com/ros2/rclcpp/issues/2652) High priority bug around waitset executors.

## TODO work

- Ask if we can deprecate `Clock::cancel_sleep_or_wait`
- Write a unit-test for rclcpp #2652
- Discuss experimental namespace or anticipated code freeze with ROS PMC
- Review PRs around timers and rcl action, as they are pre-requisites for improving the timers manager.

Thank you everyone for joining!  
See you on December 20 2024

---

_[View the full topic](https://discourse.openrobotics.org/t/next-client-library-wg-meeting-friday-6th-december-2024-8am-pt/40954)._
