)]}'
{
  "commit": "82854d0d78a24fcbcf16dbf486cf60421f73096b",
  "tree": "a89a94d69a219e5b0f25f1ea2d5c906185485f9e",
  "parents": [
    "a9e3c65d22ad68b994ad7046b243ae459b242ffa"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Thu Sep 01 15:10:41 2011 +0000"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Thu Sep 01 15:10:41 2011 +0000"
  },
  "message": "Proper setting of read-\u003eeof in pipe code.\n\nSetting read-\u003eeof to 0 seems to be just a typo.  It appeared in\nnginx-0.0.1-2003-10-28-18:45:41 import (r164), while identical code in\nngx_recv.c introduced in the same import do actually set read-\u003eeof to 1.\n\nFailure to set read-\u003eeof to 1 results in EOF not being generally detectable\nfrom connection flags.  On the other hand, kqueue won\u0027t report any read\nevents on such a connection since we use EV_CLEAR.  This resulted in read\ntimeouts if such connection was cached and used for another request.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d01b204463fcf54f6a3319b99c4b1ed4fa3c9bc0",
      "old_mode": 33188,
      "old_path": "src/event/ngx_event_pipe.c",
      "new_id": "53d738f0a81eaa7de4a5c24b2b02aaefc331ead3",
      "new_mode": 33188,
      "new_path": "src/event/ngx_event_pipe.c"
    }
  ]
}