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

Backports to iron #869

Merged
merged 4 commits into from
Nov 30, 2023
Merged

Conversation

christophfroehlich
Copy link
Contributor

A manual backport PR to fix conflicts of open backports.

Replaces #837 #853 #862 #866

christophfroehlich and others added 4 commits November 29, 2023 19:01
* Simplify initialization of states
* Rename read_state_from_hardware method
* Don't set state_desired in on_activate
---------

Co-authored-by: Dr. Denis <[email protected]>
* Fix dynamic reconfigure of tolerances

* Fix static cast syntax
@RobertWilbrandt
Copy link
Contributor

Doing such backports and releasing them one day before sync makes it really hard to depend on these packages. For our ur_controllers this backport meant that we were not able to adjust to the API changes in time for the sync, and our builds now failing in the buildfarm.

@christophfroehlich
Copy link
Contributor Author

Hm, maybe we haven't thought about the API break of renaming read_state_from_hardware while backporting (I think this is the only break here). We should work on bringing the scaled JTC upstream into this package (#301, I guess this is the conflict here?).

@RobertWilbrandt
Copy link
Contributor

Yeah that will probably be the best long-term solution for us.

@bmagyar
Copy link
Member

bmagyar commented Dec 6, 2023

Sorry for the inconvenience caused guys.

I'd suggest also following this up with the ROS Boss for Iron. Releases too close to the sync are typically held. The entire purpose of the testing repo is to give some mileage to new releases before they go into sync.

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.

3 participants