diff options
| author | Mroik <mroik@delayed.space> | 2026-04-11 04:02:53 +0200 |
|---|---|---|
| committer | Mroik <mroik@delayed.space> | 2026-04-13 06:56:11 +0200 |
| commit | ffc0ad7c86408193b213c46cbca5c0d8b60f8632 (patch) | |
| tree | 2612530158ed0a2529f866e23f324758011efcfd /Cargo.lock | |
| parent | b336fd39444e8089d35a7a2bd4c0c3e8228c6c36 (diff) | |
Do not propagate TcpListener.accept() errors
Errors produced by the socket may not be necessarily fatal, meaning that
while a connection might be dropped the process should be able to resume
execution as if nothing happened and accept the next connection.
Error handling for accept() has been copied from NGINX's [1].
[1] https://stackoverflow.com/questions/76955978/which-socket-accept-errors-are-fatal
Signed-off-by: Mroik <mroik@delayed.space>
Diffstat (limited to 'Cargo.lock')
| -rw-r--r-- | Cargo.lock | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -207,6 +207,12 @@ dependencies = [ ] [[package]] +name = "libc" +version = "0.2.184" +source = "registry+https://github.com/rust-lang/crates.io-index" +checksum = "48f5d2a454e16a5ea0f4ced81bd44e4cfc7bd3a507b61887c99fd3538b28e4af" + +[[package]] name = "libsqlite3-sys" version = "0.37.0" source = "registry+https://github.com/rust-lang/crates.io-index" @@ -273,6 +279,7 @@ version = "0.1.0" dependencies = [ "anyhow", "env_logger", + "libc", "log", "rusqlite", "tokio", |
