)]}'
{
  "commit": "11ab3f92ed451db8c1e1366abcddd9c202e0738d",
  "tree": "bfa0ce452ad1e769947e8a4e88c31318d4d07839",
  "parents": [
    "9c5cdb25bf88bcc0346f5acac9b0c21bfea80de9"
  ],
  "author": {
    "name": "Lokbondo Kung",
    "email": "lokokung@google.com",
    "time": "Wed Jun 24 22:36:03 2026 -0700"
  },
  "committer": {
    "name": "dawn-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "dawn-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Wed Jun 24 22:36:03 2026 -0700"
  },
  "message": "[wire][client] Make buffer mapping in the client thread-safe.\n\n- Since the wire can now be multithreaded in Chrome, we need to make\n  sure that the buffer mapping mechanisms are thread-safe. This\n  change uses a recursive lock like we do in native to ensure that\n  the mapping states are consistent across atomic operations. This\n  change also now guarantees that calling GetMappedRange or any\n  equivalents while in a successful map async callback always\n  succeeds.\n\nBug: 503971615, 523580515\nChange-Id: I3f173d3a314fdc9984dd813ce772bc486c9c31be\nReviewed-on: https://dawn-review.googlesource.com/c/dawn/+/317816\nReviewed-by: Corentin Wallez \u003ccwallez@chromium.org\u003e\nReviewed-by: Kai Ninomiya \u003ckainino@chromium.org\u003e\nCommit-Queue: Loko Kung \u003clokokung@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "53805f144cf0a0f905867d517c0634282df8abb0",
      "old_mode": 33188,
      "old_path": "src/dawn/wire/client/Buffer.cpp",
      "new_id": "fcfebbd34013b9b730216debc0111354d9c03958",
      "new_mode": 33188,
      "new_path": "src/dawn/wire/client/Buffer.cpp"
    },
    {
      "type": "modify",
      "old_id": "8e41b71edfaa042722b9c404c2e925492daf2da2",
      "old_mode": 33188,
      "old_path": "src/dawn/wire/client/Buffer.h",
      "new_id": "ccacc8c69831b9e87c8a8882cd6de409cfb905f5",
      "new_mode": 33188,
      "new_path": "src/dawn/wire/client/Buffer.h"
    }
  ]
}