When old_execute_command raises an exception, the variable value is never assigned, but the finally block on line 148 attempts to use it in _set_cache_data(cache_span, self, cache_properties, value). This will raise an UnboundLocalError: local variable 'value' referenced before assignment, masking the original Redis exception and breaking error handling.

Also found at:

• sentry_sdk/integrations/redis/_async_common.py:120-135

When span streaming is enabled, sentry_sdk.traces.start_span() returns a StreamedSpan that requires .start() or a with block to properly initialize. In on_operation(), the span is created (line 192-194) but .start() is never called. When self.graphql_span.finish() is later called (line 234), StreamedSpan.__exit__() tries to access _context_manager_state which was never set by __enter__(). This raises an AttributeError that's silently caught by capture_internal_exceptions(), preventing the span from being sent to Sentry. Compare with graphene.py which correctly calls .start() after creating the streaming span.

Also found at:

• sentry_sdk/integrations/strawberry.py:239-246
• sentry_sdk/integrations/strawberry.py:261-266

The _estimate_size() method calls _to_transport_format() on every span added (unless count-based flush triggers first), and then _flush() calls _to_transport_format() again for all buffered spans. This means each span's attributes are serialized twice via serialize_attribute(), which iterates through all attribute values and creates dictionary structures. For spans with many attributes, this duplication adds unnecessary CPU overhead in a performance-sensitive code path.

The modified _set_status function always sets SpanStatus.ERROR for StreamedSpan regardless of the status argument. This causes Celery control flow exceptions (Retry, Ignore, Reject) that should be marked as "aborted" to be incorrectly marked as errors. While the new SpanStatus enum only has OK and ERROR values, hardcoding ERROR loses the semantic distinction between intentional control flow and actual errors, potentially causing misleading trace data.

At line 1273, NoOpStreamedSpan() is created without the scope parameter, unlike lines 1237 and 1255 which pass scope=self. When _scope is None in NoOpStreamedSpan, the __enter__ method returns early without setting scope.span = self, and __exit__ won't restore the old span. This breaks context manager behavior for ignored child spans - the ignored span won't be tracked in the scope, causing inconsistent span hierarchy when nested spans are used.

The docstring example references @trace(op="custom") but the function signature only accepts name and attributes parameters. Users following this documentation will get a TypeError: trace() got an unexpected keyword argument 'op' at runtime. This is a backwards compatibility concern as users migrating from the old API may expect the op parameter to work.

The json module is imported on line 1 but is never used in this file. The json keyword appearing on lines 24, 127, and 132 are either string literals or keyword arguments to PayloadRef, not uses of the json module.

The span name for sentry_patched_popen_wait is set to 'subprocess popen' but this function wraps Popen.wait(), not Popen.__init__(). This will make traces confusing as the wait spans will be mislabeled. The communicate function correctly uses 'subprocess communicate'.

The function imports should_send_default_pii at line 1058 but never uses it. This appears to be copied from the similar create_span_decorator function which actually uses should_send_default_pii for PII handling. This is dead code that may indicate incomplete implementation - the streaming decorator may be missing PII handling logic that exists in the non-streaming version.