There is code which uses getNumPublishers() being positive as a
guarantee that a call to the remote publisher's publish() is
guaranteed to send a message to the subscriber. However, because
connections which have not yet received their header are counted,
this is not true. One such user of getNumPublishers() is actionlib.
It relies on getNumPublishers() only returning postive when a publish
on the result topic would succeed.

Fix this by only counting connections with received headers. If we
have received the header, we know the remote publisher is tracking a
connection back to us and has accepted the connection and that a
call to publish() on its end will send the message.

Note that this issue is only relevant for the TCP transport, as the
UDP transport and intraprocess link have already setup their header
by the time they are added to the publication links. Since all
publisher link types update the header, including the caller ID,
counting those with caller IDs set to non-empty is sufficient to
solve the issue.

* fix: roscore -> AttributeError: 'ProcessMonitor' object has no attribute 'isAlive'

* Fix AttributeError: 'Thread' object has no attribute 'isAlive'

* Update remaining instances of isAlive to is_alive

Keep mock method isAlive to keep backwards compatibility for users who happen to be using the mock object.

Signed-off-by: Jacob Perron <jacob@openrobotics.org>

Co-authored-by: Jacob Perron <jacob@openrobotics.org>

* Portable fix.

* include <climits>

* Adding missing headers.

* Adding #include <vector>

Fixes #2128

Fix bug "TypeError: not enough arguments for format string" in DeserializationError

Co-authored-by: 229143434@qq.com <zxcvbnm123-*@>
Co-authored-by: tomoya <Tomoya.Fujita@sony.com>

* Add unit test for removing a callback that's being executed.

This unit test fails until we can remove callbacks that are being executed.

* Use the marked_for_removal flag if the callback is being executed.

This fixes a potential deadlock when a timer is being removed that's also being executed.

All dependencies must be declared in the package.xml, and all these
dependencies must be in the ROS distro. rosmsg doesn't meet either of
these requirements today, by using but not depending on both rostest and
std_srvs, and by using test_rosmaster, which isn't in the ROS distro at
all.

Update rosmsg to properly depend upon what it requires, and stop using
test_rosmaster completely. In place of test_rosmaster, use
diagnostic_msgs, which satisfies the same requirements of the existing
tests by having both messages and services as well as standalone and
recursive messages.

Signed-off-by: Kyle Fazzari <kyle@canonical.com>

Addressing performance issues described in #2118

Signed-off-by: Jesse Ikawa <jikawa@amazon.com>

Co-authored-by: Emerson Knapp <537409+emersonknapp@users.noreply.github.com>

Signed-off-by: Martin Pecka <peckama2@fel.cvut.cz>

This is copy&paste from https://github.com/ros/ros_comm/pull/2038/files#diff-8c5ae1a482044f103bf9b2fa9188ff9639ed617f259a8dd816075bc9e4005ef9R152
where the SIGINT handler was added to rosbag record.