The code assigns set_on_span = span.set_attribute when the span is an instance of Span, but the Span class (in sentry_sdk/tracing.py) does not have a set_attribute method. This will cause an AttributeError at runtime when _record_exception_on_span is called with a legacy Span object. The logic appears to be inverted - Span has set_data() while StreamedSpan has set_attribute().

Also found at:

• sentry_sdk/integrations/sqlalchemy.py:102

In _sentry_execute_command, the db_span and cache_span are entered via __enter__() but their __exit__() calls (lines 152, 156) are not protected by a try/finally block. If old_execute_command raises an exception, the spans will never be closed, causing span leaks and incorrect timing data. The sync version in _sync_common.py correctly uses try/finally for this pattern.

Also found at:

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

In the span streaming branch (lines 218-241), a span is always created via start_span() at line 238, even when ty == 'http' and the method is not in http_methods_to_capture. In contrast, the legacy branch correctly sets transaction = None and uses nullcontext() to skip span creation for filtered methods. This causes unintended spans to be created and sent for HTTP methods that should be excluded.

Also found at:

• sentry_sdk/integrations/graphene.py:174-175

When using span streaming mode, the code sets span.status and span.set_attribute("reason", ...) but doesn't set the HTTP status code attribute (SPANDATA.HTTP_STATUS_CODE). The legacy Span.set_http_status() method sets both the status and http.response.status_code. This means StreamedSpans will be missing important HTTP status code telemetry data that the legacy spans include.

Also found at:

• sentry_sdk/integrations/httpx.py:199-201
• sentry_sdk/integrations/stdlib.py:175-177

The constants BAGGAGE_HEADER_NAME and SENTRY_TRACE_HEADER_NAME are defined twice in succession (lines 41-42 and 45-46). While this doesn't cause a runtime error since both definitions have identical values, it indicates a likely copy-paste mistake and unnecessary code duplication.