-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<lambda>() missing 1 required positional argument: 'environ' on elastic-apm==2.2.0 #232
Comments
The issue disappears when I remove environ from I guess this
|
Hey @bastbnl. Thanks for reporting this! I fear the problem here is with channels, or more precisely, our lack of test coverage for channels. Django's own Channels, on the other hand, provides The good news is that we don't do anything with the While this shows the dire need of setting up some tests for channels, this will probably take some time. If I pushed the proposed fix to a branch in my fork, could you give it a try to see if it indeed fixes the issue? |
Django Channels doesn't provide `environ` when calling signal handlers. As we don't need it anyway, we can simply accept any arguments. Fixes elastic#232
Yes, happy to give it a try! |
Awesome! You should be able to install it via
|
TL;DR: Looks good! The error is not there anymore, the application works and there are no new errors. Just installed it with just 3 attempts
|
Awesome! I'll merge and push a release, will take about half an hour to an hour until 2.2.1 is on PyPI. BTW, we added instrumentation of elasticsearch-py in 2.2, would be great to hear any feedback you might have on it (once you can actually run a working version :D ) |
2.2.1 is now on PyPI :) https://pypi.org/project/elastic-apm/2.2.1/ Thanks again for reporting this @bastbnl! |
... and on my development server. All is looking well. Thx a lot for your swift action @beniwohli btw happy to serve as a human testrunner to discover issues with the stack I'm using. I can try to contribute to automated testing using channels. |
Just updated elasticapm to version 2.2.0 and ran into this issue:
Some of the python packages I'm using on Python 3.5.3:
The issue is not here when I revert to
elastic-apm==2.1.1
. Will try to do some diggingThe text was updated successfully, but these errors were encountered: