)]}'
{
  "commit": "937b403a596d48d01f5fc1ce380b6d6558cb6051",
  "tree": "646002d8409d6424bbbdb488f9f9c50d22b4f5df",
  "parents": [
    "5c36d25ee92cfcfe48c0aa382eb8181985662472"
  ],
  "author": {
    "name": "Martin Fick",
    "email": "mfick@codeaurora.org",
    "time": "Thu May 07 18:19:29 2020 -0600"
  },
  "committer": {
    "name": "David Pursehouse",
    "email": "dpursehouse@digital.ai",
    "time": "Tue May 12 09:44:30 2020 +0900"
  },
  "message": "Don\u0027t lose state when there\u0027s a pending push to the same ref\n\nPreviously if there was already a pending push (not an in-flight push)\nto the same endpoint, the start for the push would be dropped when\nadding the push to the Destination. This meant that a replication start\n--wait command would never complete when one of its pushes was pending\nsince its state would never receive the completion notification for that\npush.\n\nFix this by always adding the state and the ref in the Destination class\nand preventing the duplicate \"addRef\" log message in the PushOne class.\n\nBug: Issue 12731\nChange-Id: I33e6af2709bc38aac791a2f60fd896492167bbf5\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "966248ac3021c648b77cbf0554939194072b6887",
      "old_mode": 33188,
      "old_path": "src/main/java/com/googlesource/gerrit/plugins/replication/Destination.java",
      "new_id": "f4c81332dc7ad3c6db6728246683305557d56ca4",
      "new_mode": 33188,
      "new_path": "src/main/java/com/googlesource/gerrit/plugins/replication/Destination.java"
    },
    {
      "type": "modify",
      "old_id": "8ccd54a70ef9a5588d3b2b8986549b7be9e8aa70",
      "old_mode": 33188,
      "old_path": "src/main/java/com/googlesource/gerrit/plugins/replication/PushOne.java",
      "new_id": "ee291622f7285f7143ab3ccbb5ae0cf9dbfb7cf1",
      "new_mode": 33188,
      "new_path": "src/main/java/com/googlesource/gerrit/plugins/replication/PushOne.java"
    }
  ]
}
