)]}'
{
  "commit": "2bea1ef4dc0557cdae8d5db012c3b65928db7904",
  "tree": "a6d769fc3449e7b6c59fedea5e5406cfd3a5111e",
  "parents": [
    "284b9ddf35f10d0455919ff067698d1d7d887037"
  ],
  "author": {
    "name": "Spandan Das",
    "email": "spandandas@google.com",
    "time": "Fri Apr 11 22:34:59 2025 +0000"
  },
  "committer": {
    "name": "Spandan Das",
    "email": "spandandas@google.com",
    "time": "Fri Apr 11 22:45:09 2025 +0000"
  },
  "message": "Skip overrides removal of native bridge modules in fsgen\n\nfsgen\u0027s `removeOverriddenDeps` automatically removes all entries in `overrides`\nfrom the autogenerated partitions to handle scenarios where a module in\none partition overrides a module in another partition. This automatic\nremoval runs into issues for some native bridge cc modules that override\nthe native bridge variant of another module, but not the \"main\" variant.\n```\ncc_binary {\n   name: \"foo\",\n   native_bridge_supported: true,\n   overrides: \"bar\" \u003c-- LOCAL_OVERRIDES_MODULE bar.native_bridge\n}\ncc_binary {\n   name: \"bar\",\n}\n```\n\nIn the above example, both native bridge variant of foo and the \"main\"\nbar variant will be installed, even though the latter is listed in\noverrides.\n\nThis CL assumes that all native bridge modules are installed in system\n(no interpartition communication), and skips processing native bridge\nvariants in `removeOverriddenDeps`\n\nTest: lunch cf_x86_64_phone-trunk_staging-userdebug\nTest: m soong_generated_system_filesystem_test\nBefore and after diffs https://diff.googleplex.com/#key\u003d0ZrQcQmklDVR\n\nBug: 376873507\nBug: 375035189\nChange-Id: I280c550a7e10593c1e74c3ebf379161ec5c57e00\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e5f245b1d67f358046bd2216acc8e9a06568ff50",
      "old_mode": 33188,
      "old_path": "fsgen/fsgen_mutators.go",
      "new_id": "2565b009b2c5fa5060fef746196b95c8b80b0e56",
      "new_mode": 33188,
      "new_path": "fsgen/fsgen_mutators.go"
    }
  ]
}