Error Set SendFileError [src]

In WASI, this error occurs when the file descriptor does not hold the required rights to read from it.

The local end has been shut down on a connection oriented socket. In this case, the process will also receive a SIGPIPE unless MSG.NOSIGNAL is set.

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

Connection reset by peer.

Another Fast Open is already in progress.

Unable to read file due to lock.

The socket type requires that message be sent atomically, and the size of the message to be sent made this impossible. The message is not transmitted.

The local network interface used to reach the destination is down.

Network is unreachable.

This error occurs when a device gets disconnected before or mid-flush while it's being written to - errno(6): No such device or address.

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

The output queue for a network interface was full. This generally indicates that the interface has stopped sending, but may be caused by transient congestion. (Normally, this does not occur in Linux. Packets are just silently dropped when a device queue overflows.) This is also caused when there is not enough kernel memory available.

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.