{"push_id":2917997714,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"975493c65537fb6567bb98c06e36665972623ba1","before":"712a4b9b4185d420345c6b10a4e2897543993ad1","commits":[{"sha":"05b5f668b947ea0818d5a7d45b614b109750605c","author":{"name":"Brandon L Black","email":"cce9d77514b9917b5a73e1e2309f2c85ad811e0b@gmail.com"},"message":"acme-dns-01: send LATR after data recv\n\nSending the RESP_LATR response (in case of ongoing replace)\nimmediately in response to the request doesn't really leave the\nconnection in a useful state on the server side, as the client\nwill continue to send challenge data anyways and only looks for\nthe response afterwards.  This change re-arranges things so that\nwe always consume the data the client sends (when within\nlegitimate bounds) first, and then respond with one of RESP_LATR,\nRESP_FAIL, or RESP_ACK as appropriate.","distinct":true,"url":"https://api.github.com/repos/gdnsd/gdnsd/commits/05b5f668b947ea0818d5a7d45b614b109750605c"},{"sha":"975493c65537fb6567bb98c06e36665972623ba1","author":{"name":"Brandon L Black","email":"cce9d77514b9917b5a73e1e2309f2c85ad811e0b@gmail.com"},"message":"Add LATR support to acme-dns-01-flush\n\nWe may as well do this, so that integrations that really need to\nbe able to flush reliably can properly defer until after a replace\noperation has copied over the challenge data and the new daemon is\nready to flush.","distinct":true,"url":"https://api.github.com/repos/gdnsd/gdnsd/commits/975493c65537fb6567bb98c06e36665972623ba1"}]}
{"actor":{"display_login":"blblack"}}