-
Notifications
You must be signed in to change notification settings - Fork 334
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
[TricycleController] Removed “publish period” functionality ⏱ #abi-break #behavior-break #468
[TricycleController] Removed “publish period” functionality ⏱ #abi-break #behavior-break #468
Conversation
4c938e9
to
d103ada
Compare
Can you please check the documentation of the tricycle controller (if any in |
d103ada
to
589c3f0
Compare
Codecov Report
@@ Coverage Diff @@
## master #468 +/- ##
==========================================
- Coverage 35.78% 29.70% -6.08%
==========================================
Files 189 7 -182
Lines 17570 744 -16826
Branches 11592 429 -11163
==========================================
- Hits 6287 221 -6066
+ Misses 994 163 -831
+ Partials 10289 360 -9929
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.
Only flaky tests are breaking.
I can't find any comments on that topic in the minutes of that meeting, could someone quickly explain why this change is needed? |
Here is the discussion on this topic on JTC: https://docs.google.com/document/d/1818AoYucI2z82awL_-8sAA5pMCV_g_wXCJiM6SQmhSQ/edit?disco=AAAAlmxhM3k I also wrote the decision just now into the comments to make it clear (@bmagyar can you please confirm?) The reason is that we had issues on the test with this functionality, and is repeatable across the controller. So, the idea would be to make this somehow reusable in |
Thanks for the references, I commented my follow up question in #473 |
It was removed: ros-controls#468
Per discussion in Control WG meeting from Nov. 16th 2022