Fix clock thread issue (#1266) (#1267)#1685
Conversation
6262e4e to
1b75836
Compare
|
@KavenYau @clalancette friendly ping. |
clalancette
left a comment
There was a problem hiding this comment.
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. |
Signed-off-by: Daisuke Sato daisukes@cmu.edu