)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"0b8b159a2b474eeb98d4b70ea6748cbf99d36fb4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"0201f091_647fa30b","updated":"2025-06-17 09:10:03.000000000","message":"LGTM","commit_id":"0e4531adc7a1d5c631a83384b32f0418f225c788"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"c0019b33d8d535c39ae8173118eb1c1c7c72487e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"63ba6430_5ccb67a2","updated":"2025-06-22 20:56:59.000000000","message":"Ok, so I figured out the issue.\n\nWhen instantiating the LoopingCall class with this change, you need to specify the function argument with a keyword, you can\u0027t rely on the position. So something like:\n\nFixedIntervalLoopingCall(\n-                self._report_state)\n+                f\u003dself._report_state)\n\nThat works (and keeps the pep8 warning silenced).\n\nTo me, not using the keyword is a bug in our code, but I\u0027ll let you decide if you still want the change.","commit_id":"0e4531adc7a1d5c631a83384b32f0418f225c788"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"8f9e7103457ae5335498b95ac34543c110a6d048","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ceab72d0_ff23303c","updated":"2025-06-22 20:19:50.000000000","message":"This actually caused an issue in the neutron change, think we should not merge it.","commit_id":"0e4531adc7a1d5c631a83384b32f0418f225c788"},{"author":{"_account_id":13861,"name":"yatin","email":"ykarel@redhat.com","username":"yatinkarel"},"change_message_id":"eb2e1d338298246c7454fa8600b9bfcaa14b11fc","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"329e9fb9_8bdebbed","updated":"2025-07-07 14:40:09.000000000","message":"This had triggered some issues in job https://zuul.openstack.org/builds?job_name\u003dneutron-ovn-tempest-full-multinode-ovs-master\u0026project\u003dopenstack/neutron","commit_id":"0e4531adc7a1d5c631a83384b32f0418f225c788"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"cde7f09591f0434f139f3f1c3e7df3bcadb65879","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"3af1d1f0_5193a894","updated":"2025-07-07 15:25:57.000000000","message":"We should probably revert this for now, seeing a lot of usage with non keyword arguments.\n\nhttps://codesearch.opendev.org/?q\u003dFixedIntervalLoopingCall\u0026i\u003dnope\u0026literal\u003dnope\u0026files\u003d\u0026excludeFiles\u003d\u0026repos\u003d","commit_id":"0e4531adc7a1d5c631a83384b32f0418f225c788"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"cd86d0e0db604259ed4463bae433691eed7a5998","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e285f1b8_b898da88","in_reply_to":"3af1d1f0_5193a894","updated":"2025-07-07 16:50:49.000000000","message":"Yeah, I maybe should have seen that coming based on my patch to change the neutron callers. I will create the revert.\n\nHmm, I can\u0027t create a revert automatically since this didn\u0027t have a SOB line originally:\n\nCould not perform action: not Signed-off-by author/committer/uploader in message footer\n\nWill have to do manually for now.","commit_id":"0e4531adc7a1d5c631a83384b32f0418f225c788"}]}