)]}'
{
  "commit": "aa313126da6bf3bf8b672173331e1ed02a635f8f",
  "tree": "da55a98b1ae16c954bd8c3f07c91859bd0f6f1bc",
  "parents": [
    "eb1f75e4232cac32454482b1c4460c468c4828d9"
  ],
  "author": {
    "name": "Jim Ray",
    "email": "jimray@google.com",
    "time": "Mon Mar 21 14:17:50 2022 -0700"
  },
  "committer": {
    "name": "Commit Bot",
    "email": "commit-bot@chromium.org",
    "time": "Wed Mar 30 22:51:00 2022 +0000"
  },
  "message": "Fix error when script_executable is not in PATH\n\nThis change fixes an unclear error message that can arise on Windows\nwhen the exe pointed to by script_executable in the .gn dotfile\ndoesn\u0027t exist in the user\u0027s PATH.\n\nIf this occurs, the following error is printed:\n\"\"\"\nERROR at //starboard/build/config/BUILDCONFIG.gn:15:15: Could not execute interpreter.\n\n\u003cexec_script that was attempted\u003e\n\nI was trying to execute \"\".\n\"\"\"\n\nThis occurs because the function that searches for the\nscript_executable in the PATH on a Windows machine returns an empty\nbase::FilePath if the exe isn\u0027t found. As such, check if this happens\nand return an Err that reports the problem.\n\nChange-Id: I963b01619f68cef2a951fafc4c66f274176e66e0\nReviewed-on: https://gn-review.googlesource.com/c/gn/+/13260\nReviewed-by: Brett Wilson \u003cbrettw@chromium.org\u003e\nCommit-Queue: Brett Wilson \u003cbrettw@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9dba72e0928a6d030fbcb2c372b62c99174d8013",
      "old_mode": 33188,
      "old_path": "src/gn/setup.cc",
      "new_id": "8f1bd7a5c237179ce18ff8f4943572492b23e8c8",
      "new_mode": 33188,
      "new_path": "src/gn/setup.cc"
    },
    {
      "type": "modify",
      "old_id": "370f7226c88baa2d694ea5586b04bdd6b5cb3061",
      "old_mode": 33188,
      "old_path": "src/gn/setup_unittest.cc",
      "new_id": "d905355a1ca836d930dc8eed646ce0cb2f69dd8a",
      "new_mode": 33188,
      "new_path": "src/gn/setup_unittest.cc"
    }
  ]
}