)]}'
{
  "commit": "afb24239828efefbd08c04197c00e4b3b406de7a",
  "tree": "3bbd49af38463b9dd46de123b6c4cf691efa81dd",
  "parents": [
    "85b5558531b11399139c1ed3b897c6d8bb7df7a7"
  ],
  "author": {
    "name": "Luca Milanesio",
    "email": "luca.milanesio@gmail.com",
    "time": "Sat Apr 20 22:24:08 2024 +0100"
  },
  "committer": {
    "name": "Luca Milanesio",
    "email": "luca.milanesio@gmail.com",
    "time": "Thu Jul 04 21:21:08 2024 +0000"
  },
  "message": "Check for existence of change\u0027s target SHA1 for reindexing\n\nWhen the target branch of a change was advancing rapidly,\nthe reindexing retries applied by the ForwardedIndexingHandlerWithRetries\nwere continuing potentially forever as they were waiting to\nsee the target branch\u0027s expected SHA1 for the event.\n\nWhilst it is vital to wait for a target branch SHA1 to appear before\nreindexing a change on a remote site, it isn\u0027t essential to have\nthat SHA1 being *exactly* the tip of the target branch, as that\nmoment can be easily missed.\n\nExample:\n- Create two changes C1 and C2 in parallel and push them with\n  %submit option\n- The changes C1 and C2 will trigger the rapid advance of their\n  target SHA1\n- The other nodes may reindex C1 but not C2 because the target branch\n  has advanced more than expected\n\nChecking simply the existence of the target SHA1 in the repository\nis enough to satisfy the conditions for the change being reindexed.\n\nBug: Issue 335353379\nChange-Id: Ife361ec3378a60c0d1eb15df0f9570d569adc07a\n(cherry picked from commit 89d497605c85b3422f2b6958cca1df3fc2dd532f)\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "063d7bfcd75223587690bcb8a194f0da719645ff",
      "old_mode": 33188,
      "old_path": "src/main/java/com/googlesource/gerrit/plugins/multisite/index/ChangeCheckerImpl.java",
      "new_id": "54dcca6fc689aec6c820b01b79e1c9143c3ad158",
      "new_mode": 33188,
      "new_path": "src/main/java/com/googlesource/gerrit/plugins/multisite/index/ChangeCheckerImpl.java"
    }
  ]
}