@pytest.fixture on an async fixture ignores loop_scope, so mysql_repo ran on the per-function loop while mysql_test_db_url's engine was bound to the module loop — triggering 'Future attached to a different loop'.
@pytest.fixture on an async fixture ignores loop_scope, so mysql_repo ran on the per-function loop while mysql_test_db_url's engine was bound to the module loop — triggering 'Future attached to a different loop'.