From 7ef0eddfdcbe8c372b1de1ec7a9057ae9e6779bc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6rg=20Thalheim?= Date: Wed, 2 Apr 2025 17:59:30 +0200 Subject: [PATCH] decrease connect-timeout to 5s For people self-hosting caches that can be occasionally down, the default timeout is very long. This is annoying if you are trying to update your binary cache at the same time you are trying to update another machine. Same if cachix has one of its rare hiccups. We tested this value of 5s in srvos now for years and we like to travel around the world with shitty internet, so it should be still reasonable high. (cherry picked from commit bef91a618af5f1eb88757e52fad703c6145c3d5f) --- src/libstore/filetransfer.hh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/libstore/filetransfer.hh b/src/libstore/filetransfer.hh index 0ecc7f376..47e767664 100644 --- a/src/libstore/filetransfer.hh +++ b/src/libstore/filetransfer.hh @@ -30,7 +30,7 @@ struct FileTransferSettings : Config {"binary-caches-parallel-connections"}}; Setting connectTimeout{ - this, 0, "connect-timeout", + this, 5, "connect-timeout", R"( The timeout (in seconds) for establishing connections in the binary cache substituter. It corresponds to `curl`’s