All Errors

This error occurs when the SSH connection is unexpectedly terminated by the remote server during the authentication or communication phase. The server closes the TCP connection without properly completing the SSH protocol handshake, often due to server configuration issues, firewall blocking, or resource constraints.

The SQLITE_READONLY_RECOVERY error occurs when SQLite is attempting to recover a WAL (Write-Ahead Logging) mode database but lacks the necessary write permissions to complete the recovery process. This typically happens when a database connection was improperly closed or crashed, and SQLite needs to replay uncommitted changes from the WAL file back to the main database but is prevented by insufficient file system permissions.

PostgreSQL error 22P03 occurs when binary data format is invalid or mismatched with the column type. This happens with bytea columns, COPY BINARY operations, or client driver encoding issues.

This Vite error occurs when the bundler cannot locate an imported module, typically due to incorrect paths, missing dependencies, or misconfigured path aliases.

This SSH error occurs when the server cannot allocate a pseudo-terminal (PTY) for your session. It typically appears with git operations, SFTP transfers, or interactive SSH connections and is usually non-fatal but indicates the server rejected TTY allocation.

The Prisma P2002 error occurs when you attempt to insert or update a record with a value that violates a unique constraint in your database. This happens when trying to create a duplicate entry for a field marked as @unique, such as an email address that already exists. The fix typically involves checking for existing records before insertion or using upsert operations.

A NOT NULL constraint violation occurs when you try to insert or update a record with a NULL value in a column that requires a value. Learn how to identify the problematic column and fix the query.

This error occurs when importing modules without file extensions in Vite projects. Node.js ESM requires explicit file extensions in all import statements, and Vite enforces this standard.

This error occurs when your app lacks the necessary permissions to read or write files in Firebase Cloud Storage. Learn how to authenticate users, configure security rules, and fix access issues in your Firebase project.

PostgreSQL error 42P21 occurs when the database cannot determine which collation to use for string comparison operations. This happens when comparing or joining columns with different collation settings, or when UNION/CASE statements combine strings that use incompatible sorting rules.

This TypeScript error occurs when strictNullChecks is enabled and you try to assign a null value to a variable or parameter typed as string. The fix involves using union types, type guards, or the non-null assertion operator.

Error 22001 occurs when you try to insert or update a string value that exceeds the defined column length (e.g., a 15-character string in a VARCHAR(10) column). PostgreSQL rejects the data to protect data integrity, and you must either shorten the data or expand the column.

This error occurs when a user with an active ban attempts to authenticate or refresh their session in Supabase. Banned users cannot log in or refresh tokens until their ban expires or is lifted.

This SSH warning occurs when you run commands with piped or redirected input without allocating a terminal. The fix involves using SSH flags like -t, -tt, or -T depending on your use case.

This error occurs when you try to insert or update data in a SQLite table that violates a CHECK constraint. CHECK constraints enforce data validation rules at the database level, ensuring only valid data enters your table.

This TypeScript error occurs when you assign an object that lacks required properties defined in its type or interface. TypeScript enforces that objects must include all non-optional properties.

PostgreSQL throws this error when a date or timestamp string does not match the expected format. Fix it by ensuring your input dates are in the correct format (YYYY-MM-DD for dates, YYYY-MM-DD HH:MM:SS for timestamps) or by using TO_DATE() and TO_TIMESTAMP() functions with explicit format masks.

This MySQL error occurs when attempting to create or alter a table with all columns marked as INVISIBLE. MySQL requires every table to have at least one visible column to ensure data can be retrieved via standard SELECT * queries.

TypeScript only accepts .d.ts files as declaration sources, so pointing a typeRoots, types, or package types path at a .ts file triggers this error. Rename the declaration material to .d.ts and regenerate your package.ts output before publishing so the compiler can safely load the definitions.

TypeScript tuples are fixed-length arrays and each index must be explicitly declared. Accessing an index that is outside the known length causes the compiler to throw the "Tuple type 'X' of length 2 has no element at index 3" error.