{"ref":"refs/heads/flatiron-1.4","commits":[{"author":{"name":"Angus Salkeld","email":"86b65304d27d8de73dd7d624c33df7e088f8d94b@redhat.com"},"sha":"9ddb845f412531b6a2761f42823b6be43216a9c8","message":"Add calls to missing object_find_destroy() to fix mem leaks\n\nSigned-off-by: Angus Salkeld <asalkeld@redhat.com>\nReviewed-by: Steven Dake <sdake@redhat.com>","url":"https://api.github.com/repos/corosync/corosync/commits/9ddb845f412531b6a2761f42823b6be43216a9c8"},{"author":{"name":"Yunkai Zhang","email":"e26ac62a79d9fc94a9c5bc37cc25f41a4f1ed37e@taobao.com"},"sha":"ffe4943ff52843e1c7beba1250256dc7b6f283e4","message":"Fixed bug when corosync receive JoinMSG in OPERATIONAL state\n\nAccordig the totem protocal, nodes should enter GATHER state when it\nreceive JoinMSG in OPERATIONAL state. If we discard it in OPERATIONAL\nstate, the nodes sending this JoinMSG could not receive the response\nuntill other nodes reach token lost timeout.\n\nThis bug will cause nodes having entered GATHER state spend more time to\nrejoin the ring, and then it will make nodes reach token expired timeout\nmore easily.\n\nSigned-off-by: Yunkai Zhang <qiushu.zyk@taobao.com>\nReviewed-by: Steven Dake <sdake@redhat.com>\n(cherry picked from commit d991400372603f2b42b0697614a39712f00fa52d)","url":"https://api.github.com/repos/corosync/corosync/commits/ffe4943ff52843e1c7beba1250256dc7b6f283e4"}],"head":"ffe4943ff52843e1c7beba1250256dc7b6f283e4","push_id":51590584,"size":2}