Railway deployment failed - no idea why

[agileben]

✔ Generated Prisma Client Python (v0.11.0) to ./../../prisma in 335ms

INFO: Started server process [1]

INFO: Waiting for application startup.

ERROR: Traceback (most recent call last):

File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 732, in lifespan

async with self.lifespan_context(app) as maybe_state:

File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 608, in aenter

await self._router.startup()

File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 709, in startup

await handler()

File "/usr/local/lib/python3.11/site-packages/litellm/proxy/proxy_server.py", line 2905, in startup_event

create_view_response = await prisma_client.check_view_exists()

                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/site-packages/backoff/_async.py", line 151, in retry

ret = await target(*args, **kwargs)

      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/site-packages/litellm/proxy/utils.py", line 995, in check_view_exists

if required_view not in ret[0]["view_names"]:

   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

TypeError: argument of type 'NoneType' is not iterable

ERROR: Application startup failed. Exiting.

[krrishdholakia]

Hey @agileben this issue is fixed here - #5723

I'm assuming this is a new db with no existing views. It relates to a recent change made (v1.44.28+) which moved the view creation logic out of the proxy startup.

[lackeyi]

Is there a workaround for this? I am trying to get an instance running in Azure, and it looks like this may be the issue I am running into as well.

[krrishdholakia]

It'll be out by eod. if it's urgent use v1.44.27

[lackeyi]

That is impressive turn around! Thanks for the quick response!

[lackeyi]

I have tried rolling back to 1.44.27 and also tried the new 1.46.1 this morning. I am still seeing this same issue.

[ishaan-jaff]

fixed here: #5740

we needed a check for if the ret value is None

[lackeyi]

I was able to get it to run on v1.44.17-stable as a temporary workaround.