Skip to content
This repository has been archived by the owner on Sep 27, 2019. It is now read-only.

Incompatibility between sentry-asgi v0.2.0 and responder v1.3.1 #13

Closed
sboisson opened this issue May 23, 2019 · 2 comments
Closed

Incompatibility between sentry-asgi v0.2.0 and responder v1.3.1 #13

sboisson opened this issue May 23, 2019 · 2 comments

Comments

@sboisson
Copy link

Adding the middleware to Responder cause this errror at request handling:

TypeError: __call__() missing 2 required positional arguments: 'receive' and 'send'
  File "uvicorn/protocols/http/httptools_impl.py", line 368, in run_asgi
    result = await app(self.scope, self.receive, self.send)
  File "uvicorn/middleware/debug.py", line 96, in __call__
    raise exc from None
  File "uvicorn/middleware/debug.py", line 78, in __call__
    await self.app(scope, receive, inner_send)
  File "uvicorn/middleware/asgi2.py", line 6, in __call__
    instance = self.app(scope)
  File "responder/api.py", line 276, in __call__
    return self.app(scope)

@sboisson
Copy link
Author

sboisson commented May 23, 2019

The workaround is to pin sentry-asgi to verson 0.1.5

@tomchristie
Copy link
Member

Yup. The latest versions of Sentry-ASGI uses the ASGI 3 protocol.
Pin to 0.1.x if you're working with a library that doesn't yet support that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants