The code calls self._span.segment.set_name(name) when self._span is an instance of StreamedSpan. However, NoOpStreamedSpan is a subclass of StreamedSpan that sets self.segment = None in its constructor. When self._span is a NoOpStreamedSpan, accessing self._span.segment.set_name(name) will raise AttributeError: 'NoneType' object has no attribute 'set_name'. The code should either check isinstance(self._span, NoOpStreamedSpan) first or use a null check on segment before calling methods on it.

Also found at:

• sentry_sdk/traces.py:527-528

The variable span_ctx is declared at line 324 but only assigned inside the capture_internal_exceptions() block (lines 337/360). If an exception occurs after transaction is assigned (e.g., at line 333-335 or 349-359) but before span_ctx is assigned, the exception is suppressed but span_ctx remains unbound. The check at line 362 only verifies transaction is not None, then line 365 with span_ctx: will raise UnboundLocalError, crashing the Celery task execution.

StreamedSpan is imported inside the if TYPE_CHECKING: block (line 30), but it's used in an isinstance() check at runtime (line 167 in graphql_span). When span streaming is enabled and the finally block executes, a NameError: name 'StreamedSpan' is not defined will be raised because the import is not available at runtime.

Also found at:

• sentry_sdk/integrations/stdlib.py:127

In set_transaction_name, the code checks isinstance(self._span, StreamedSpan) and then accesses self._span.segment.set_name(name). However, NoOpStreamedSpan (a subclass of StreamedSpan) sets segment = None in its constructor. Since isinstance() returns True for subclasses, when the current span is a NoOpStreamedSpan, accessing .segment.set_name() will raise AttributeError: 'NoneType' object has no attribute 'set_name'. This can occur when spans are filtered out via is_ignored_span() or when a span has no name.

When size + 1 >= MAX_BEFORE_FLUSH on line 68, the code returns early without updating _running_size[span.trace_id]. The span has already been added to _span_buffer (line 66), but its size is never tracked. If the flush event doesn't clear all buffers immediately (e.g., due to threading), subsequent byte-based flush decisions will underestimate the actual buffer size, potentially causing memory growth beyond the intended limit.

Also found at:

• sentry_sdk/integrations/redis/utils.py:152-160

When scope.span is a StreamedSpan, the code always sets SpanStatus.ERROR regardless of the actual status parameter passed to _set_status. This loses the distinction between "aborted" (for control flow exceptions like Retry, Ignore, Reject) and "internal_error" (for actual failures). Since StreamedSpan.set_status() accepts Union[SpanStatus, str] and handles both types correctly, the status parameter should be passed through.

Also found at:

• sentry_sdk/integrations/strawberry.py:314-320

In _wrap_tracer, the span_ctx variable is declared with a type annotation but not initialized. In the span_streaming branch, if start_span() succeeds but any subsequent setter method (set_origin, set_source, set_op) throws an exception, the exception is suppressed by capture_internal_exceptions() but span_ctx is never assigned. Since transaction is not None, the code proceeds to with span_ctx: (line 365), causing an UnboundLocalError that crashes the Celery task.

The httpx integration now supports both legacy tracing and the new span streaming mode (trace_lifecycle: stream), but the existing tests in tests/integrations/httpx/test_httpx.py only test the legacy mode using start_transaction(). The new StreamedSpan code paths (lines 64-67, 80-88, 145-148, 161-168) are not covered by any integration tests, meaning bugs in span attribute setting or the streaming workflow won't be caught.

In _sentry_execute_command, spans are opened via __enter__() but closed via __exit__(None, None, None) without a try/finally block. If await old_execute_command() raises an exception, both db_span and cache_span will never have __exit__ called, leaving them unclosed. This can cause memory leaks and incorrect tracing data (spans that are never finished).

Also found at:

• sentry_sdk/integrations/redis/_sync_common.py:135-146

In on_parse() for streaming mode (line 261-262), sentry_sdk.traces.start_span() is called without the parent_span=self.graphql_span argument, unlike on_validate() (line 239-240) which correctly passes it. This inconsistency means the parsing span will be parented to whatever span is currently active on the scope rather than explicitly to self.graphql_span, potentially causing incorrect span hierarchy in the trace.