)]}'
{
  "commit": "22d1696819f1ccde7696728ee6a2b5386836f6d6",
  "tree": "9ff52c65cbba9713149ba064151719d44f06e85a",
  "parents": [
    "306ed20daff4704168c7048c4c64c4ea9d46c153"
  ],
  "author": {
    "name": "Valentin Bartenev",
    "email": "vbart@nginx.com",
    "time": "Thu Jun 16 20:55:11 2016 +0300"
  },
  "committer": {
    "name": "Valentin Bartenev",
    "email": "vbart@nginx.com",
    "time": "Thu Jun 16 20:55:11 2016 +0300"
  },
  "message": "HTTP/2: fixed the \"http request count is zero\" alert.\n\nWhen the stream is terminated the HEADERS frame can still wait in the output\nqueue.  This frame can\u0027t be removed and must be sent to the client anyway,\nsince HTTP/2 uses stateful compression for headers.  So in order to postpone\nclosing and freeing memory of such stream the special close stream handler\nis set to the write event.  After the HEADERS frame is sent the write event\nis called and the stream will be finally closed.\n\nSome events like receiving a RST_STREAM can trigger the read handler of such\nstream in closing state and cause unexpected processing that can result in\nanother attempt to finalize the request.  To prevent it the read handler is\nnow set to ngx_http_empty_handler.\n\nThanks to Amazon.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "342c307ef375e7e4ce3b47953358973d95d4bbd4",
      "old_mode": 33188,
      "old_path": "src/http/v2/ngx_http_v2.c",
      "new_id": "19e5f3a0975fa2ae66a1c99948b21cefdc18275e",
      "new_mode": 33188,
      "new_path": "src/http/v2/ngx_http_v2.c"
    }
  ]
}