Skip to content

fix: restore does not exist to validation error classification #613

Description

@anandgupta42

Problem

PR #611 removed "does not exist" from the validation error classification keywords to prevent HTTP 404 messages from being misclassified. However, the pattern reordering in the same PR (moving http_error before validation) already prevents that issue.

The removal caused SQL errors like "column foo does not exist" to fall through to unknown instead of validation.

Found by

Multi-model code review (Claude + Gemini 3.1 Pro consensus).

Fix

Restore "does not exist" to validation keywords. HTTP 404 errors still classify correctly as http_error because that pattern has priority.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions