Authentication-Results: mail-b.sr.ht; dkim=pass header.d=emersion.fr header.i=@emersion.fr Received: from mail-40136.proton.ch (mail-40136.proton.ch [185.70.40.136]) by mail-b.sr.ht (Postfix) with ESMTPS id 085ED11EF2F for <~emersion/hut-dev@lists.sr.ht>; Sat, 28 May 2022 07:53:14 +0000 (UTC) Date: Sat, 28 May 2022 07:53:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=emersion.fr; s=protonmail2; t=1653724392; x=1653983592; bh=go49HcW7N94DcOYpSkuLDwPR4STg00sKZdg59RNr6O8=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To: Feedback-ID:Message-ID; b=vDILyYCc0aPHkgyzzPlpuqS6quTOU0Yt3jfoC8aPdcMoMYYMtgQDFF106kZu1dsKQ 2hOjrKO1tWrL5atxvDQhpKlEzcESEy8mHIdCBq4OyuHVsEgy6hrF3H0Mkgm6RqTXbC T6jR41VCl24ve62Of8WhGhATxgdXYzhUrwiwKq8KlKowah6cpcnFTicULWHGDgMwiv /k/9PTb9B67AxN701irFuSURP5tVQJeVoUKuMtMZ4KFDX9tOAujqFYPJrM+h5TJpys 7EOHKWqm/j8pETGTgcSXxXXERrzF1LNaFgDJvTJlbGs5bBe+x8Tp88wlcWyBpsYRxB +2S2NQW3rr2AQ== To: Blallo From: Simon Ser Cc: ~emersion/hut-dev@lists.sr.ht Reply-To: Simon Ser Subject: Re: [PATCH] Make timeout configurable Message-ID: <3JNzmIMfnnIA2cTXpbkaMFRkxng1BQv1Luatof43V25F4MpgSFS_k5E9zFm7WPdpnR0DasSRPKgS3dAr1w5iodrZTsc8UvEifatPy6ImF6Y=@emersion.fr> In-Reply-To: <20220516150540.42563-1-blallo@autistici.org> References: <20220516150540.42563-1-blallo@autistici.org> Feedback-ID: 1358184:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Monday, May 16th, 2022 at 17:02, Blallo wrote: > The http client used for interacting with the hut instance had a > hardcoded 30 seconds timeout. While this might be ok in most cases, I > happened to hit one of the corner cases when trying to push a tarball to > site.ht. This commit adds a global flag to set the value, defaulting to > the old one. Hm. If possible, I'd prefer to do the right thing by default and set a longer timeout for queries involving large file uploads, without requiring the user to manually pass a --timeout option.