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/excessive_warnings_lost_trajectories #13

Open
RPKrijnen opened this issue Jul 13, 2022 · 0 comments
Open

fix/excessive_warnings_lost_trajectories #13

RPKrijnen opened this issue Jul 13, 2022 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@RPKrijnen
Copy link
Collaborator

"No trajectory defined at current time" is one of the warnings that gets pushed out by ros_control. This is an issue with a setup for a third party developer. We should check if this is due to some timing issue (ros time vs system time) or that the code is slow, maybe we implement the action interface in an incorrect way.

@RPKrijnen RPKrijnen added the good first issue Good for newcomers label Jul 13, 2022
@akshayrmenon akshayrmenon linked a pull request Aug 24, 2022 that will close this issue
@akshayrmenon akshayrmenon added bug Something isn't working and removed good first issue Good for newcomers labels Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants