)]}'
{
  "commit": "c42c70f478b4ec1a153b77129fd3e905f5b74314",
  "tree": "126224fc10f2d4dcfa4f5c42917d644b2a40ea88",
  "parents": [
    "d7c2673d3ffb5c8c7c994a3ee385997237ed0d99"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Thu Sep 15 18:12:58 2011 +0000"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Thu Sep 15 18:12:58 2011 +0000"
  },
  "message": "Workaround for cpu hog on errors with cached connections.\n\nJust doing another connect isn\u0027t safe as peer.get() may expect peer.tries\nto be strictly positive (this is the case e.g. with round robin with multiple\nupstream servers).  Increment peer.tries to at least avoid cpu hog in\nround robin balancer (with the patch alert will be seen instead).\n\nThis is not enough to fully address the problem though, hence TODO.  We\nshould be able to inform balancer that the error wasn\u0027t considered fatal\nand it may make sense to retry the same peer.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f698833af7a3d14054fa5c0056a544e7b0cf7743",
      "old_mode": 33188,
      "old_path": "src/http/ngx_http_upstream.c",
      "new_id": "3913e13891745d6aed26c219b875c9d60e4885dd",
      "new_mode": 33188,
      "new_path": "src/http/ngx_http_upstream.c"
    }
  ]
}