)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":1,"name":"James E. Blair","email":"jim@acmegating.com","username":"corvus"},"change_message_id":"51e03c6b1548f51466df1d4e7ed295b94fd53c9a","unresolved":false,"context_lines":[{"line_number":36,"context_line":"  tasks:"},{"line_number":37,"context_line":"  - debug:"},{"line_number":38,"context_line":"      msg: blah"},{"line_number":39,"context_line":"    name: foo"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"which would have clued me in immediately."},{"line_number":42,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"9f560f44_efedce8b","line":39,"updated":"2020-07-31 20:41:33.000000000","message":"If you put in a very large playbook, would it output the entire playbook here?\n\nI intentionally did not want to be so spammy with these error messages.  We do quote some code when there\u0027s a Zuul config error because we can extract the relevant part, but that\u0027s not the case here, where the error is something that we don\u0027t understand.\n\nMaybe we could include +/- 5 raw lines.\n\nHowever, I think a better approach would be to rely on inline comments.  Both Gerrit and Github are able to leave line comments for Zuul config errors.  Maybe we can update ConfigItem errors to include file information so that they can leave file comments.","commit_id":"654cc2fb1b4fc5413858c5eb8b1116366e69340e"},{"author":{"_account_id":7118,"name":"Ian Wienand","email":"iwienand@redhat.com","username":"iwienand"},"change_message_id":"b1fb941565970dd756ff6a5ca3c20f3f625a2eaa","unresolved":false,"context_lines":[{"line_number":36,"context_line":"  tasks:"},{"line_number":37,"context_line":"  - debug:"},{"line_number":38,"context_line":"      msg: blah"},{"line_number":39,"context_line":"    name: foo"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"which would have clued me in immediately."},{"line_number":42,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"9f560f44_22068fcf","line":39,"in_reply_to":"9f560f44_efedce8b","updated":"2020-08-05 03:38:16.000000000","message":"I agree a better approach is to get inline comments, but it seems to me to a large refactor to get these values in context; I can\u0027t immediately see how to keep the association since this is all working on bits of config that has been parsed and is now a regular dict/list etc.\n\nThe latest revision takes the approach of trimming the lines as suggested, which might be a compromise position.","commit_id":"654cc2fb1b4fc5413858c5eb8b1116366e69340e"}]}