When old_execute_command raises an exception, db_span.__exit__() and cache_span.__exit__() are never called because there's no try/finally block wrapping the await call. This differs from the sync version in _sync_common.py which correctly uses try/finally at lines 151-160. Leaking spans will cause incorrect timing data and potential memory/scope issues.

Also found at:

• sentry_sdk/integrations/redis/_sync_common.py:158

The code calls self.span._to_traceparent(), self.span._to_baggage(), and self._span._get_trace_context() on the span object. However, the Span type from tracing.py (used in legacy non-streaming mode) only defines the non-underscore versions: to_traceparent(), to_baggage(), and get_trace_context(). This will cause AttributeError at runtime when using the SDK in non-streaming mode.

Setting self._segment = None on line 586 without overriding _dynamic_sampling_context() and _get_trace_context() in NoOpStreamedSpan causes a runtime error. When scope.get_trace_context() is called with an active NoOpStreamedSpan, it invokes the inherited _get_trace_context() which calls _dynamic_sampling_context(), which accesses self._segment._get_baggage() - resulting in AttributeError: 'NoneType' object has no attribute '_get_baggage'.

In the span streaming branch (lines 218-241), a span is always created via start_span() at line 238, regardless of whether the HTTP method is in http_methods_to_capture. In contrast, the legacy branch (lines 243-275) only creates a transaction when method in self.http_methods_to_capture. This causes HTTP requests with methods like OPTIONS, HEAD, etc. (if not in the filter) to create unnecessary spans in streaming mode, potentially impacting performance and creating unwanted telemetry data.

When using span streaming mode, the HTTP response status code is not recorded as an attribute via SPANDATA.HTTP_STATUS_CODE. Only span.status is set to "ok" or "error". This breaks consistency with the legacy API where set_http_status() sets both the status and the numeric status code. Features that depend on the status code attribute (like trace_ignore_status_codes filtering or breadcrumb creation) will not work correctly for streamed spans.

Also found at:

• sentry_sdk/integrations/httpx.py:200-201

The isinstance(span, StreamedSpan) assertion on line 1008 will always pass even when span is a NoOpStreamedSpan, because NoOpStreamedSpan inherits from StreamedSpan. This test is meant to verify that non-ignored spans are real StreamedSpan instances (not NoOp), but the current check provides a false sense of security since it cannot distinguish between the two types. The test relies solely on the span.sampled is True check which precedes it, making the isinstance assertion redundant and misleading.