)]}'
{
  "commit": "0de7bb95022057e8b89334f44759cf6f950e131f",
  "tree": "9a10c1fa5262a437d52f02b3162923f6cd154e90",
  "parents": [
    "07812ff95355e3fe07a684dcab596c24a92b8a29"
  ],
  "author": {
    "name": "Oscar Bonilla",
    "email": "6f6231@gmail.com",
    "time": "Mon Jan 17 03:05:01 2022 -0800"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Mon Jan 17 03:06:09 2022 -0800"
  },
  "message": "Don\u0027t resolve symlinks for --sandbox_base\n\nOn macOS BigSur, the sandbox-exec command behaves slightly different than on\nCatalina when firm links are present.\n\nResolving symlinks can prevent the sandbox for allowing write operations to the\nsandbox base.\n\nThis effectively reverts a piece of 656a0ba, namely:\n\n\u003e  When using --experimental_sandbox_base, ensure that symlinks in the path are\n\u003e  resolved. Before this, you had to check whether on your system /dev/shm is a\n\u003e  symlink to /run/shm and then use that instead. Now it no longer matters, as\n\u003e  symlinks are resolved.\n\nSee https://github.com/bazelbuild/bazel/issues/13766 for full details.\n\nCloses #13984.\n\nPiperOrigin-RevId: 422319807\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0f73a413d97bde2427b792d0cead26af8506590a",
      "old_mode": 33188,
      "old_path": "src/main/java/com/google/devtools/build/lib/sandbox/SandboxModule.java",
      "new_id": "1f2b1c104a9dcc46f4c783f96dddb16a74f505ef",
      "new_mode": 33188,
      "new_path": "src/main/java/com/google/devtools/build/lib/sandbox/SandboxModule.java"
    }
  ]
}