Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="drift/instrumentation/psycopg/instrumentation.py">

<violation number="1" location="drift/instrumentation/psycopg/instrumentation.py:378">
P2: Span is not ended when `RuntimeError` is raised. This causes a resource leak. Consider wrapping in try/finally to ensure `span_info.span.end()` is always called.</violation>
</file>

<file name="drift/core/mode_utils.py">

<violation number="1" location="drift/core/mode_utils.py:57">
P2: Inconsistent error handling: `is_background_request` makes the same SDK calls that are protected by try-except in `handle_record_mode`. Consider adding error handling and returning `False` on failure (safe default).</violation>

<violation number="2" location="drift/core/mode_utils.py:57">
P2: Inconsistent error handling: `handle_record_mode` wraps these same SDK calls in try-except, but `handle_replay_mode` does not. If `TuskDrift.get_instance()` or subsequent calls can fail, this function should also handle exceptions gracefully to avoid crashing the instrumented application.</violation>
</file>

<file name="drift/instrumentation/psycopg2/instrumentation.py">

<violation number="1" location="drift/instrumentation/psycopg2/instrumentation.py:471">
P2: Span is not ended before raising RuntimeError, causing a span leak. Add `span_info.span.end()` before the raise statement to ensure the span is properly closed.</violation>
</file>

<file name="drift/instrumentation/redis/instrumentation.py">

<violation number="1" location="drift/instrumentation/redis/instrumentation.py:199">
P1: Span is never ended in `_replay_execute_command`. The `SpanUtils.with_span()` context manager only handles context attach/detach but does not end the span. Add `span_info.span.end()` in a finally block to ensure the span is properly closed.</violation>

<violation number="2" location="drift/instrumentation/redis/instrumentation.py:199">
P1: Span is never ended in `_replay_pipeline_execute`. The `SpanUtils.with_span()` context manager only handles context attach/detach but does not end the span. Add `span_info.span.end()` in a finally block to ensure the span is properly closed.</violation>
</file>