)]}'
{
  "commit": "1268e50f21392da291b8a2db11383195f2b75c6e",
  "tree": "7086e45e2456e5ef8200ba63dec1887e05af89d7",
  "parents": [
    "eb6f406143568b1d73d9d81ad3474c435b166392"
  ],
  "author": {
    "name": "Adam Perry",
    "email": "adamperry@fuchsia.infra.roller.google.com",
    "time": "Thu Dec 04 14:55:08 2025 -0800"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Thu Dec 04 14:56:34 2025 -0800"
  },
  "message": "[roll] Roll fuchsia [factory] std::sync -\u003e fuchsia_sync\n\nThe behaviors of fuchsia_sync\u0027s locks are very similar to those from\nthe standard library. std::sync::Mutex is a port of the libsync\nmutex that fuchsia_sync::Mutex links against, and fuchsia_sync::RwLock\nis very similar to the std::sync::RwLock\u0027s futex-based approach. However\nthere are some important differences:\n\n1. fuchsia_sync supports lock cycle detection which surfaces many\n    deadlocks. See the documentation[0] for more details.\n2. fuchsia_sync doesn\u0027t support lock poisoning because most of\n   Fuchsia\u0027s code is compiled with panic\u003dabort.\n    a. saves memory with smaller types\n    b. avoids noop error handling syntax and branches\n\n[0]: https://fuchsia.dev/fuchsia-src/development/debugging/lock_cycles\n\nOriginal-Bug: 465178981\nOriginal-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1439913\nOriginal-Revision: 9ccd517c1ef2ec02a61448e07da0b51e29387f5c\nGitOrigin-RevId: b4d2dc3fe12df2c40923c8d20fbe7fb067b9166e\nChange-Id: I6e1db9c9c1d43268cf2deb420a8cbfd6ed279a38\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7fae5a336572d3201d3f201c0288414202e0b37f",
      "old_mode": 33188,
      "old_path": "stem",
      "new_id": "9cff9523d1182bb54c194cb53f49795a83517c7a",
      "new_mode": 33188,
      "new_path": "stem"
    }
  ]
}