)]}'
{
  "commit": "80f61a9979079ed16b9eff50ba65ad8bf1b15fb6",
  "tree": "886c30e2570dc6f5117c7dbf353de023524b0309",
  "parents": [
    "7e73eb740f3c52a5b7c0ae9c2cd33b486d885552"
  ],
  "author": {
    "name": "Jonathan Hart",
    "email": "jono@onlab.us",
    "time": "Tue Apr 19 22:13:49 2016 -0700"
  },
  "committer": {
    "name": "Donald Sharp",
    "email": "sharpd@cumulusnetworks.com",
    "time": "Fri Apr 22 08:37:25 2016 -0400"
  },
  "message": "pimd: Fix hang when doing nexthop lookup from zebra\n\nI was running in to a bug when pimd would hang in some cases when\nit had to do a nexthop lookup from zebra, such as when a PIM JOIN\nwas received. This issue could be easily reproduced by running\n\u0027show ip rib \u003cip\u003e\u0027 from the pimd vty which forces a nexthop lookup.\n\nThe issue is in zclient_read_nexthop, the zclient_read_header function\nreads the message content into the stream, but then after that the\nzclient_read_nexthop function tries to read the message content again\nfrom the socket, but there are no bytes so it hangs waiting for input.\nThe solution is to not try to read the message content the second time.\nAcked-by: Jafar Al-Gharaibeh\nTested-by: NetDEF CI System \u003ccisystem@netdef.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b5b219ea357ce9965390974392cd2b55a7e5173c",
      "old_mode": 33188,
      "old_path": "pimd/pim_zlookup.c",
      "new_id": "770fbf74215fc55b58aa10a767b5bbce06dd76fd",
      "new_mode": 33188,
      "new_path": "pimd/pim_zlookup.c"
    }
  ]
}