chore(dramatiq): Remove transaction-based tracing - #7445
Conversation
Codecov Results 📊✅ 71427 passed | ⏭️ 3370 skipped | Total: 74797 | Pass Rate: 95.49% | Execution Time: 218m 9s 📊 Comparison with Base Branch
All tests are passing successfully. ✅ Patch coverage is 100.00%. Project has 2286 uncovered lines. Files with missing lines (1)
Coverage diff@@ Coverage Diff @@
## master #PR +/-##
==========================================
- Coverage 90.20% 89.99% -0.21%
==========================================
Files 193 185 -8
Lines 25788 22831 -2957
Branches 9530 8328 -1202
==========================================
+ Hits 23261 20545 -2716
- Misses 2527 2286 -241
- Partials 1432 1336 -96Generated by Codecov Action |
| SPANDATA.MESSAGING_DESTINATION_NAME, message.queue_name | ||
| ) | ||
| message._sentry_span_ctx = transaction | ||
| scope.set_transaction_name(message.actor_name, source=SegmentNameSource.TASK) |
There was a problem hiding this comment.
This is new ^, wasn't there in the old streaming branch
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit a2dbfda. Configure here.
| }, | ||
| SPANSTATUS.OK, | ||
| True, | ||
| True, |
There was a problem hiding this comment.
Unused capture_events fixture parameter left in test
Low Severity
The capture_events fixture parameter was left in the test_task_transaction function signature after removing the transaction-based code path. The function now only uses capture_items but capture_events is still requested as a fixture without ever being called. Every other occurrence of capture_events in this file actually invokes it (e.g., events = capture_events()). This is a leftover from the refactoring that adds unnecessary noise to the test signature.
Reviewed by Cursor Bugbot for commit a2dbfda. Configure here.


Closes https://linear.app/getsentry/issue/PY-2690/remove-transaction-based-tracing-from-dramatiq