From mboxrd@z Thu Jan 1 00:00:00 1970 From: Subject: bug#26201: No notification of cache misses when downloading substitutes Date: Tue, 21 Mar 2017 08:32:39 -0700 Message-ID: <20170321083239.3cbf1e8d@khaalida> References: <20170320184449.5ac06051@khaalida> <144e9ba8-af93-fb18-d2b9-f198ae7c11e9@tobias.gr> <20170320195247.05f72fc9@khaalida> <8e7e07d1-563f-666f-2c32-2a772757c86f@tobias.gr> <20170320214809.466dc5fe@khaalida> <20170320234912.46680062@khaalida> <1bbd8ee3-1745-3642-27ed-f095c732dc11@tobias.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56592) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cqLmT-0002rM-Ba for bug-guix@gnu.org; Tue, 21 Mar 2017 11:33:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cqLmQ-000128-O1 for bug-guix@gnu.org; Tue, 21 Mar 2017 11:33:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:39922) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cqLmQ-00011y-Li for bug-guix@gnu.org; Tue, 21 Mar 2017 11:33:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cqLmQ-00076S-GO for bug-guix@gnu.org; Tue, 21 Mar 2017 11:33:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <1bbd8ee3-1745-3642-27ed-f095c732dc11@tobias.gr> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Tobias Geerinckx-Rice Cc: 26201@debbugs.gnu.org On Tue, 21 Mar 2017 15:55:05 +0100 Tobias Geerinckx-Rice wrote: > To clarify: > > - Warnings should be scary because warnings should be actionable. There are warnings and there are errors. Warnings don't have to be scary; I get them every time I update emacs because of duplicate icons stored in two different directories in the store. Is that actionable? Not as far as I am concerned, unless I want to hand delete something from the store, which, as far as I understand it, shouldn't be done. > There's nothing the user can or needs to do about a cache miss. Please reread the 2nd part of my response in Message #23 in this bugreport for why this is needed. > - It would be randomly shown to everyone, since this happens > constantly. Unless mirror.hydra randomly loses data in it's cache from hydra, it won't be random in the least. > - The behaviour warned about is not incorrect or abnormal. No, but the behavior would inform the user that the unusual and random slowdown isn't another problem and is because mirror.hydra is having to update it's cache, which, as I explained before, is useful information. > [...] Quite frankly I'd like someone else to take a look at this bug, if for no other reason than I'm not sure if we're communicating clearly with each other here. Most of what you are saying makes no sense whatsoever and seems to miss the point I have attempted to make. While I will thank you for actually writing a patch, saying "the caching proxy is working properly! and there's nothing you can do about it." seems rather cynical and clearly misses the point of what I'm requesting here.