)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"c4087621e2eb585f44d82496398531cb467b0d9e","unresolved":false,"context_lines":[{"line_number":9,"context_line":"As response from the deployment team at Fujitsu,"},{"line_number":10,"context_line":"at step 3. After maintenance window, if sending SIGHUP"},{"line_number":11,"context_line":"to the console proxy services will cause them to stop."},{"line_number":12,"context_line":"This patch adds a note for that."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Change-Id: I700e7696f59c58ed8d4900b7457f0251ba836d29"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_6cdf34d7","line":12,"updated":"2018-10-23 00:21:07.000000000","message":"Sorry, can you provide more detail about what happened when you sent SIGHUP to the console proxy service? Which proxy service did you use, noVNC?\n\nBecause if the service really stopped because of the signal, it sounds like a bug that needs to be fixed and not something to clarify in documentation. The SIGHUP signal should not cause the console proxy service to stop.","commit_id":"1b3be792b960b3ff551e47d8d43f19c06a57272d"}]}