-
Notifications
You must be signed in to change notification settings - Fork 93
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
Issue working with Sentry celery integration #105
Comments
Hi @mumumumu thanks for reporting. |
I'm currently experiencing this issue as well - even after the monkey patch change in the Sentry SDK.
|
…ameronmaske/celery-once/issues/105) Add tests for celery_once. Move re-usable pytest fixture for celery into a common conftest.py.
@mackthehack Are you on Python 2? |
I'm using python 3.6. |
Can you try 3.0.1 and see if that fixes the error? It changes how keys are generated. |
3.0.1 should resolve this issue. I'll re-open if anyone else experiences this. |
I'm trying to use
celery-once
with the Sentry celery integration, but I'm running into an issue with how Sentry patches the task tracer.The issue I'm seeing is that the key before and after the task is patched are different. I believe this is because of how
inspect.getcallargs
is working with Sentry's wrappedrun
method.Would there be anything wrong with storing the key on the task instance like this:
The text was updated successfully, but these errors were encountered: