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
Upstream issue celery/celery#4875 closed #4649
Comments
It appears that this celery bug has been resolved for 4.5 and 5.0.3. |
I tried removing the code referenced by the comment, and it causes the test |
The issue referenced was [resolved](celery/celery#6374), but it actually does not apply to the bit of code it's pointing to. Fixes #4649 I tried removing the code referenced by the comment, and it causes the test `tests/contrib/celery/test_integration.py::CeleryDistributedTracingIntegrationTask::test_distributed_tracing_propagation_async` to fail. As far as I can tell from about an hour of investigation, the celery [fix](celery/celery#4356) only affects "hybrid messages" (those that blend protocol 1 and 2 syntax as part of a rolling Celery upgrade), which our test suite doesn't use.
The issue referenced was [resolved](celery/celery#6374), but it actually does not apply to the bit of code it's pointing to. Fixes DataDog#4649 I tried removing the code referenced by the comment, and it causes the test `tests/contrib/celery/test_integration.py::CeleryDistributedTracingIntegrationTask::test_distributed_tracing_propagation_async` to fail. As far as I can tell from about an hour of investigation, the celery [fix](celery/celery#4356) only affects "hybrid messages" (those that blend protocol 1 and 2 syntax as part of a rolling Celery upgrade), which our test suite doesn't use.
Upstream issue celery/celery#4875 referenced in the file:
has been closed.
The code referencing this issue could potentially be updated.
The text was updated successfully, but these errors were encountered: