)]}'
{"tempest_lib/common/rest_client.py":[{"author":{"_account_id":11662,"name":"Paul Glass","email":"paul.glass@rackspace.com","username":"pglass"},"change_message_id":"7950e562d1c6660be4eb602b0cf366aa03a1b91e","unresolved":false,"context_lines":[{"line_number":677,"context_line":""},{"line_number":678,"context_line":"        if resp.status \u003d\u003d 404:"},{"line_number":679,"context_line":"            if parse_resp:"},{"line_number":680,"context_line":"                resp_body \u003d self._parse_resp(resp_body)"},{"line_number":681,"context_line":"            raise exceptions.NotFound(resp_body)"},{"line_number":682,"context_line":""},{"line_number":683,"context_line":"        if resp.status \u003d\u003d 400:"}],"source_content_type":"text/x-python","patch_set":2,"id":"7a016987_6730139f","line":680,"updated":"2015-05-18 15:23:22.000000000","message":"There seem to be tests with combos of \u0027application/json\u0027 and response bodies that are empty (or just invalid json in general), which give us failures here.\n\nIdeally, self._parse_resp should catch and suppress the ValueError on invalid json... But there may be users that rely on that ValueError, so you might have to parse the json here locally.","commit_id":"a3c6a781dcf190e0e675fe06a5e50ef501b36149"},{"author":{"_account_id":395,"name":"Endre Karlson","email":"endre.karlson@gmail.com","username":"endre-karlson"},"change_message_id":"c2837d3ec9a5c9c665bcc5f5cddc18d68c6d72c0","unresolved":false,"context_lines":[{"line_number":677,"context_line":""},{"line_number":678,"context_line":"        if resp.status \u003d\u003d 404:"},{"line_number":679,"context_line":"            if parse_resp:"},{"line_number":680,"context_line":"                resp_body \u003d self._parse_resp(resp_body)"},{"line_number":681,"context_line":"            raise exceptions.NotFound(resp_body)"},{"line_number":682,"context_line":""},{"line_number":683,"context_line":"        if resp.status \u003d\u003d 400:"}],"source_content_type":"text/x-python","patch_set":2,"id":"7a016987_b6b98d17","line":680,"in_reply_to":"7a016987_6730139f","updated":"2015-05-19 13:00:04.000000000","message":"Not sure how you mean that I should be doing this part?","commit_id":"a3c6a781dcf190e0e675fe06a5e50ef501b36149"}],"tempest_lib/exceptions.py":[{"author":{"_account_id":5196,"name":"Matthew Treinish","email":"mtreinish@kortar.org","username":"treinish"},"change_message_id":"450bf9c06c4d21b2bf3285272a4bfa301847b345","unresolved":false,"context_lines":[{"line_number":49,"context_line":"                          testtools.TestCase.failureException):"},{"line_number":50,"context_line":"    def __init__(self, resp_body, *args, **kwargs):"},{"line_number":51,"context_line":"        self.resp_body \u003d resp_body"},{"line_number":52,"context_line":"        message \u003d kwargs.get(\"message\", resp_body)"},{"line_number":53,"context_line":"        super(RestClientException, self).__init__(message, *args, **kwargs)"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":""}],"source_content_type":"text/x-python","patch_set":7,"id":"5afe65bd_e9e4310e","line":52,"updated":"2015-06-02 09:55:17.000000000","message":"So the only thing I think is missing here is a docstring explaining the use of the message kwarg. This is new behavior to pass in a message and a body so having an explanation about it would be good.\n\nBut, since there wasn\u0027t a real docstring here before I think that would be fine as a follow-on patch.","commit_id":"3d446a54ec012dfe464cc467b3706e5b5d0d099b"}]}