)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"2b0a55b05710788a7804a57fe1feeaedb0d6ad97","unresolved":false,"context_lines":[{"line_number":10,"context_line":"API could hang indefinitely if network or other environmental related"},{"line_number":11,"context_line":"issues were encountered."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"When encountered during a call to update_available_resource this can"},{"line_number":14,"context_line":"result in the local n-cpu service reporting as UP while never being able"},{"line_number":15,"context_line":"to break out of a subsequent RPC timeout loop as documented in bug"},{"line_number":16,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"7faddb67_72abd674","line":13,"updated":"2019-07-24 15:26:35.000000000","message":"I\u0027m a bit hesitant to backport this, at least all the way to queens, and so soon after it merged on master. Did anyone recreate the problem reported in the bug and verify this resolves it? I didn\u0027t see a comment from the bug reporter that this fixed their problem. Maybe this is a no-brainer and I\u0027m just being paranoid.","commit_id":"a27ed51cb31912a5159f0cad804fdc447c6b0407"}]}
