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.15.8 (Noetic) and 1.14.6 for backporting into Melodic #2008

Merged
merged 4 commits into from
Jul 24, 2020

Conversation

dirk-thomas
Copy link
Member

The following list of changes has been integrated into ros_comm 1.15.8 (Noetic) since the last Melodic release (1.14.6).

Backported: (these changes are part of this PR)

Not backported:

peci1 and others added 4 commits July 24, 2020 09:50
This allows to force the advertised throttled publisher to be latched or
not, instead of using the same latching property value as the input
topic.

It defaults to the previous behaviour, i.e. it uses the same latching
property value as the input topic.
* Add which node has been registered with the same name

Was looking through logs of several nodes that had been launched at the same time and it was getting hard to tell which node was being duplicated. This would allow you do to see the name of the node that caused the issue

* switch to shutdown_node_task
@dirk-thomas dirk-thomas mentioned this pull request Jul 24, 2020
@dirk-thomas dirk-thomas merged commit f11086c into melodic-devel Jul 24, 2020
@dirk-thomas dirk-thomas deleted the backports_melodic branch July 24, 2020 19:15
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.

4 participants