)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"855dcca2dcfabb39ee549d94855892090af8b9af","unresolved":false,"context_lines":[{"line_number":10,"context_line":"is in a local section, but the value in direct_maps is null."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Now I have set insecure_debug to \u0027True\u0027, and it shows like \u0027..."},{"line_number":13,"context_line":"(e.g. {0} in a local section).\u0027. But it still shows \u0027An unexpected...\u0027."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Change-Id: If6263229b153828ffa07ee3ad6004f3db7cdfd98"},{"line_number":16,"context_line":"Closes-Bug: #1695131"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"df140735_8d07d518","line":13,"updated":"2017-06-05 20:37:40.000000000","message":"i agree with Colleen\u0027s statement here. I think the change is fine but it was hard to figure out exactly what the issue was from the bug report for the commit message.\n\nThe commit message here could be something like:\n\n  Improve exception logging for DirectMappingError\n\n  Previously, when `keystone.conf [DEFAULT] insecure_debug` was set to False,\n  an error would returns details and specifics about how the mapping failed. When\n  enabling `keystone.conf [DEFAULT] insecure_debug`, the error was replaced with\n  a much more opaque message, which is counter-intuitive to the purpose of\n  `insecure_debug`. This change updates the debug attribute of the\n  DirectMappingError exception so that it provides useful information when\n  `insecure_debug` is enable.","commit_id":"78eb44266cfc3e5053b71c27df7b7030641dbf53"}]}