)]}'
{
  "commit": "a72ee9a88813b35dfde76f3043932532d5500de7",
  "tree": "a87b533b93432149ec7ddb972528ec482eec97e2",
  "parents": [
    "87da0df8c45e0f398aeeacb83ff2f8e8d5819e55"
  ],
  "author": {
    "name": "rajalakshmi-ganesan",
    "email": "rajalakshmi_ganesan@persistent.co.in",
    "time": "Wed Dec 26 15:03:27 2012 +0530"
  },
  "committer": {
    "name": "rajalakshmi-ganesan",
    "email": "rajalakshmi_ganesan@persistent.co.in",
    "time": "Thu Dec 27 17:33:18 2012 +0530"
  },
  "message": "Logic in rest_client incorrect \"resp.status\u003d413\"\n\nrest_client is NOT redriving rate limited calls for the second time.\nWhen 413 error code is encountered for a request, it checks for the\nword \"overLimit\" and \"limit\" in resp_body and resp_body[message]\nrespectively so as to confirm if it is a absolute-limited call.\nIf absolute limited call is confirmed, OverLimit exception is raised\nwithout any re-try for request.\nThen comes the check for depth \u003c MAX_RECURSION_DEPTH, if it is true,\nre-drive towards request call occurs.\nBut, the word \"limit\" also appears in the message of ratelimited call.\nHence it is incorrect to raise OverLimit exception without re-try when\nword \"limit\" is present in the message of response.\nThus changed the word to \"exceeded\" instead of \"limit\".\nFixes: bug #1093573\n\nChange-Id: Iadd94c18668096d7e4795631337230ec36e9c4b9\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "884d147a0590136f7bfb0f97d7a0505074048463",
      "old_mode": 33188,
      "old_path": "tempest/common/rest_client.py",
      "new_id": "c96fc4f73533e3926aaa4d88d2b68620769ceca6",
      "new_mode": 33188,
      "new_path": "tempest/common/rest_client.py"
    }
  ]
}