)]}'
{"ironic/common/exception.py":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"f097ff58d1aba7dc7acaf94d601d1e3cbc5b11cf","unresolved":false,"context_lines":[{"line_number":606,"context_line":""},{"line_number":607,"context_line":""},{"line_number":608,"context_line":"class CIMCException(IronicException):"},{"line_number":609,"context_line":"    _msg_fmt \u003d _(\"Cisco IMC exception occurred for node %(node)s: %(error)s.\")"}],"source_content_type":"text/x-python","patch_set":1,"id":"7a2fa921_9a74ad36","line":609,"updated":"2015-10-08 01:57:32.000000000","message":"Are you sure we should do this? I\u0027d rather the message not have an ending \u0027.\u0027, than for it to have two \u0027..\u0027 if the error string (or reason string) has an ending \u0027.\u0027.\n\nI don\u0027t mind putting the \u0027.\u0027 at the end of the other ones, but if we put periods after the ones that end with error strings or whatever, we should check/verify that those strings don\u0027t have periods.","commit_id":"c1ad336259f45f3c751bd67c123d274e6a612248"}]}