)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"063c325a04c07ba49585ddbcce901c95dd83e847","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f26a320c_d90d40b7","updated":"2024-04-09 16:14:04.000000000","message":"I\u0027m fine with disabling the test, I just wonder whether it is only the test that is broken or the actual proxy, too? Does it make sense to reconsider whether we should have it in place at all?","commit_id":"2641e8e6ac752010eb201008a3705b5db3766280"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"0f7659704a0439e6472bf2461821964293ac6af4","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8550ede7_b4c00487","in_reply_to":"f26a320c_d90d40b7","updated":"2024-04-10 14:46:15.000000000","message":"The proxy is \"broken\" too. The problem is that upstream changed their api significantly leaving us in a bad spot. However, the primary user of this proxy was tripleo and those jobs have largely been cleaned up so I don\u0027t think anyone outside of our testing has really noticed.\n\nI agree we can clean that up later as well. I was half hoping that someone might save it because it is a useful thing to have but it isn\u0027t something high on my priority list.","commit_id":"2641e8e6ac752010eb201008a3705b5db3766280"}]}