-
Notifications
You must be signed in to change notification settings - Fork 240
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
Add callbacks for PlayerClock::jump(time_point) API #775
Conversation
Signed-off-by: Michael Orlov <michael.orlov@apex.ai>
Signed-off-by: Michael Orlov <michael.orlov@apex.ai>
Signed-off-by: Michael Orlov <michael.orlov@apex.ai>
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.
Just a nitpick on the documentation formatting - I'd like to change that before we merge so that it is consistent, but this LGTM
Signed-off-by: Michael Orlov <michael.orlov@apex.ai>
Signed-off-by: Michael Orlov <michael.orlov@apex.ai>
Please make sure CI (on https://ci.ros2.org) gets run on these PRs (if it has been, it isn't obvious to me where). In this case, this has caused regressions on Windows: https://ci.ros2.org/view/nightly/job/nightly_win_rel/1961/ |
Ah - there wasn't a run. @MichaelOrlov can you quickly fix the windows build? if not, please revert this PR and reopen so we can fix the CI before merging for good |
Should we go ahead and revert this for now? |
This reverts commit abd4229. Signed-off-by: Emerson Knapp <emerson.b.knapp@gmail.com>
Yes, #778 |
@MichaelOrlov I've merged the revert - could you take a look at the windows failures and reopen this contribution? |
@emersonknapp @clalancette Sorry guys, I have not seen notification. And my apologies for the broken CI. I will take a look on breakage. |
@emersonknapp @clalancette I figured out. Issue was in warnings from MSBuild about type cast in unit tests. However I don't know how to reopen this MR since branch has been deleted and I don't see any options to reopen MR. |
Yes, that seems to be the right thing to do. |
Add callbacks for PlayerClock::jump(time_point) API
Part of #696