)]}'
{
  "commit": "7497bd23151bce9f4605c7b23627dd1d04cdaa49",
  "tree": "341dba341403a04738814e05c8b8e378c946ea31",
  "parents": [
    "0ef492fd9fcd31396b42bbe96f92ae2e13848023"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Jul 11 19:59:56 2017 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Jul 11 19:59:56 2017 +0300"
  },
  "message": "Core: disabled SO_REUSEPORT when testing config (ticket #1300).\n\nWhen closing a socket with SO_REUSEPORT, Linux drops all connections waiting\nin this socket\u0027s listen queue.  Previously, it was believed to only result\nin connection resets when reconfiguring nginx to use smaller number of worker\nprocesses.  It also results in connection resets during configuration\ntesting though.\n\nWorkaround is to avoid using SO_REUSEPORT when testing configuration.  It\nshould prevent listening sockets from being created if a conflicting socket\nalready exists, while still preserving detection of other possible errors.\nIt should also cover UDP sockets.\n\nThe only downside of this approach seems to be that a configuration testing\nwon\u0027t be able to properly report the case when nginx was compiled with\nSO_REUSEPORT, but the kernel is not able to set it.  Such errors will be\nreported on a real start instead.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2af287614140bf42e9f58442cdd615895403f976",
      "old_mode": 33188,
      "old_path": "src/core/ngx_connection.c",
      "new_id": "046098f1aee90baf1091c488373e9cefc6065e70",
      "new_mode": 33188,
      "new_path": "src/core/ngx_connection.c"
    }
  ]
}