)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":10058,"name":"Erlon R. Cruz","email":"erlon.rodrigues.cruz@canonical.com","username":"sombrafam"},"change_message_id":"f20cc0b05a63a7039554a8b1d3a319c7d13c5e3c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"22dfa464_f6af3a5d","updated":"2026-06-24 13:06:52.000000000","message":"Hey Claudiu, thanks for the fix. Can you give any context on why this should be changed?","commit_id":"c428901a4d79980923c71eaa020c357549048128"},{"author":{"_account_id":8213,"name":"Claudiu Belu","email":"cbelu@cloudbasesolutions.com","username":"claudiub"},"change_message_id":"495d02824c762fdec1e0a1026e9e0e95b7ecd24b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"59192d04_90bcc706","in_reply_to":"22dfa464_f6af3a5d","updated":"2026-06-24 14:37:17.000000000","message":"Hello. Check the commit below this: https://review.opendev.org/c/openstack/cinder/+/994152/8\n\nBasically, it helps enforce test correctness by enforcing autospecs on mocked objects / methods / functions. If a mock is being used, and some mocked method is being called, if it called with a wrong argument it should naturally raise TypeError, rather than silently pass (false positive test).\n\nFrom what I\u0027ve seen in the commit below, there are some gaps in the cinder code caught by autospecs.","commit_id":"c428901a4d79980923c71eaa020c357549048128"}]}