)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"8c93930e34854548c8c45c8ea86e52b54442a718","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"00a38957_e264bd37","updated":"2024-05-10 11:09:43.000000000","message":"clean cherry-pick and master patch has landed.","commit_id":"994358d582e8e8d98a3e8e91ceb77ae354c1e275"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"02a559c4e783a330e679181f2588ce2c422020ce","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6705733a_7df37838","in_reply_to":"00a38957_e264bd37","updated":"2024-05-10 13:57:21.000000000","message":"Clean cherry pick, indeed. This is a bug fix, so should be OK to backport. I was a bit hesitant when i read the bug report, as some user might be building on this faulty behaviour... but anyway, that means they end up in a broken state, so best is to avoid such issue. and the \"workaround\" is explained in multiple places with this patch.\n\nSo I tend to accept this as a backport... Given that the patch was proposed by Sean, a fellow stable core, and Gibi is also a stable core, I +2+W this.","commit_id":"994358d582e8e8d98a3e8e91ceb77ae354c1e275"}]}