Giovanni Barillari
Giovanni Barillari
Any news on this?
FYI Granian 1.0 added support for lifespan state, thus the `lifespan` method is now supported instead of relying on deprecated lifespan events.
Sounds reasonable to me, I'll be happy to accept a PR for this. The only thing I would change in your plan is to name the extra `reload` instead of...
This is something that will require some analysis, but only after #25 is done
@cyb3rs3ntry `ASGIFlowError` usually means Granian received an unexpected event from the framework/application. [Looking at channels source code](https://github.com/django/channels/blob/4.0.0/channels/utils.py#L52-L59) it seems the issue is related with closing the connection. I never used...
> any other information I can do to help here? Should I create a basic app in docker? Also I just noticed it happens every ~65 seconds with no requests...
@cyb3rs3ntry so, I'm going to merge #193 and release a new patch version. Unfortunately, I'm not sure this is gonna solve everything regarding `channels`, as from my local tests there's...
> I am also seeing the `ASGI Lifespan errored, continuing without Lifespan support` warning with Granian 1.02 & Django 5.0.2. Although, I can say I am **not** using Channels. Happy...
@cyb3rs3ntry would you be able to test this with 1.1.0 and report what's the status?
Closing this for inactivity, feel free to open a new issue once tested with latest Granian version