)]}'
{
  "commit": "b02a3e3c93f8fff940bdb8a4d16cd07438450417",
  "tree": "fd7f81baf74dd4595e95586d5d083ffc70fda835",
  "parents": [
    "2e6ffe81427ad18761269d30cb4822d397c6fc1b"
  ],
  "author": {
    "name": "Ben",
    "email": "benlawson@fuchsia.infra.roller.google.com",
    "time": "Mon Mar 16 12:15:03 2026 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Mon Mar 16 12:17:03 2026 -0700"
  },
  "message": "[roll] Roll fuchsia [bt][snoop] Collect and report controller core dumps\n\nMonitor incoming HCI traffic for vendor-specific crash diagnostic\nevents and automatically trigger the collection of core dumps.\n\nWhen a crash event is detected, bt-snoop creates a VMO and captures\nsubsequent HCI traffic into a PCAP-formatted core dump. The\ncollection window is debounced to avoid spamming reports. After the\nwindow closes, the collected dump is submitted as an attachment to\nthe fuchsia.feedback.CrashReporter service.\n\nAdditionally, restructure state management using a CrashState struct\nto track concurrent dump collections across devices, and adopt\nfuchsia_async timing primitives to ensure reliable unit test behavior.\n\nOriginal-Bug: 488367063\nMultiply: bt-snoop-unittests\nTest:\n1) fx test bt-snoop-unittests\n2) fx shell bt-fct-hci raw 1c fd 01 f5\n3) verify crash report at go/crash/79d398af0543da41\n\nOriginal-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1529980\nOriginal-Revision: acc1183aff3ece8c56f01d6b4c648b207bc10117\nGitOrigin-RevId: 8c67000059a2bd417b26c1e6336abe91a9c0d9b4\nChange-Id: Ic0c264388700899548ad8aa48730c34da8236b2e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0d7585061676475214cf960ca44a26169f2030f2",
      "old_mode": 33188,
      "old_path": "stem",
      "new_id": "395adba372094476da66c5c26f415c3ee5b5da42",
      "new_mode": 33188,
      "new_path": "stem"
    }
  ]
}