scriptoriumadmin/litellm
1
0
Fork 0
mirror of https://github.com/BerriAI/litellm.git synced 2026-09-06 08:16:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 79

fix(tests): satisfy the tests-tree ruff config and correct a stale comment

Browse source 
Moving the resolver tests under tests/ brings them under ruff-tests.toml,
which the package-internal directory they came from was never linted by, so a
pre-existing pytest.raises pattern now needs to be a raw string (RUF043).

Also corrects the comment on proxy_cli's RuntimeError handler: both resolvers
raise on permission failures, not just v2.
This commit is contained in:
Yuneng Jiang 2026-08-28 01:38:27 -07:00
parent 7b36bfb967
commit fbd1339993
No known key found for this signature in database
2 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
litellm/proxy/proxy_cli.py
View file

@ -1323,10 +1323,10 @@ def run_server(
use_v2_resolver=use_v2_migration_resolver,
)
except RuntimeError as e:
# Raised on unrecoverable migration errors: the v2
# resolver's non-idempotent failures and permission
# issues, and any `prisma db push` against a
# partitioned LiteLLM_SpendLogs.
# Raised on unrecoverable migration errors: permission
# failures from either resolver, the v2 resolver's
# non-idempotent failures, and any `prisma db push`
# against a partitioned LiteLLM_SpendLogs.
print(
f"\033[1;31mLiteLLM Proxy: Database migration cannot proceed. {e}\033[0m",
file=sys.stderr,

2
tests/litellm-proxy-extras/test_setup_database_fail_fast.py
View file

@ -219,7 +219,7 @@ def test_v2_resolve_specific_migration_failure_raises_runtime_error(
)
with patch("subprocess.run", side_effect=_fake_migrate_deploy_failure(1, stderr)):
with pytest.raises(
RuntimeError, match="Failed to mark migration .* as applied"
RuntimeError, match=r"Failed to mark migration .* as applied"
):
ProxyExtrasDBManager.setup_database(use_migrate=True, use_v2_resolver=True)