Litestar
"Task was destroyed but it is pending!" #4119
Replies: 1 comment 2 replies
-
|
This is super hard to tell without knowing your app in detail. Only guess I could make is that, since it's the main The scenario you've described should not happen, as your ASGI server should shutdown the app gracefully, that is:
What ASGI server are you using? |
Beta Was this translation helpful? Give feedback.
-
|
I am using NGINX Unit I have no The pods also have a |
Beta Was this translation helpful? Give feedback.
-
|
NGINX unit is known to have quirks when it comes to its ASGI implementation. It's possible that something's wonky there. You could try using some other ASGI server and see if it happens there as well to rule out an issue with unit. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am getting this error from a litestar app (more specifically, I am seeing this in the log file; presumable from stdout/stderr)
I was thinking this could be due to the app pod (kubernetes) getting shutdown (SIGTERM) as part of scaling down, while the app is still handling requests, but I am not sure. Does that make sense? And is that "as intended" or should I do something about this?
The app is using some middleware (customized prometheus middleware, this middleware) and also a
before_request. I can give more details as needed.I am seeing this for both litestar 2.9.0 and 2.15.2. For 2.9.0, the line in litestar/app.py is 591 instead (same code).
Beta Was this translation helpful? Give feedback.
All reactions