From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/30221] Negative cache should differentiate failure types
Date: Mon, 13 Mar 2023 16:40:48 +0000 [thread overview]
Message-ID: <bug-30221-10460-ipKq4f8O7U@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30221-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30221
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
Even a 404 error may be transient, as a server may just not have gotten around
to indexing new content yet. Other transient errors may persist awhile. I
don't know of any unambiguous winning policy here.
As to the question that, if such a policy were formulated, how could the
results be represented in the filesystem: xattrs, yeah maybe. But even
simpler would be to have the code set the mtime or ctime of the 0-length file
to a cause-related artificial timestamp that will inform the "cache_miss_s"
expiry calculations.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-13 16:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 1:32 [Bug debuginfod/30221] New: " vi at endrift dot com
2023-03-13 16:40 ` fche at redhat dot com [this message]
2023-03-14 1:47 ` [Bug debuginfod/30221] " vi at endrift dot com
2023-03-17 1:00 ` vi at endrift dot com
2023-03-17 1:08 ` fche at redhat dot com
2023-03-17 1:16 ` vi at endrift dot com
2023-03-17 1:20 ` fche at redhat dot com
2023-03-17 1:28 ` vi at endrift dot com
2023-03-17 1:30 ` vi at endrift dot com
2023-03-17 16:16 ` amerey at redhat dot com
2023-03-17 16:53 ` amerey at redhat dot com
2023-03-17 23:39 ` vi at endrift dot com
2023-03-24 11:22 ` fche at redhat dot com
2023-04-08 13:29 ` mark at klomp dot org
2023-04-21 2:04 ` fche at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-30221-10460-ipKq4f8O7U@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).