You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Thank you for creating this framework. I'm currently using ariadne to manage a graphql lambda.
For every execution I get a stack trace:
ERROR:mangum.lifespan:Exception in 'lifespan' protocol.
Traceback (most recent call last):
File "/Users/lilja/Library/Caches/pypoetry/virtualenvs/backend-dmp__8h8-py3.8/lib/python3.8/site-packages/mangum/protocols/lifespan.py", line 93, in run
await self.app({"type": "lifespan"}, self.receive, self.send)
File "/Users/lilja/Library/Caches/pypoetry/virtualenvs/backend-dmp__8h8-py3.8/lib/python3.8/site-packages/ariadne/asgi.py", line 94, in __call__
raise ValueError("Unknown scope type: %r" % (scope["type"],))
ValueError: Unknown scope type: 'lifespan'
However, the lambda/mangum executes as the rest of the code as usual and I have correct graphql output.
I'm not up-to-speed with asgi stuff and don't really know what this means, is there a way to silence this error? Should I create a github issue with the other framework in question?
This is due to the default lifespan behavior of Mangum. You can set the Mangum(graphql_app, lifespan="off") setting to explicitly disable lifespan to avoid this, though Mangum should probably be catching exceptions generally in these cases instead of raising.
Hi! Thank you for creating this framework. I'm currently using ariadne to manage a graphql lambda.
For every execution I get a stack trace:
However, the lambda/mangum executes as the rest of the code as usual and I have correct graphql output.
I'm not up-to-speed with asgi stuff and don't really know what this means, is there a way to silence this error? Should I create a github issue with the other framework in question?
raised error in question: https://github.com/mirumee/ariadne/blob/master/ariadne/asgi.py#L113
How I use mangum
The text was updated successfully, but these errors were encountered: