All Errors

The "EdgeFunctionError: Function invocation timeout" error occurs when a Supabase Edge Function exceeds its maximum execution time limit. This typically happens with long-running operations, infinite loops, or inefficient code that takes too long to complete within the function's time constraints.

This error occurs when the operating system runs out of buffer space for network operations, typically during heavy socket operations or large data transfers. It indicates system-level resource exhaustion rather than a code-level bug.

npm cannot create a directory because the filesystem or policy blocks it (Windows/WSL AV locks, root-owned prefixes, read-only mounts). Use user-owned paths, release locks, and retry.

This Git error occurs when you try to operate on a file that Git cannot find or does not recognize. Common causes include typos in the filename, the file not being tracked by Git, or case sensitivity issues. The fix depends on whether you need to stage, unstage, or remove a file.

SSH fails to connect or initialize when your .ssh/config file contains invalid or misspelled configuration options. This error occurs during SSH parsing and prevents any connections from being established.

Exit code 143 means the container was stopped by SIGTERM during shutdown. Fix premature kills by adding a SIGTERM handler and raising terminationGracePeriodSeconds.

The 'credential-manager-core was not found' error occurs when Git's configuration references the deprecated credential helper name. Git Credential Manager was renamed from 'manager-core' to 'manager' in late 2022, and older configurations need to be updated.

This security notification appears when a package repository changes its Origin metadata. It requires explicit user acknowledgment before package updates can proceed. Learn how to safely accept these changes.

MySQL Error 1050 occurs when attempting to CREATE a table that already exists in the database. Fix it using IF NOT EXISTS clause or by checking/dropping the existing table first.

This warning appears when apt finds GPG keys in the deprecated /etc/apt/trusted.gpg file instead of the modern /etc/apt/trusted.gpg.d/ directory. While not blocking updates, it indicates outdated key management that should be migrated to comply with current security practices.

The 'no basic auth credentials' error occurs when Docker cannot find authentication credentials for a container registry. This typically happens when you haven't logged in to the registry, credentials have expired, or there's a mismatch between your login context and the command execution context.

The "stdin is not a tty" message appears when SSH runs a command without allocating a terminal, typically with piped input or remote scripts. Force a TTY with the -t flag when one is genuinely needed.

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 error occurs when the Docker CLI cannot establish a TCP connection to the Docker daemon. The daemon may not be running, not listening on the expected port, or network/firewall issues are blocking the connection.

This error occurs in ioredis when a command cannot complete because the Redis connection has been lost and reconnection attempts have exceeded the configured limit. By default, ioredis will retry each pending command up to 20 times before failing with this error.

MySQL Error 1451 occurs when you try to delete or update a row in a parent table that has child rows referencing it through a foreign key constraint. This error protects referential integrity but can be resolved by deleting child rows first, using CASCADE rules, or modifying your constraint strategy.

EUNKNOWNCOMMAND occurs when you run an npm command that doesn't exist or is misspelled. Check your command spelling and verify the command exists in npm documentation.

This error occurs when a user lacks the required privileges to access or modify a table. Fix it by granting appropriate permissions using the GRANT statement.

Git has detected a UTF-8 Byte Order Mark at the beginning of a file. While valid UTF-8, BOMs can cause cross-platform compatibility issues with diff, merge, and patch operations.

Git server rejects your push because the repository or namespace has exceeded its storage quota limit. This commonly occurs on platforms like GitHub, GitLab, and Bitbucket when repositories grow too large or contain oversized files.