{"push_id":772581202,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"d41c81ef9c7234178c09cc8f912f34c3e1472d51","before":"707f74f4b87041859ca925a7bcd0afbac8417a85","commits":[{"sha":"d65fbbdd81cc91f9a13fdbb4c9da1454a5dfe970","author":{"email":"dfccc06f14414bff5a59be7fc90abf4404b47fc8@google.com","name":"Ross Light"},"message":"capnp: clarify that clients are safe to use from multiple goroutines","distinct":true,"url":"https://api.github.com/repos/zombiezen/go-capnproto/commits/d65fbbdd81cc91f9a13fdbb4c9da1454a5dfe970"},{"sha":"d41c81ef9c7234178c09cc8f912f34c3e1472d51","author":{"email":"dfccc06f14414bff5a59be7fc90abf4404b47fc8@google.com","name":"Ross Light"},"message":"server: add call queuing\n\nFixes #3 (mostly).\n\nSince an RPC connection's goroutine is responsible for the call order\nguarantee, it must block until Call returns an answer.  However, this\nleads to #3, where servers that make RPCs on the connection before\nAck'ing will deadlock.  Either the RPC implementation must add queueing\nor the server.  Server seemed like a more reasonable place to put the\nfunctionality.\n\nThere is still a possibility of deadlock, but it's only after the queue\nis full of unack'd calls.","distinct":true,"url":"https://api.github.com/repos/zombiezen/go-capnproto/commits/d41c81ef9c7234178c09cc8f912f34c3e1472d51"}]}