)]}'
{
  "commit": "8383c46b129c2b3a5f3833e602d946d2fcc57e39",
  "tree": "c6e4a35cfbd45f6049ce687ec0c86dc20aa4f5db",
  "parents": [
    "28d3b5930a6da0e4f15040679d8b51dda0b29c86"
  ],
  "author": {
    "name": "spatel2-samsung",
    "email": "s.patel2@samsung.com",
    "time": "Wed Apr 15 22:41:59 2026"
  },
  "committer": {
    "name": "Spencer Fricke",
    "email": "115671160+spencer-lunarg@users.noreply.github.com",
    "time": "Wed May 20 19:29:36 2026"
  },
  "message": "scripts: Improve SafePNextCopy for unknown structs\n\nIf a pNext chain contains unknown structure, the current code will\nskip it by not updating prev_pNext. When a known structure is\nencountered later, the chain will be re-sewn to exclude the custom\nstructure. However, if the unknown structure is at the very end,\nthe current code will not repair the pNext pointer of prev_pNext.\nThus the safe copy of the chain will still contain an unsafe pNext\npointer at the end.\n\nThis commit fixes this issue by setting prev_pNext-\u003epNext on every\niteration, even if prev_pNext itself is not updated. If safe_pNext\nis itself a nullptr, we should still overwrite prev_pNext-\u003epNext\nso as not to leave an unsafe value there. If later a known\nstructure is seen, this nullptr will be overwritten and the\ncurrent functionality will remain the same.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0bd6e0ffa0f74e80cf57973f67f0630e81633444",
      "old_mode": 33188,
      "old_path": "scripts/generators/safe_struct_generator.py",
      "new_id": "3c9632be09024efa40fcb0c313440c304507b6d0",
      "new_mode": 33188,
      "new_path": "scripts/generators/safe_struct_generator.py"
    },
    {
      "type": "modify",
      "old_id": "7cc6de45919627040ff12c4c63b63802d96a673a",
      "old_mode": 33188,
      "old_path": "src/vulkan/vk_safe_struct_utils.cpp",
      "new_id": "670054e6c380d0b6069d0b324a38a70c02f7eb38",
      "new_mode": 33188,
      "new_path": "src/vulkan/vk_safe_struct_utils.cpp"
    }
  ]
}