)]}'
{
  "commit": "3f0df23b0b9eee22e76a24b396a33fbd036d6904",
  "tree": "bd2cdf0910e1eb262cbb6afe5aef1712ad1036f6",
  "parents": [
    "50a48f8e3cf2392fcda258d350ae20394c83c0f6"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Wed Jul 31 17:29:00 2019 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Wed Jul 31 17:29:00 2019 +0300"
  },
  "message": "Gzip: fixed \"zero size buf\" alerts after ac5a741d39cf.\n\nAfter ac5a741d39cf it is now possible that after zstream.avail_out\nreaches 0 and we allocate additional buffer, there will be no more data\nto put into this buffer, triggering \"zero size buf\" alert.  Fix is to\nreset b-\u003etemporary flag in this case.\n\nAdditionally, an optimization added to avoid allocating additional buffer\nin this case, by checking if last deflate() call returned Z_STREAM_END.\nNote that checking for Z_STREAM_END by itself is not enough to fix alerts,\nas deflate() can return Z_STREAM_END without producing any output if the\nbuffer is smaller than gzip trailer.\n\nReported by Witold Filipczyk,\nhttp://mailman.nginx.org/pipermail/nginx-devel/2019-July/012469.html.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "48f3dd7c7cc84591169748333977e52c2cbd5d59",
      "old_mode": 33188,
      "old_path": "src/http/modules/ngx_http_gzip_filter_module.c",
      "new_id": "c75169c537492342d19feeb6c821044a0cebd5f0",
      "new_mode": 33188,
      "new_path": "src/http/modules/ngx_http_gzip_filter_module.c"
    }
  ]
}