)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1179,"name":"Clay Gerrard","email":"clay.gerrard@gmail.com","username":"clay-gerrard"},"change_message_id":"a383850144f15968aeedaef37acd8f471cf1cfbe","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a60ac271_e9a6e78e","updated":"2022-12-18 23:59:14.000000000","message":"do we get to turn this back on after we backport our http parsing fix?","commit_id":"c8662c6f0ef8b9f321234add40263d0947623c09"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"59c74eafe7a116d3574be2605acb71b4dee89bf2","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d19ced55_fad65916","in_reply_to":"a60ac271_e9a6e78e","updated":"2022-12-19 20:30:56.000000000","message":"Would have to wait until we cut a stable release post-backport, but yeah, there exists a path wherein we get this turned back on. Historically, we don\u0027t have a great track record of actually doing it for stable branches, though -- master is front of mind, and stable tends to be an afterthought. Master is in basically all ways better, we do our best to ensure you can always upgrade to it, so stable tags tend to be infrequent. As a result, there\u0027s often some new form of breakage that would prevent us from re-enabling.\n\nIf we wanted to be serious about it, we might want to have a known-failures file for things like this -- but I think it\u0027d be hard to get the scoping right. It\u0027s always some dependency that shifts and causes us headaches, so it\u0027s weird to list known-failures by Swift release; OTOH, there *should be* a known Swift release that contains a workaround to get it passing again.","commit_id":"c8662c6f0ef8b9f321234add40263d0947623c09"}]}