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.

Sign up for GitHub

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

Jump to bottom

[JTC] Reject messages with effort fields (#699) (backport #719) #738

Merged
merged 1 commit into from
Aug 7, 2023
Merged

[JTC] Reject messages with effort fields (#699) (backport #719) #738

merged 1 commit into from
Aug 7, 2023

Conversation

christophfroehlich
Copy link
Contributor

A manual backport without merge conflicts now.

@bmagyar @christophfroehlich
[JTC] Reject messages with effort fields (ros-controls#699) (ros-cont…
e46585c 
…rols#719)

Co-authored-by: Christoph Fröhlich <christophfroehlich@users.noreply.github.com>
(cherry picked from commit a572381)
@christophfroehlich christophfroehlich mentioned this pull request Aug 7, 2023
Closed
@christophfroehlich
Copy link
Contributor Author

Failing CI job is not related to this change imho, because it has failing tests with trajectories without efforts field.

@bmagyar bmagyar merged commit 6a4e7a6 into ros-controls:humble Aug 7, 2023
12 of 13 checks passed
@christophfroehlich christophfroehlich deleted the bp/humble/pr-719 branch August 8, 2023 05:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bmagyar bmagyar bmagyar approved these changes

@DasRoteSkelett DasRoteSkelett Awaiting requested review from DasRoteSkelett

@destogl destogl Awaiting requested review from destogl

@harderthan harderthan Awaiting requested review from harderthan

@progtologist progtologist Awaiting requested review from progtologist

@rosterloh rosterloh Awaiting requested review from rosterloh

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@christophfroehlich @bmagyar