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

changes between 1.14.3 and 1.13.6 for backporting #1477

Merged
merged 13 commits into from
Aug 17, 2018

Conversation

dirk-thomas
Copy link
Member

@dirk-thomas dirk-thomas commented Aug 9, 2018

The following list of changes has been integrated into ros_comm 1.14.3 (Melodic) since the last Lunar release (1.13.6).

Commits before branching: some commits were made after the 1.13.6 release before the branch for Melodic was created. Those are therefore the same on the Lunar and Melodic branch. They won't be enumerated here.

Backported: (these changes are part of this PR)

Not backported:

@ros/ros_team @ros/ros_comm-maintainers RFC.

alspitz and others added 12 commits August 9, 2018 14:45
* Template std::max instead of casting explicitly.
* Change to force a rebuild of the pollset on flag changes

This change fixes issues seen in #1357, resulting from #1281
* Handle RLIM_INFINITY

* XmlRpcServer: use unsigned int for rlimit

* Properly link xmlrpcpp tests

* Exclude test libraries from all target

* Symbol overriding for OSX

* fix signed / unsigned comparison warning
Signed-off-by: Chris Lalancette <clalancette@gmail.com>
* Make a copy of the topic list

get_topics() returns a set, which is iterated by the Log constructor.
Make a copy of the set (atomic in cpython!) so nobody adds or removes
something while the Log constructor iterates over it

* Revert "Make a copy of the topic list", Fix

This reverts commit 0e019e0.
Move the fix to the _TopicManager so anybody else calling get_topics doesn't get burned by the same issue as _rosout
…1450)

* Rename getLastestTime to getLatestTime

Per directions [here](#1449 (comment)).

* Test getLatestTime instead of getLastestTime

per #1449 (comment)
@dirk-thomas dirk-thomas self-assigned this Aug 9, 2018
@mikepurvis
Copy link
Member

Looks like good picks to me.

@bmagyar
Copy link
Contributor

bmagyar commented Aug 11, 2018

I would like to request #1464 to be added to the backported list.

I wouldn't really call it a new feature, it is only a minor getter that allows to avoid hacking around this issue in user code. This is especially desired as Kinetic is likely to stay around for a while within companies using ROS: many haven't even left Indigo yet, let alone planning to move to Melodic.

@dirk-thomas
Copy link
Member Author

This is especially desired as Kinetic is likely to stay around for a while within companies using ROS: many haven't even left Indigo yet, let alone planning to move to Melodic.

This on it's own is not a real argument because at the same time these users demand stability. That is ultimately the reason why we have distributions and changes to existing distros are limitted to bug fixes (since any change has the potential to introduce regressions).

I wouldn't really call it a new feature, it is only a minor getter that allows to avoid hacking around this issue in user code.

That being said I agree with you that #1464 is a very small API addition which should be safe to backport to provide the convenience not to pass the information in parallel. 👍

I cherry-picked the corresponding commit in d80aa6d and updated the above description.

@dirk-thomas
Copy link
Member Author

The following change wasn't backported as part of this (or any future) backport PR:

fix compiler warnings about unused variables (#1428)

Not necessary

The change has been backported separately to Lunar (#1610) and to Kinetic (#1578.)

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.