)]}'
{
  "commit": "5267d9877248f2531e5e6e4a1619eded8b6ae0ce",
  "tree": "069f487eec63352f2ca1d0a5fefb4b1f2c335ba2",
  "parents": [
    "3115c14e431fc2144316e5810207f777ec53bb8c"
  ],
  "author": {
    "name": "Greg Spencer",
    "email": "gspencergoog@users.noreply.github.com",
    "time": "Mon Jun 01 11:24:53 2020 -0700"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Jun 01 11:24:53 2020 -0700"
  },
  "message": "Revert flutter command to shlock when flock isn\u0027t available (#58281)\n\nThis reverts the flutter command to use shlock when flock isn\u0027t available. It seems that the mkdir method isn\u0027t as reliable as we want. I think that this is because the trap isn\u0027t always be executed, which is why I think that shlock uses PIDs to help it be more reliable. Unfortunately, that means that we\u0027re back to not working over network shares (which is where things were before I moved to the mkdir method, so not really a regression). I did leave in the mkdir method for platforms that have neither flock nor shlock (which should be very few and far between, but still), so at least we\u0027ll do some locking there now.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e490ac35ad8b8a5befb6164793c11d536042a109",
      "old_mode": 33261,
      "old_path": "bin/internal/shared.sh",
      "new_id": "702bd9ed5bdc6dcc2f0cef234e341ebcaed12d60",
      "new_mode": 33261,
      "new_path": "bin/internal/shared.sh"
    }
  ]
}