)]}'
{
  "commit": "e90f1244eeff573c9e42bffbeb8c02cb801e89ad",
  "tree": "a7f7debd059a6608c4731eaa842fac683ff7e3d5",
  "parents": [
    "26415027d188cd5671bf4e28988f830820745215"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Fri Mar 18 05:04:45 2016 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Fri Mar 18 05:04:45 2016 +0300"
  },
  "message": "Fixed timeouts with threaded sendfile() and subrequests.\n\nIf a write event happens after sendfile() but before we\u0027ve got the\nsendfile results in the main thread, this write event will be ignored.\nAnd if no more events will happen, the connection will hang.\n\nRemoving the events works in the simple cases, but not always, as\nin some cases events are added back by an unrelated code.  E.g.,\nthe upstream module adds write event in the ngx_http_upstream_init()\nto track client aborts.\n\nFix is to use wev-\u003ecomplete instead.  It is now set to 0 before\na sendfile() task is posted, and it is set to 1 once a write event\nhappens.  If on completion of the sendfile() task wev-\u003ecomplete is 1,\nwe know that an event happened while we were executing sendfile(), and\nthe socket is still ready for writing even if sendfile() did not sent\nall the data or returned EAGAIN.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d7f915de9cd5958dc20634a57e0cf0da863d4213",
      "old_mode": 33188,
      "old_path": "src/event/modules/ngx_epoll_module.c",
      "new_id": "081b0e55093aa9081a841dfd63e5fe4868604fc2",
      "new_mode": 33188,
      "new_path": "src/event/modules/ngx_epoll_module.c"
    },
    {
      "type": "modify",
      "old_id": "8d01e10d0770499d994492a28e6fa60896a5bfd1",
      "old_mode": 33188,
      "old_path": "src/os/unix/ngx_linux_sendfile_chain.c",
      "new_id": "50a9cea2ecac924454df362fcea4c4f07dc1864e",
      "new_mode": 33188,
      "new_path": "src/os/unix/ngx_linux_sendfile_chain.c"
    }
  ]
}
