)]}'
{
  "commit": "429c28c783fe953e113c83c61118585bf539cf53",
  "tree": "bb185a28d30619705a921111f2da6e3f0bc4cb21",
  "parents": [
    "e5a9ff757f94ec6f3fb62c8f2c8a9618fc6d63e2"
  ],
  "author": {
    "name": "brianmacy",
    "email": "brianmacy@gmail.com",
    "time": "Wed Feb 04 09:00:44 2026 -0500"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Feb 04 09:00:44 2026 -0500"
  },
  "message": "fix(rust): Zero vtable memory in write_vtable to prevent uninitialized data (#8898)\n\nThe write_vtable() function\u0027s comment claimed to \"fill the WIP vtable\nwith zeros\" but make_space() only reserves memory without initializing\nit. When using custom allocators with non-zeroed buffers, unset vtable\nfield entries would contain garbage instead of zero (which indicates\n\"use default value\").\n\nThis fix explicitly zeros the vtable memory after reserving space,\nmatching the C++ implementation\u0027s buf_.fill_big() behavior.\n\nAdded regression test using a garbage-filled allocator (0xAA) that\nverifies vtable entries for unset fields are properly zeroed.\n\nFixes #8894",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d8a6e81dc7f8a107bfbe4b123425df8f23722185",
      "old_mode": 33188,
      "old_path": "rust/flatbuffers/src/builder.rs",
      "new_id": "84bb622580a3de4e0b3cc64a3567387882dac89c",
      "new_mode": 33188,
      "new_path": "rust/flatbuffers/src/builder.rs"
    },
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "401bc2fcf4bd8ffd36fbebce1bdab1debb70c12e",
      "new_mode": 33188,
      "new_path": "tests/rust_usage_test/tests/vtable_zeroed_test.rs"
    }
  ]
}