-
Notifications
You must be signed in to change notification settings - Fork 911
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
AttributeError: 'NoneType' object has no attribute 'close' #2212
Comments
@jacobperron friendly ping |
The error message makes it sound like it's a bug in rospy. @MatthijsBurgh Can you provide simple steps to reproduce the error? |
@jacobperron I will get back to you when I have been able to isolate the issue into a reproducible error. The situation in which I experienced this error the first time, was in a node launching other nodes. Now I also experience this in nodes with an action_server simple_client. In both situations it happens during stopping of a node.
|
This is most likely a race condition due to a previous We also experienced different cases where either the socket or the buffers were called as |
The complete solution of this issue would require to rewrite the classes to be thread safe. Anyway, a opened a PR with a workaround here: #2233 |
@jacobperron What do you think about #2233? Or would like to go for some locks? |
#2233) Co-authored-by: Daniele Calisi <calisi@magazino.eu>
I've merged the workaround. Thanks @madmage! |
Hi there, import rospy
from sensor_msgs.msg import JointState
import rospy
from sensor_msgs.msg import JointState
def main():
rospy.init_node('test', anonymous=True)
while not rospy.is_shutdown():
js = rospy.wait_for_message('/iiwa/joint_states', JointState, timeout=5)
print(list(js.position))
if __name__ == '__main__':
main() As the workaround in #2233 , a multi-thread set needed, but how can do it in single node and single thread case? Thanks in advance! |
I have no clue of the following exception is caused by incorrect implemetnation on my side or caused by a bug in rospy.
The text was updated successfully, but these errors were encountered: