Commit 17715c0
authored
Restore original behavior by always creating a span (#3005)
In the original implementation of celery trace propagation we had code to only create a span for the task if it was NOT started by Celery Beat (because there is no transaction created in the beat process, so also not span should be created).
See this code: https://github.com/getsentry/sentry-python/blob/master/sentry_sdk/integrations/celery.py#L187-L200
Turns out this has never worked and task_started_from_beat has always been False meaning a span was ALWAYS created.
(This did never break anything or caused any troube. When looking into a transaction less future this is also absolutely fine.)
So this PR restores now the original behavior by always creating a span.1 parent 7ef20df commit 17715c0
1 file changed
+4
-11
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
11 | 11 | | |
12 | 12 | | |
13 | 13 | | |
14 | | - | |
| 14 | + | |
15 | 15 | | |
16 | 16 | | |
17 | 17 | | |
| |||
30 | 30 | | |
31 | 31 | | |
32 | 32 | | |
33 | | - | |
34 | 33 | | |
35 | 34 | | |
36 | 35 | | |
| |||
243 | 242 | | |
244 | 243 | | |
245 | 244 | | |
246 | | - | |
247 | | - | |
248 | | - | |
249 | | - | |
250 | | - | |
251 | | - | |
252 | | - | |
253 | | - | |
254 | | - | |
| 245 | + | |
| 246 | + | |
| 247 | + | |
255 | 248 | | |
256 | 249 | | |
257 | 250 | | |
| |||
0 commit comments