{"push_id":669305119,"size":1,"distinct_size":1,"ref":"refs/heads/bug/lost-connection-exception","head":"f665308473fb84d03b5a5084d18d1443fea376af","before":"46b1e34ae7da5dff4fd843ba3e370a57071262e7","commits":[{"sha":"f665308473fb84d03b5a5084d18d1443fea376af","author":{"email":"a4595b0da37bd168d3d296ad0ec35d53d79873ef@gmail.com","name":"Mike Lenzen"},"message":"Added new exceptions and logic to allow for designing programs that \nautomatically reconnect on a lost connection\n\nAdded ConnectionClosedError and ConnectionLostError.\nConnectionClosedError is raised when the connection is closed normally,\nConnectionLostError is raised when the connection is lost unexpectedly.\ncleanup\nSend poison pill when the connection is closed so that cleanup methods\n(Channel.close, Connection.close, Consumer.cancel) do not block waiting\nfor a message from the server on a closed connection.\nFixes from experience with an actual example script\nconsistently handle setting futures inside syncronizer when poison pill\nis swallowed","distinct":true,"url":"https://api.github.com/repos/lenzenmi/asynqp/commits/f665308473fb84d03b5a5084d18d1443fea376af"}]}