-
Notifications
You must be signed in to change notification settings - Fork 412
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
Fix clock thread issue (#1266) (#1267) #1685
Conversation
6262e4e
to
1b75836
Compare
@KavenYau @clalancette friendly ping. |
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.
From an API/ABI standpoint, this seems reasonable to me. We can't be breaking API, since both enable_ros_time
and disable_ros_time
were private static methods. And we aren't changing ABI, since we aren't changing the size of the TimeSource object. Finally, the removal of two methods from the symbol table could be considered an ABI break, but since they were private there was no way for external callers to get at them without grubbing around in the ELF sections. So this all looks good to me.
I'd like another opinion though, just to be sure my reasoning is sound. @hidmic, would you mind taking a look? Also pinging @jacobperron .
(oh, and we'll obviously need CI for this) |
We could actually keep both methods if we wanted, but deleting them sounds ok to me. |
The CI needs to be run against Foxy ros2.repos here :). |
|
@ivanpauno The Ubuntu distro was set to Bionic, but it should be Focal. |
🤦♂️, danke! |
@ivanpauno thanks for taking care of CI 👍 @jacobperron requesting final review, when you got time. |
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.
LGTM
Signed-off-by: Daisuke Sato daisukes@cmu.edu