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

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.

In _end(), the scope variable is carefully resolved on lines 397-399 to use the passed scope, self._scope, or the current scope as fallback. However, on line 438, sentry_sdk.get_current_scope()._capture_span(self) ignores this resolved scope and fetches a fresh current scope instead. If the current scope has changed between entering and ending the span (e.g., in async contexts), this could cause the span to be captured with incorrect scope data.

The json module is imported at line 1 but is not used anywhere in the file. All JSON serialization is done via PayloadRef(json=...) which doesn't require the json import. This adds unnecessary overhead during module loading.

The new populate_from_segment method does not check if segment._name is truthy before setting sentry_items["transaction"], unlike the legacy populate_from_transaction which checks transaction.name first. If a segment has an empty string name, it will be included in baggage headers, whereas the legacy code would omit it. This is a subtle backwards compatibility issue that could affect downstream services parsing baggage.

The function create_streaming_span_decorator imports should_send_default_pii from sentry_sdk.scope at line 1058 but never uses it. This appears to be copy-paste from the original create_span_decorator function where it is used. While this doesn't cause runtime errors, it adds unnecessary overhead to each decorator invocation and indicates incomplete implementation - the decorator may be missing PII filtering that should be applied.