{"push_id":1213355071,"size":2,"distinct_size":2,"ref":"refs/heads/fix-277-v2-minimal","head":"defc1fe3658329dfb9fdd072409a243e4fbf2d0f","before":"724de082d410319c1119bedc1d372af0b3b57b60","commits":[{"sha":"f97cf04712b45a8a65c936995b3f9bd68982ba0a","author":{"name":"Menno Smits","email":"d3684fb36535b0b5fbacc807bccfae70f905ded7@freshfoo.com"},"message":"Handle upsert duplicate key errors correctly if retries run out\n\nThe handling of the duplicate key error was wrong if the maximum number\nof upsert retries was reached. The final error would be ignored.\n\nRestructure the upsert retry logic to account for this.\n\nAlso remove unwanted logging about retries.","distinct":true,"url":"https://api.github.com/repos/babbageclunk/mgo/commits/f97cf04712b45a8a65c936995b3f9bd68982ba0a"},{"sha":"defc1fe3658329dfb9fdd072409a243e4fbf2d0f","author":{"name":"Christian Muirhead","email":"85ff0d17bfb1515851b27ce919eed201c1707f8f@canonical.com"},"message":"Clarify \"retries\" and make upsert retry loops consistent\n\nQuery.Apply would attempt upserts one more time because of the later\nloop check. Change the interpretation of maxUpsertRetries to exclude the\nfirst attempt, which makes the name more accurate.","distinct":true,"url":"https://api.github.com/repos/babbageclunk/mgo/commits/defc1fe3658329dfb9fdd072409a243e4fbf2d0f"}]}
{"actor":{"display_login":"babbageclunk"}}