euri10

Should server shutdown after receiving "lifespan.shutdown.failed"?

5

### Discussed in https://github.com/encode/uvicorn/discussions/2298 Originally posted by **peterschutt** April 5, 2024 If the shutdown failure message isn't initiated by the app receiving a "lifespan.shutdown" from uvicorn, then the app continues...

ASGI not working properly, CFFI life cycle is wrong.

1

**Describe the bug** I can crash the server using the below app, it happens evertime I run the second wrk command, and the stacktrace is: ```bash ❯ python main_socketify.py ERROR:root:Uncaught...

Not able to run Litestar app with lifespan

1

**Describe the bug** lifespan crashes without any interesting info **To Reproduce** Steps to reproduce the behavior: run that simple app, it runs ok with lifespan=False and crashes with lifespan=True `ERROR...

## Description - ## Closes

### Description following this discussion https://discord.com/channels/919193495116337154/1256638718236823593 we could make the below mvce simpler and catch a `HTTPDisconnect` instead of forcing the user to use anyio `CancelledError` (see @provinzkraut answer here:...

fix #37 I dont know the workflow too well here, let me know if I'm missing something

hello, it would be amazing now 17 is live :) thanks in advance

Bug: using a custom jinja Environement seems to bypass a potential template callable

1

### Description if using a custom env like described in https://docs.litestar.dev/2/usage/templating.html#registering-a-custom-template-engine I cannot add template callables, the registration is bypassed ### URL to code causing the issue _No response_ ###...

fix: template callable is now correctly registered when using custom env

1

fix #3791 ## Description - ## Closes