The code assigns span.set_attribute for Span instances and span.set_data for StreamedSpan instances, but these methods don't exist on those respective classes. Span (from tracing.py) has set_data() but not set_attribute(), while StreamedSpan (from traces.py) has set_attribute() but not set_data(). This will cause an AttributeError at runtime when _record_exception_on_span is called.

Also found at:

• sentry_sdk/integrations/sqlalchemy.py:102

In sentry_patched_execute_command, the value variable is assigned inside the try block (line 152), but it's accessed in the finally block (line 158). If old_execute_command raises an exception, value is never assigned, causing an UnboundLocalError when _set_cache_data(cache_span, self, cache_properties, value) is called. This will mask the original Redis exception with an internal error.

In the span streaming branch (lines 218-241), when ty is 'http' but the method is NOT in http_methods_to_capture, the code still creates a span via sentry_sdk.traces.start_span() (line 238). In the legacy branch, transaction would remain None and nullcontext() would be used instead. This behavioral difference causes spans to be created and sent for HTTP methods that users have explicitly configured to ignore, potentially leading to excessive span volume and unexpected costs.

In the synchronous send() function, when span_streaming is enabled, the HTTP response status code is not being set as an attribute on the span. The legacy Span.set_http_status() method sets SPANDATA.HTTP_STATUS_CODE (i.e., http.response.status_code), but the StreamedSpan path only sets the status string ("ok"/"error") and the "reason" attribute. This causes a data inconsistency where spans sent in streaming mode will be missing the HTTP status code, which is important telemetry data for HTTP client spans.

Also found at:

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

The async _sentry_execute_command function manually enters db_span and cache_span using __enter__() but lacks a try...finally block to ensure __exit__() is called when old_execute_command raises an exception. In contrast, the sync version in _sync_common.py wraps the call in try...finally. If the Redis command throws, spans won't be closed, the scope's active span won't be restored, and the error status won't be set on the spans.