-
Notifications
You must be signed in to change notification settings - Fork 324
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
[JSB] Fix the behaviour of publishing unavailable state interfaces when they are previously available #1331
[JSB] Fix the behaviour of publishing unavailable state interfaces when they are previously available #1331
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1331 +/- ##
==========================================
+ Coverage 80.57% 80.67% +0.10%
==========================================
Files 109 109
Lines 9553 9580 +27
Branches 832 835 +3
==========================================
+ Hits 7697 7729 +32
+ Misses 1578 1573 -5
Partials 278 278
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
oh mamma mia! that is a good catch!
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.
I tested this right now with example_13: I could reproduce the issue and can confirm that this PR solves it.
87f21b3
into
ros-controls:master
…en they are previously available (#1331) * Add test to reproduce the behaviour of ros-controls/ros2_control_demos#417 (comment) * Add fix to solve the issue of the publishing non-existing joint_states (cherry picked from commit 87f21b3)
…en they are previously available (#1331) * Add test to reproduce the behaviour of ros-controls/ros2_control_demos#417 (comment) * Add fix to solve the issue of the publishing non-existing joint_states (cherry picked from commit 87f21b3)
…en they are previously available (#1331) (#1339) * Add test to reproduce the behaviour of ros-controls/ros2_control_demos#417 (comment) * Add fix to solve the issue of the publishing non-existing joint_states (cherry picked from commit 87f21b3) Co-authored-by: Sai Kishor Kothakota <sai.kishor@pal-robotics.com>
…en they are previously available (#1331) (#1340) * Add test to reproduce the behaviour of ros-controls/ros2_control_demos#417 (comment) * Add fix to solve the issue of the publishing non-existing joint_states (cherry picked from commit 87f21b3) Co-authored-by: Sai Kishor Kothakota <sai.kishor@pal-robotics.com>
Hello!
While reviewing the Example 13, I came across this situation described in the comment : ros-controls/ros2_control_demos#417 (comment)
After debugging, the resource manager properly sets the state interfaces. However, some internal variables are not properly reset, and this results in the publishing of previously available interfaces.
The proposed fix fixes the issue of properly publishing the state of the known state interfaces alone