When span streaming is enabled, `get_start_span_function()` returns `sentry_sdk.traces.start_span` which only accepts `name` (positional), `attributes`, and `parent_span` parameters. However, all callers (e.g., anthropic.py:408, mcp.py:440, google_genai:76, langchain.py:982) invoke the returned function with `op=...`, `name=...`, `origin=...` kwargs which are not accepted by the new streaming API. This will cause a `TypeError` at runtime when span streaming mode is enabled.

When span streaming is enabled, `get_start_span_function()` returns `sentry_sdk.traces.start_span` which only accepts `name` (positional), `attributes`, and `parent_span` parameters. However, all callers (e.g., anthropic.py:408, mcp.py:440, google_genai:76, langchain.py:982) invoke the returned function with `op=...`, `name=...`, `origin=...` kwargs which are not accepted by the new streaming API. This will cause a `TypeError` at runtime when span streaming mode is enabled.

When span streaming is enabled, `get_start_span_function()` returns `sentry_sdk.traces.start_span` which only accepts `name` (positional), `attributes`, and `parent_span` parameters. However, all callers (e.g., anthropic.py:408, mcp.py:440, google_genai:76, langchain.py:982) invoke the returned function with `op=...`, `name=...`, `origin=...` kwargs which are not accepted by the new streaming API. This will cause a `TypeError` at runtime when span streaming mode is enabled.

When `old_execute_command` raises an exception, the `value` variable at line 142 is never assigned. However, the `finally` block at lines 143-150 always executes and attempts to use `value` in `_set_cache_data(cache_span, self, cache_properties, value)` at line 148. This causes an `UnboundLocalError`, masking the original Redis exception and preventing proper error propagation to the caller.

When `old_execute_command` raises an exception, the `value` variable at line 142 is never assigned. However, the `finally` block at lines 143-150 always executes and attempts to use `value` in `_set_cache_data(cache_span, self, cache_properties, value)` at line 148. This causes an `UnboundLocalError`, masking the original Redis exception and preventing proper error propagation to the caller.

When `old_execute_command` raises an exception, the `value` variable at line 142 is never assigned. However, the `finally` block at lines 143-150 always executes and attempts to use `value` in `_set_cache_data(cache_span, self, cache_properties, value)` at line 148. This causes an `UnboundLocalError`, masking the original Redis exception and preventing proper error propagation to the caller.

The `graphql_span` is created with `sentry_sdk.traces.start_span()` but neither `start()` is called nor is it used as a context manager before `yield`. When `end()` is called after the yield, it calls `__exit__()` which tries to access `self._context_manager_state` which was never set by `__enter__()`. This raises an `AttributeError` that's silently caught by `capture_internal_exceptions()`, causing `_end()` to never be called and the span to never be sent.

The `graphql_span` is created with `sentry_sdk.traces.start_span()` but neither `start()` is called nor is it used as a context manager before `yield`. When `end()` is called after the yield, it calls `__exit__()` which tries to access `self._context_manager_state` which was never set by `__enter__()`. This raises an `AttributeError` that's silently caught by `capture_internal_exceptions()`, causing `_end()` to never be called and the span to never be sent.

The `graphql_span` is created with `sentry_sdk.traces.start_span()` but neither `start()` is called nor is it used as a context manager before `yield`. When `end()` is called after the yield, it calls `__exit__()` which tries to access `self._context_manager_state` which was never set by `__enter__()`. This raises an `AttributeError` that's silently caught by `capture_internal_exceptions()`, causing `_end()` to never be called and the span to never be sent.

❌ Patch coverage check failed: 11.65% < target 80%

❌ Patch coverage check failed: 11.65% < target 80%

Failed to upload coverage artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Failed to upload test artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

❌ Patch coverage check failed: 11.73% < target 80%

Failed to upload coverage artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Failed to upload test artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

❌ Patch coverage check failed: 11.65% < target 80%

Failed to upload coverage artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Failed to upload test artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

❌ Patch coverage check failed: 11.73% < target 80%

Failed to upload coverage artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Failed to upload test artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

❌ Patch coverage check failed: 11.73% < target 80%

Failed to upload coverage artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Failed to upload test artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

❌ Patch coverage check failed: 11.73% < target 80%

Failed to upload coverage artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Failed to upload test artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

❌ Patch coverage check failed: 11.73% < target 80%

Failed to upload coverage artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Failed to upload test artifact: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

In `_sentry_execute_command`, the async version does not wrap the `await old_execute_command()` call in a try/finally block, unlike the sync version in `_sync_common.py`. If the Redis command raises an exception, `db_span.__exit__()` and `cache_span.__exit__()` will never be called, causing the spans to remain unclosed. This could lead to resource leaks and corrupted tracing state.

In `_sentry_execute_command`, the async version does not wrap the `await old_execute_command()` call in a try/finally block, unlike the sync version in `_sync_common.py`. If the Redis command raises an exception, `db_span.__exit__()` and `cache_span.__exit__()` will never be called, causing the spans to remain unclosed. This could lead to resource leaks and corrupted tracing state.

In the span streaming code path (lines 109-127), `span.start()` is called which sets the span as active on the scope and saves the old span in `_context_manager_state`. If `real_putrequest()` at line 148 raises an exception, `span.end()` in `getresponse` is never called, leaving the scope's `span` attribute pointing to an orphaned span and never restoring the previous span. This corrupts the scope state for subsequent operations in the same request/thread.

The `dynamic_sampling_context()` method in `StreamedSpan` (line 509-510) accesses `self.segment.get_baggage()` without null checking. Since `NoOpStreamedSpan` sets `self.segment = None` (line 666) and does not override `dynamic_sampling_context()`, calling this method on a `NoOpStreamedSpan` instance will raise `AttributeError: 'NoneType' object has no attribute 'get_baggage'`. While internal SDK code only calls this on sampled spans, user code could call this method on any span returned from `start_span()`, causing an unexpected crash.

When `ignore_spans` contains a dict with only unrecognized keys (e.g., a typo like `{"nme": "/health"}` instead of `{"name": "/health"}`), both `name_matches` and `attributes_match` default to `True`, causing the rule to match ALL spans. This could silently drop all trace data due to a simple configuration mistake.

When an exception occurs during a GraphQL operation, the `finally` block calls `_graphql_span.end()` which internally invokes `__exit__(None, None, None)`. The `StreamedSpan.__exit__` method checks `if value is not None and should_be_treated_as_error(ty, value)` to set the span status to ERROR, but since `end()` always passes `None` for the exception info, the span status will remain OK even when the operation fails with an exception. The legacy code path (`finish()`) has the same limitation, but this is a missed opportunity to fix it for the new API.

When an exception occurs during a GraphQL operation, the `finally` block calls `_graphql_span.end()` which internally invokes `__exit__(None, None, None)`. The `StreamedSpan.__exit__` method checks `if value is not None and should_be_treated_as_error(ty, value)` to set the span status to ERROR, but since `end()` always passes `None` for the exception info, the span status will remain OK even when the operation fails with an exception. The legacy code path (`finish()`) has the same limitation, but this is a missed opportunity to fix it for the new API.