{"push_id":2893849190,"size":1,"distinct_size":1,"ref":"refs/heads/MAID-3036","head":"9e81f55e58db5a80c941de5c838a43ec00c8a0d3","before":"9f48ea9c5229417ad9589e0ed3e8e00921002bbd","commits":[{"sha":"9e81f55e58db5a80c941de5c838a43ec00c8a0d3","author":{"name":"Fraser Hutchison","email":"ac12578a32f18141cf4141be6495c58eeebd578a@maidsafe.net"},"message":"fix/parsec: resolve add_event issues\n\nThis ensures that when a new node is handling its initial request from a\npeer which will contain the entire graph, it places all these events\nbefore its own ones in the 'events_order' list.  So now, when forming\nits response, it skips all these events which it has just been given and\nonly includes its own.\n\nIt also fixes an associated issue whereby we were sending events to a\npeer which included each of the last ancestors of that peer's latest\nevent, rather than all the ones newer than those.","distinct":true,"url":"https://api.github.com/repos/Fraser999/parsec/commits/9e81f55e58db5a80c941de5c838a43ec00c8a0d3"}]}
{"actor":{"display_login":"Fraser999"}}