All Errors

This error occurs when a query references a table that was not included in a preceding LOCK TABLES statement. Fix it by adding all required tables to your lock statement or by using UNLOCK TABLES to release locks and switch to transactions.

This error occurs when Node.js attempts to perform I/O operations on a file descriptor that has already been closed or is invalid. It commonly happens with double-close scenarios, premature stream closures, or attempting to read/write after a file handle has been released.

A TLS handshake timeout occurs when the client and server fail to complete the SSL/TLS negotiation within the timeout period (default 120 seconds). This typically indicates network delays, server resource constraints, or infrastructure issues.

This error occurs when Node.js tries to load a native addon compiled for glibc on Alpine Linux (which uses musl). The fix involves rebuilding native modules with Alpine's build tools or switching to a glibc-based Docker image.

The ENOSPC error occurs when npm cannot write files due to insufficient disk space. Clear npm cache, remove node_modules, or free up disk space to resolve this.

npm encountered a 401 Unauthorized HTTP response when attempting to fetch a scoped package. This indicates the registry rejected the request due to missing, invalid, expired, or incorrectly configured authentication credentials.

This Python error typically occurs during package installation or configuration. Check your environment setup and verify package availability.

This error occurs when a Redis replica attempts to synchronize with a master that is itself a replica but has lost its own master connection. Fixing it requires ensuring proper master configuration and network connectivity in your replication topology.

This error occurs when the SSH client detects that a server's ECDSA host key has changed from what is stored locally. It's a security warning that prevents automatic connection to the server, requiring you to verify that the host hasn't been compromised or replaced.

This error occurs when you try to generate an SSH key with a type that ssh-keygen doesn't recognize or support. It's usually caused by a typo in the key type name, using an unsupported algorithm on your OpenSSH version, or trying to use deprecated key types.

This error occurs when attempting to link an OAuth identity that is already associated with another user account in Supabase Auth, commonly when converting anonymous users to verified accounts.

This error occurs when apt tries to add a GPG key for a repository but the gnupg package is not installed on the system. This commonly happens in minimal Docker images or fresh Linux installations when running apt-key commands.

This Git warning appears when a filename contains characters that are not valid UTF-8 encoding. It commonly occurs with files created on systems using different character encodings (like Latin-1 or Windows code pages) and can cause cross-platform issues.

This Git warning appears when running sparse-checkout commands on a repository that hasn't been initialized for sparse checkout. Enable sparse checkout with 'git sparse-checkout init' or disable the feature to resolve it.

This error occurs when Git expects a symbolic reference (like HEAD pointing to a branch) but finds a direct commit SHA or corrupted reference instead. Most commonly happens in detached HEAD state or with corrupted .git files.

This Git error occurs when you try to run a command that Git doesn't recognize. It usually means you've misspelled a command, forgot to install a Git extension, or are trying to use a command that doesn't exist. The fix involves checking spelling, installing missing extensions, or using the correct command name.

This error occurs when Node.js cannot load a compiled native addon module from the expected build directory. Native modules are C++ extensions that must be compiled for your specific platform and Node.js version.

This error occurs when npm attempts to clone a git repository during dependency installation but git cannot locate the repository at the specified URL. This suggests either the URL is wrong, the repository doesn't exist, or you lack permissions.

This error occurs when SQLite cannot upgrade a read transaction to a write transaction due to snapshot isolation conflicts. It happens when a transaction starts in read mode, but later tries to write while other transactions are accessing the same data snapshot.

This error occurs during SSH port forwarding (tunneling) when the target service is not running, listening on the wrong port, or blocked by a firewall. The SSH connection succeeds, but the forwarded connection to the remote service fails.