Error Set TcpConnectToHostError [src]

In WASI, this error may occur when the file descriptor does not hold the required rights to open a new resource relative to it.

The implementation does not support the specified address family.

The given address is already in use, or in the case of Internet domain sockets, The port number was specified as zero in the socket address structure, but, upon attempting to bind to an ephemeral port, it was determined that all port numbers in the ephemeral port range are currently in use. See the discussion of /proc/sys/net/ipv4/ip_local_port_range ip(7).

A nonexistent interface was requested or the requested address was not local.

The socket is already connected, and a specified option cannot be set while the socket is connected.

On Windows, antivirus software is enabled by default. It can be disabled, but Windows Update sometimes ignores the user's preference and re-enables it. When enabled, antivirus software on Windows intercepts file system operations and makes them significantly slower in addition to possibly failing with this error code.

On Windows, file paths cannot contain these characters: '/', '*', '?', '"', '<', '>', '|'

reading a timerfd with CANCEL_ON_SET will lead to this error when the clock goes through a discontinuous change

Socket is non-blocking and already has a pending connection in progress.

A connect() on a stream socket found no one listening on the remote address.

Connection was reset by peer before connect could complete.

Timeout while attempting connection. The server may be too busy to accept new connections. Note that for IP sockets the timeout may be very long when syncookies are enabled on the server.

One of these three things:

• pathname refers to an executable image which is currently being executed and write access was requested.
• pathname refers to a file that is currently in use as a swap file, and the O_TRUNC flag was specified.
• pathname refers to a file that is currently being read by the kernel (e.g., for module/firmware loading), and write access was requested.

The underlying filesystem does not support file locks

Either:

• One of the path components does not exist.
• Cwd was used, but cwd has been deleted.
• The path associated with the open directory handle has been deleted.
• On macOS, multiple processes or threads raced to create the same file with O.EXCL set to false.

The file is too large to be opened. This error is unreachable for 64-bit targets, as well as when opening directories.

The option is not supported by the protocol.

WASI-only; file paths must be valid UTF-8.

Windows-only; file paths provided by the user must be valid WTF-8. https://simonsapin.github.io/wtf-8/

The path refers to directory but the DIRECTORY flag was not provided.

Unable to read file due to lock.

The path exceeded max_path_bytes bytes.

On Windows, \\server or \\server\share was not found.

The network subsystem has failed.

Network is unreachable.

A new path cannot be created because the device has no room for the new file. This error is only reachable when the CREAT flag is provided.

A component used as a directory in the path was not, in fact, a directory, or DIRECTORY was specified and the path was not a directory.

The path already exists and the CREAT and EXCL flags were provided.

Setting the socket option requires more elevated permissions.

The per-process limit on the number of open file descriptors has been reached.

This error occurs in Linux if the process to be read from no longer exists.

Unknown protocol, or protocol family not available.

The protocol type or the specified protocol is not supported within this domain.

The socket inode would reside on a read-only filesystem.

The socket type is not supported by the protocol.

Too many symbolic links were encountered in resolving addr.

The system-wide limit on the total number of open files has been reached.

Insufficient kernel memory was available, or the named file is a FIFO and per-user hard limit on memory allocation for pipes has been reached.

The send and receive timeout values are too big to fit into the timeout fields in the socket structure.

The Operating System returned an undocumented error code.

This error is in theory not possible, but it would be better to handle this error than to invoke undefined behavior.

When this error code is observed, it usually means the Zig Standard Library needs a small patch to add the error code to the error set for the respective function.

This error occurs when no global event loop is configured, and reading from the file descriptor would block.