{"push_id":2335702080,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"73e17314732faf33224987fc37df9c3860296888","before":"6d764735d00ca9782b4bbbac777b8709f8a0aa9c","commits":[{"sha":"73e17314732faf33224987fc37df9c3860296888","author":{"name":"lukes","email":"80786a5d5c765d810dc52f177d75422290d13593@google.com"},"message":"Fix a bug in AbstractFuture.setFuture\n\nIf the future being assigned was cancelled then there could be slightly different behavior based on whether or not the wasInterrupted bit is set and whether or not it was a TrustedFuture.  The fix is to never propagate the wasInterrupted bit from setFuture.\n\nThis also fixes the potentially confusing behavior where wasInterrupted could be true but interruptTask() would never be called.\n\nFor all these reasons, it remains the case that setFuture can never cause interruptTask to be invoked.\n\n-------------\nCreated by MOE: https://github.com/google/moe\nMOE_MIGRATED_REVID=162767529","distinct":true,"url":"https://api.github.com/repos/ChenZhangg/google_guava_0/commits/73e17314732faf33224987fc37df9c3860296888"}]}
{"actor":{"display_login":"ChenZhangg"}}