We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, the TimersManager class waits for timers to be ready using the following code
TimersManager
timers_cv_.wait_for(lock, time_to_sleep.value(), [this]() {return timers_updated_;});
This will always sleep using the system clock, even if the "time to sleep" was computed from a timer using the ROS clock
We should take into account the clock type when deciding how to sleep, and use an API that is aware of ROS clock
The text was updated successfully, but these errors were encountered:
duplication of #2457. lets keep this alive as tracking issue, and i will close #2457. CC: @alsora
Sorry, something went wrong.
Ops, my bad. I started looking into this problem and created a ticket without noticing we already had one.
This issue has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/the-ros-2-c-executors/38296/4
https://discourse.ros.org/t/the-ros-2-c-executors/38296/13
alsora
No branches or pull requests
Feature request
Feature description
Currently, the
TimersManager
class waits for timers to be ready using the following codeThis will always sleep using the system clock, even if the "time to sleep" was computed from a timer using the ROS clock
We should take into account the clock type when deciding how to sleep, and use an API that is aware of ROS clock
The text was updated successfully, but these errors were encountered: