)]}'
{
  "commit": "08917db9270e179b857cd2d7eb2d69538ae5b6cc",
  "tree": "77316ee5cb8867e642d45fc835612c1d828ed275",
  "parents": [
    "d62a5265d7f51bc17842b0c5e1ef895131f77982"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Thu Oct 21 18:38:38 2021 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Thu Oct 21 18:38:38 2021 +0300"
  },
  "message": "Removed CLOCK_MONOTONIC_COARSE support.\n\nWhile clock_gettime(CLOCK_MONOTONIC_COARSE) is faster than\nclock_gettime(CLOCK_MONOTONIC), the latter is fast enough on Linux for\npractical usage, and the difference is negligible compared to other costs\nat each event loop iteration.  On the other hand, CLOCK_MONOTONIC_COARSE\ncauses various issues with typical CONFIG_HZ\u003d250, notably very inaccurate\nlimit_rate handling in some edge cases (ticket #1678) and negative difference\nbetween $request_time and $upstream_response_time (ticket #1965).\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7964b008f72ec835397725a7b9e64f269bd1e9ef",
      "old_mode": 33188,
      "old_path": "src/core/ngx_times.c",
      "new_id": "16788c98cb2ed2a63ebfbdeea199b0d54d63435c",
      "new_mode": 33188,
      "new_path": "src/core/ngx_times.c"
    }
  ]
}