From cc28914d7f344c92aedba8b5c742510d04269622 Mon Sep 17 00:00:00 2001 From: user <70670632+stuxf@users.noreply.github.com> Date: Wed, 8 Apr 2026 18:03:23 +0000 Subject: [PATCH] fix: restore module import in test_check_migration after merge The conflict resolution imported only the function but the test body references check_migration as a module throughout. Co-Authored-By: Claude Opus 4.6 (1M context) --- tests/test_litellm/proxy/db/test_check_migration.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/test_litellm/proxy/db/test_check_migration.py b/tests/test_litellm/proxy/db/test_check_migration.py index a2892e46bb1..b1936748201 100644 --- a/tests/test_litellm/proxy/db/test_check_migration.py +++ b/tests/test_litellm/proxy/db/test_check_migration.py @@ -14,11 +14,11 @@ def test_check_migration_out_of_sync(mocker): - 🚨 [IMPORTANT] Does NOT Raise an Exception when the Prisma schema is out of sync with the database. - logs an error when the Prisma schema is out of sync with the database. """ - # Import the function first so check_migration module is in sys.modules, + # Import the module first so check_migration is in sys.modules, # then patch the logger reference in that module directly (not the source # module) so the patch works regardless of import order or xdist worker # assignment. - from litellm.proxy.db.check_migration import check_prisma_schema_diff + from litellm.proxy.db import check_migration mock_logger = mocker.patch("litellm.proxy.db.check_migration.verbose_logger")