-
Notifications
You must be signed in to change notification settings - Fork 237
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
waitset -> wait_set #152
waitset -> wait_set #152
Conversation
@@ -1668,11 +1668,11 @@ rclpy_get_zero_initialized_wait_set(PyObject * Py_UNUSED(self), PyObject * Py_UN | |||
return pywait_set; | |||
} | |||
|
|||
/// Initialize a waitset | |||
/// Initialize a wait set |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should merge this PR.
How does this sound? With the number of people on vacation this week it seems unlikely the wait_for_service feature will make it in. Since most of #140 is refactoring for that, it won't need to be in the dec 8th release. Separately I'll split out the executor bug fixes from #140 to make sure those get in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good, I'll merge this soon, wrapping up third party rmw PRs.
With the number of people on vacation this week it seems unlikely the wait_for_service feature will make it in.
We'll see, I think there is a lot of value in getting some version of wait_for_service in before the release. We also have several PRs blocked until we can use that feature in tests.
Separately I'll split out the executor bug fixes from #140 to make sure those get in.
Yeah thats always a good idea to ease review. thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dhood I've made the state more complicated than it needs to be. The version of #127 that was approved has a couple problems:
- It adds overhead that makes the 1kHz timer test fail 100% of the time on aarch64
- A separate GraphListener wouldn't make sense once a
wait_for_service_async
is added
#135 was split from #127 to implement wait_for_service
in a way that makes sense with wait_for_service_async
. #140 was split from #135 to make the PR smaller. #140 has bug fixes found while reviewing #127 plus the performance improvements needed to get the 1kHz timer test to pass.
connects to ros2/rmw#131