)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"9b5818f3bab731088b0a9e9cc4ad46bdf3d31637","unresolved":true,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This is part of our effort to move away from FunctionalTest. The"},{"line_number":10,"context_line":"FunctionalInitWrapper class is only used in"},{"line_number":11,"context_line":"glance/tests/functional/db/test_sqlalchemy.py."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Change-Id: Ia8e8d51fbea5b0e0edb3863a235ddc52af9a4d65"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"d49bb5ad_9012e40e","line":11,"updated":"2025-01-09 15:16:59.000000000","message":"...but does it even need it? I don\u0027t see api calls (i.e. `self.api_get(...`) in there? Perhaps it just uses it for the `setup_database()` function? If so, that\u0027s pretty small and it would probably be best to break the link instead of adding the `SynchronousAPIBase` to it no?","commit_id":"758cc76c26124d71c71ab357c7273ce1af7c2333"},{"author":{"_account_id":8122,"name":"Cyril Roelandt","email":"cyril@redhat.com","username":"cyril.roelandt.enovance"},"change_message_id":"7fa3cec68cc52d6131a63560b2ff444c47ba6cfa","unresolved":true,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This is part of our effort to move away from FunctionalTest. The"},{"line_number":10,"context_line":"FunctionalInitWrapper class is only used in"},{"line_number":11,"context_line":"glance/tests/functional/db/test_sqlalchemy.py."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Change-Id: Ia8e8d51fbea5b0e0edb3863a235ddc52af9a4d65"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"338f87b9_bd152a1a","line":11,"in_reply_to":"d49bb5ad_9012e40e","updated":"2025-02-05 19:36:49.000000000","message":"OK I looked into it and indeed I don\u0027t think FunctionalInitWrapper is still needed. See my next patchset :)","commit_id":"758cc76c26124d71c71ab357c7273ce1af7c2333"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"64692fa95bb36d16a0b777227ddb20c402f333b3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"470bc1e1_38949de9","updated":"2025-01-20 10:49:14.000000000","message":"This series of patch seems related to eventlet, do you mind if we attach it the the eventlet-removal topic?","commit_id":"758cc76c26124d71c71ab357c7273ce1af7c2333"},{"author":{"_account_id":8122,"name":"Cyril Roelandt","email":"cyril@redhat.com","username":"cyril.roelandt.enovance"},"change_message_id":"416da066854b9150bdcba364bc263bf7eced3bb8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7c36bfde_01722b93","in_reply_to":"470bc1e1_38949de9","updated":"2025-01-20 14:41:24.000000000","message":"Can we not keep eventlet-removal-functional-tests? This way we can still list eventlet-related patches by using \"prefixtopic:eventlet-removal\" in Gerrit, but we can also point out to specific \"sub topics\" using the full name.\n\nIf that\u0027s an issue, go ahead and change the topic as you see fit :)","commit_id":"758cc76c26124d71c71ab357c7273ce1af7c2333"}]}