Skip to content
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 osx #428

Merged
merged 1 commit into from
Jun 3, 2021
Merged

fix osx #428

merged 1 commit into from
Jun 3, 2021

Conversation

Karsten1987
Copy link
Contributor

osx reported a bunch of error, mainly about not finding isnan. Then there were warnings about non-virtual destructors and unused variables.

Signed-off-by: Karsten Knese <Karsten1987@users.noreply.github.com>
Copy link
Member

@destogl destogl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, though not testable really...

Copy link
Member

@bmagyar bmagyar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gut thanks

@bmagyar bmagyar merged commit a814ac1 into master Jun 3, 2021
v-lopez pushed a commit to pal-robotics-forks/ros2_control that referenced this pull request Jun 4, 2021
Signed-off-by: Karsten Knese <Karsten1987@users.noreply.github.com>
@destogl destogl deleted the fix_osx branch August 19, 2021 09:54
livanov93 pushed a commit to livanov93/ros2_control that referenced this pull request Mar 22, 2023
* Change type cast wall timer period from second to nanoseconds.
    create_wall_timer() expects delay in nanoseconds (duration object) however the type cast to seconds will result in 0 (if duration is less than 1s) and thus causing timer to be fired non stop resulting in very high CPU usage.

* Reset smartpointer so that create_wall_timer() call can destroy previous trajectory timer.
   node->create_wall_timer() first removes timers associated with expired smartpointers before servicing current request.  The JTC timer pointer gets overwrite only after the create_wall_timer() returns and thus not able to remove previous trajectory timer resulting in upto two timers running for JTC during trajectory execution.  Althougth the previous timer does nothing but still get fired.

Signed-off-by: Arshad Mehmood <arshadm78@yahoo.com>

Signed-off-by: Arshad Mehmood <arshadm78@yahoo.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants