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

rosgraph/ifaddrs.py: Don't fail with tun devices. (#30) #32

Merged
merged 1 commit into from
Dec 6, 2012

Conversation

schneider42
Copy link
Contributor

No description provided.

dirk-thomas added a commit that referenced this pull request Dec 6, 2012
rosgraph/ifaddrs.py: Don't fail with tun devices. (#30)
@dirk-thomas dirk-thomas merged commit f02dca7 into ros:master Dec 6, 2012
rsinnet pushed a commit to MisoRobotics/ros_comm that referenced this pull request Jun 19, 2017
rosgraph/ifaddrs.py: Don't fail with tun devices. (ros#30)
dirk-thomas pushed a commit that referenced this pull request Feb 8, 2019
* If process died when checking should_respawn, treat it as over-due and respawn (#32)

* fix how the return value of should_respawn() is checked
tahsinkose pushed a commit to tahsinkose/ros_comm that referenced this pull request Apr 15, 2019
* If process died when checking should_respawn, treat it as over-due and respawn (ros#32)

* fix how the return value of should_respawn() is checked
dirk-thomas pushed a commit that referenced this pull request Aug 3, 2020
* If process died when checking should_respawn, treat it as over-due and respawn (#32)

* fix how the return value of should_respawn() is checked
dirk-thomas pushed a commit that referenced this pull request Aug 3, 2020
* If process died when checking should_respawn, treat it as over-due and respawn (#32)

* fix how the return value of should_respawn() is checked
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.

2 participants