)]}'
{
  "commit": "08d8bb827574b4cd8c94a4212c9abac2b353795a",
  "tree": "cb9422e806211577635afffbc82179c60e237d75",
  "parents": [
    "6f794ed1da16aefbb7774d58c46af58a7e1895bd"
  ],
  "author": {
    "name": "Alejandro Nijamkin",
    "email": "nijamkin@google.com",
    "time": "Tue Jan 31 16:13:25 2023 -0800"
  },
  "committer": {
    "name": "Ale Nijamkin",
    "email": "nijamkin@google.com",
    "time": "Thu Feb 02 14:00:11 2023 +0000"
  },
  "message": "Fixes instant crash in WPP.\n\nTurns out that getClocks() can return a collection that has no clock\nthat matches the ID returned from getCurrentClockId().\n\nAlso, getCurrentClockId() is accessing Settings (which is a content\nprovider) on the main thread. A separate bug has been filed to fix that\nin the ClockRegistry. This CL offers a workaround of moving the\nexpensive call to the background and for doing it only once instead of\nup to N times each time.\n\nFix: 267356108\nTest: WPP no longer crashes. Clocks screen shows the textual list of clocks.\nChange-Id: I91eb54697feea53db89f297b7fa2d045028246ae\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "581c233c177a63bb741fb3607ca7b0cad395f640",
      "old_mode": 33188,
      "old_path": "src/com/android/customization/module/ThemePickerInjector.kt",
      "new_id": "c9581239e5193276c21f47b93aa3d805d813079e",
      "new_mode": 33188,
      "new_path": "src/com/android/customization/module/ThemePickerInjector.kt"
    },
    {
      "type": "modify",
      "old_id": "d5830e21a8c614c2355f2d30fda1d8b4b1828062",
      "old_mode": 33188,
      "old_path": "src/com/android/customization/picker/clock/data/repository/ClockPickerRepositoryImpl.kt",
      "new_id": "f6b051429f651006ec33b6996e4e65f9cf976e75",
      "new_mode": 33188,
      "new_path": "src/com/android/customization/picker/clock/data/repository/ClockPickerRepositoryImpl.kt"
    }
  ]
}