)]}'
{
  "commit": "1fde167ae683982d77b9ca7e1308bf9f498291e8",
  "tree": "9f33aa4a4b7dd3a10bac3a4134c39743a9cd526e",
  "parents": [
    "86772f20cca54b46f62b65ece1ef61224aef09db"
  ],
  "author": {
    "name": "Kai Ninomiya",
    "email": "kainino@chromium.org",
    "time": "Fri Jul 11 17:44:39 2025 -0700"
  },
  "committer": {
    "name": "Kai Ninomiya",
    "email": "kainino@chromium.org",
    "time": "Fri Jul 11 17:44:39 2025 -0700"
  },
  "message": "[M138] [dawn][native] Split maxImmediateSize into a separate limits group\n\nTiering is applied per group of limits such that if any of tier (n+1)\ncan\u0027t be supported, all limits go down to tier (n). maxImmediateSize\nshouldn\u0027t be grouped with the OTHER limits because its tiers don\u0027t line\nup with the others, causing maxVertexAttributes to be lowered\nunnecessarily (it\u0027s the only limit in the OTHER group that varies from\ntier0 to tier1).\n\nFixed: 430603273\nTest: manually checked webgpureport.org in local windows chromium build\nBug: 430371785\nChange-Id: Ibd1901c08aed2d471591adc4755a802ca866a1bd\nReviewed-on: https://dawn-review.googlesource.com/c/dawn/+/251574\nAuto-Submit: Kai Ninomiya \u003ckainino@chromium.org\u003e\nReviewed-by: dan sinclair \u003cdsinclair@chromium.org\u003e\nCommit-Queue: Kai Ninomiya \u003ckainino@chromium.org\u003e\nReviewed-by: Loko Kung \u003clokokung@google.com\u003e\n(cherry picked from commit 2113eec7a2b9c0b3cb21a98c6239baa7ca865466)\nReviewed-on: https://dawn-review.googlesource.com/c/dawn/+/251754\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3a76cb033c19a26dc498137c394ebe8a08fdf14b",
      "old_mode": 33188,
      "old_path": "src/dawn/native/Limits.cpp",
      "new_id": "49b4e34759ca5350e65163c1ee016aec8a15b069",
      "new_mode": 33188,
      "new_path": "src/dawn/native/Limits.cpp"
    }
  ]
}