)]}'
{
  "commit": "61d2bf2d1cbc71dc0b0d37882551529cfd9a5c03",
  "tree": "3627164076e0b6906cf41cbdff3dbdee1af45e6f",
  "parents": [
    "e4c7095d9d9114e4050efdcbbb5204899ef7a3b6"
  ],
  "author": {
    "name": "Kai Ninomiya",
    "email": "kainino@chromium.org",
    "time": "Fri Sep 18 00:19:52 2026 -0700"
  },
  "committer": {
    "name": "dawn-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "dawn-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Fri Sep 18 00:19:52 2026 -0700"
  },
  "message": "[dawn][wire] Always crash on serialization errors\n\nCurrently OnSerializeError in Chromium is a debug-only NOTREACHED. To\nharden against sending junk to the GPU process, we can just crash\ninstead, and may as well do that in Dawn rather than going through the\nserializer interface to do it.\n\nOf course the GPU process doesn\u0027t trust wire data from the renderer\nanyway, but this makes it harder to bypass validation that happens in\nthe renderer process, like origin-clean checks.\n\nBug: 560062638\nChange-Id: I18a0072cde7246e7eea0dd3a6c66ee37eec7147a\nReviewed-on: https://dawn-review.googlesource.com/c/dawn/+/342276\nCommit-Queue: Kai Ninomiya \u003ckainino@chromium.org\u003e\nReviewed-by: Corentin Wallez \u003ccwallez@chromium.org\u003e\nReviewed-by: Loko Kung \u003clokokung@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5b887aeac0039f63becd19c6efeb64a7ded32385",
      "old_mode": 33188,
      "old_path": "include/dawn/wire/Wire.h",
      "new_id": "2e2eb360554b3c8a0706b04869e80ab61cfa534d",
      "new_mode": 33188,
      "new_path": "include/dawn/wire/Wire.h"
    },
    {
      "type": "modify",
      "old_id": "474ba90ea8b100473a3456e4025e9919f30caccd",
      "old_mode": 33188,
      "old_path": "src/dawn/wire/ChunkedCommandSerializer.h",
      "new_id": "2483ebde7857b4d2e66aea407ee99c6a8c4e7fa7",
      "new_mode": 33188,
      "new_path": "src/dawn/wire/ChunkedCommandSerializer.h"
    }
  ]
}