{"push_id":1141666874,"size":1,"distinct_size":1,"ref":"refs/heads/system_call_interrupts","head":"d9699ac307812d20fd2a53c6c2f3e962cfc1cf12","before":"1d81425317df690e2633e06bc311dc7bb8072534","commits":[{"sha":"d9699ac307812d20fd2a53c6c2f3e962cfc1cf12","author":{"name":"Thomas Jackson","email":"79d4e65b640d9611e34e2b00fbd8ed07cd741715@gmail.com"},"message":"Handle system interrupts during socket.create_connection\n\nThis is in a similar vein to #250, but the root cause of this issue is actually an upstream python issue (http://bugs.python.org/issue20611) which is not fixed in 2.x or <3.5. Python doesn't handle interrupted system calls-- so the applications are responsible for doing so.\n\nThis patch simply retries the create_connection call on system call interrupt, while honoring the original timeout request.\n\nNote: although the timeout for `create_tcp_connection` will be honored, if there are interrupts each subsequent call to `create_connection` will have less time to complete.","distinct":true,"url":"https://api.github.com/repos/jacksontj/kazoo/commits/d9699ac307812d20fd2a53c6c2f3e962cfc1cf12"}]}
{"actor":{"display_login":"jacksontj"}}