)]}'
{
  "commit": "6e865c2ac36c0a0dbc1fc67e5f6167a0974f2ffe",
  "tree": "5d68d9db1538a79dce9a7fc5837a5e437dc2c9c6",
  "parents": [
    "e375dd862dbaf130cd4b6d1aea7c240f2cf9876f"
  ],
  "author": {
    "name": "Paul Hammant",
    "email": "paul@hammant.org",
    "time": "Fri Jan 20 17:52:59 2023"
  },
  "committer": {
    "name": "Paul Hammant",
    "email": "paul@hammant.org",
    "time": "Fri Jan 20 17:52:59 2023"
  },
  "message": "for discussion - a change to exception handling that originates in chromedriver.exe. Specifically, while \u0027this version of chromedriver supports v111 and /full/path/to/chrome.exe is v112\u0027 is a decent message, it does not communicate where \u0027this\u0027 is as a fully qualified path. A try/catch/wrap/rethrow strategy can add the extra path detail that was missing. This may be useful to end users who inadvertently have many chromedriver.exes on their machine \\(via different means\\) and don\u0027t know which one to attempt to upgrade in order to push through the v111:v112 snafu. A person might be in that pickle cos they\u0027ve clone many repos and run the project\u0027s choice of build which many have bought chromdriver.exe down many times to different locations.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0e6dd1f135776285e90d27e1539ae92c3d1b4b37",
      "old_mode": 33188,
      "old_path": "java/src/org/openqa/selenium/remote/service/DriverService.java",
      "new_id": "cd76b10af703ccf80dffe081638dbacc330ef6b3",
      "new_mode": 33188,
      "new_path": "java/src/org/openqa/selenium/remote/service/DriverService.java"
    }
  ]
}