In sentry_patched_execute_command, if old_execute_command raises an exception, the finally block will attempt to access value in the call to _set_cache_data(cache_span, self, cache_properties, value), but value was never assigned. This causes an UnboundLocalError: local variable 'value' referenced before assignment, which will crash the application instead of propagating the original Redis exception.

Also found at:

• sentry_sdk/integrations/redis/_async_common.py:145-147

The code calls span.set_status(SpanStatus.ERROR) on line 102 when the span is a StreamedSpan. However, StreamedSpan class (defined in sentry_sdk/traces.py) does not have a set_status() method - it only has a status property setter. This will raise an AttributeError at runtime when a SQL error occurs in streaming mode. The fix should use property assignment: span.status = SpanStatus.ERROR.

Also found at:

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

When using span streaming mode, the HTTP status code (e.g., 200, 404, 500) is not recorded as an attribute on the span. Only the status ('ok'/'error') and 'reason' are set. Compare with wsgi.py line 235 which correctly calls span.set_attribute("http.response.status_code", status_int) for StreamedSpan. This results in data loss - users won't see the actual HTTP status code in their traces when using span streaming mode.

The sentry_patched_popen_wait function incorrectly sets the span name to 'subprocess popen' when it should be 'subprocess wait' to match the OP.SUBPROCESS_WAIT operation and the method being wrapped. This inconsistency will make it harder to identify subprocess.wait spans in the Sentry UI, as the span name won't match the operation being performed.