)]}'
{
  "commit": "6b5d9a99432aabd77d5ce155f17d24ae3556c27c",
  "tree": "bec0e30d2519761a461808be4aa6d5197aae2354",
  "parents": [
    "a98e4e0e8077e75ed0d92a24dce6de0a92b9e037"
  ],
  "author": {
    "name": "Nikhil Namjoshi",
    "email": "nikhilnamjoshi@google.com",
    "time": "Tue Nov 21 21:41:30 2023 +0000"
  },
  "committer": {
    "name": "Nikhil Namjoshi",
    "email": "nikhilnamjoshi@google.com",
    "time": "Tue Nov 21 22:35:22 2023 +0000"
  },
  "message": "Update the MCTP socket timeout\n\nOn the miniBMC side when the IOC is being reset, the IOC\nconfig page read can take longer.  Currently the total timeout\nfor the config page read is set to 6 seconds. This config page\nread happens every time miniBMC receives redfish requests for\nSATA drive resources. The redfish response timeout on the BMC\nis set to 1 second. So in any case, if IOC goes of reset, the\nconfig page read can easily take more than 2-3 seconds and\ntherefore BMC can timeout. Eventually miniBMC and BMC\ncommunication can go out of sync.\n\nThis can happen when miniBMC is receiving SATA drive resource requests\nwhile Host is booting up. During host bootup IOC resets 3 times.\n\nSo update the BMC MCTP socket timeout to a safe value.\n\nTested:\nRan repeated redfish queries for SATA drive resources for\nover 8 hours on a machine where the Host is bootlooping and on every\nboot it is resetting IOC 3 times. No issue of miniBMC and BMC going\nout of sync is observed.\n\nGoogle-Bug-Id: 300946789\nGoogle-Bug-Id: 310061372\nGoogle-Bug-Id: 308729272\nChange-Id: Ie2913e8f3c9e13736b3b593b581334b0643cf8b1\nSigned-off-by: Nikhil Namjoshi \u003cnikhilnamjoshi@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "12726435bd6054a49cc7b22a160d62aa071961c6",
      "old_mode": 33188,
      "old_path": "rded.cpp",
      "new_id": "75b78d36ae000246bd8d9bf8e59e62332eda3668",
      "new_mode": 33188,
      "new_path": "rded.cpp"
    }
  ]
}